> ## Documentation Index
> Fetch the complete documentation index at: https://support.configview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Census setup

Configview reads your Census organization (reverse ETL and data activation, getcensus.com, now part of Fivetran Activations) through the Census **Activations API V2** (`https://app.getcensus.com/api/v2`, or `https://app-eu.getcensus.com/api/v2` for the EU region), using an **Activations personal access token**. Configview sends only `GET` requests. It never creates, changes, triggers or deletes anything in Census.

You will end up with **1 required secret** (`GETCENSUS_ACCESS_TOKEN`) and **1 optional secret** (`GETCENSUS_REGION`) in Configview when setup is complete.

> **Scope of this integration today.** Configview answers "where does our warehouse data flow, into which tools, and are those syncs healthy": the sources Census reads from, the destinations it writes to, every sync (label, status, operation, schedule, paused, number of mappings and alerts), per-sync run summaries, datasets and webhooks. It does **not** read connection credentials or details, field mappings or constants, SQL, record data, run logs or error messages.

***

## What you need

* A Census (Fivetran Activations) account that can create a personal access token
* Your region: US (default) or EU

***

## Step 1: Open the Census page in Configview

Open Configview in a second browser tab and leave it open:

`https://{companyname}.configview.com/admin/integrations/census`

***

## Step 2: Create the token

1. In Census open your **user settings** and create a **personal access token** (an Activations token; a Fivetran API key does not work here)
2. Census documents no read-only token, so the token can do more than Configview uses; Configview only ever reads
3. In the Configview tab paste it into `GETCENSUS_ACCESS_TOKEN` under **Credentials** and save
4. If your organization is on `app-eu.getcensus.com`, set `GETCENSUS_REGION` to `eu`

***

## Step 3: Connect and verify

1. Click **Connect**. Configview creates its tables and schedules every collector at your default run time:

| Script | Notes |
| - | - |
| **Sources** | Warehouses and databases, type and last connection test. |
| **Activations (destinations)** | Tools Census writes into, type and last connection test. |
| **Syncs** | Every sync with status, operation, schedule and paused flag. |
| **Datasets** | Dataset names, columns count and size. Needs the datasets feature on your plan. |
| **Webhooks** | Name, host and events. |
| **Sync run stats** | Per sync: last run, runs and failures over 7 and 30 days. Runs after Syncs. |

2. Click **Verify now**. The health check reads the secret, then one page of sources and syncs.

If a check fails:

* **401.** The token is wrong, revoked, a Fivetran key or an old V1 workspace token, or the region is wrong.
* **403 or 404.** The token cannot read that area (datasets are plan-gated).

***

## Data Tables

Each table has a `run_at` column and keeps only the newest run.

| Table | Source | Key Columns |
| - | - | - |
| `getcensus_sources` | `GET /sources` | source\_id, source\_name, source\_type, sync\_engine, last\_test\_succeeded, last\_tested\_at |
| `getcensus_activations` | `GET /activations` | activation\_id, activation\_name, source\_id, destination\_type, is\_file\_system\_destination, last\_test\_succeeded |
| `getcensus_syncs` | `GET /syncs` | sync\_id, sync\_label, activation\_id, sync\_status, operation, is\_paused, schedule\_frequency, mapping\_count, alert\_count |
| `getcensus_sync_run_stats` | `GET /syncs/{id}/sync_runs` | sync\_id, last\_run\_at, last\_run\_status, last\_success\_at, runs\_30d, failed\_runs\_30d, records\_processed\_30d |
| `getcensus_datasets` | `GET /datasets` | dataset\_id, dataset\_name, source\_id, column\_count, cached\_record\_count |
| `getcensus_webhooks` | `GET /webhooks` | webhook\_id, webhook\_name, endpoint\_host, events |

***

## Things worth knowing

**No people.** API V2 has no member, role or invitation endpoints; user access moved to Fivetran's user management and needs a separate Fivetran API key. This integration therefore shows data flows, not who can edit them.

**API V1 is being retired.** Census retires API V1 on 2027-01-15; Configview uses V2 only. A V1 workspace token will not work.

**Run stats are summaries.** The collector reads at most the 300 newest runs per sync and keeps only counts, the last status and the last error code. Error messages and run content are never stored.

**Segments are not collected.** Segment records carry the SQL behind them, so Configview skips them.

**Rate limit.** Census publishes no numeric limit. Configview paces itself at 120 requests a minute, waits as long as a `429 Retry-After` asks and retries server errors.

## What isn't collected

* Source and destination connection details, credentials and storage settings
* Field mappings, constants and advanced sync configuration
* Dataset and segment SQL
* Sync run records, error messages and record data
* Webhook URLs (only the host)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.