Linking Census as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
The Census source is currently in alpha. It has been tested against Census's API documentation but not yet battle-tested with live production workloads. If you run into issues, please let us know.
The Census (Fivetran) connector syncs your reverse-ETL workspace metadata into PostHog, including syncs, sync runs, sources, and destinations.
Adding a data source
Go to the Data pipeline page and select the Sources tab.
Click + New source and select Census (Fivetran) by clicking the Link button.
Select your Workspace region from the dropdown:
| Label | Connects to |
|---|---|
| US | app.getcensus.com |
| EU | app-eu.getcensus.com |
Enter your API access token. This comes from your Census workspace settings (see Getting your API access token below).
Click Next.
Select the tables you want to import, set the sync method and frequency, then click Import.
The data warehouse then starts syncing your Census data. You can see details and progress in the data pipeline sources tab.
Getting your API access token
To connect Census to PostHog, you need a workspace API access token:
Log in to your Census workspace at app.getcensus.com (or app-eu.getcensus.com for EU).
Go to Workspace settings > API Access.
Click Create new token (or use an existing one with appropriate permissions).
Copy the token – you'll need it when linking the source in PostHog.
Configuration
| Option | Type | Required |
|---|---|---|
API access token | password | Yes |
Workspace region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
syncs | A Census sync: the configuration that moves data from a source model to a destination object, including its schedule, field mappings, and alerting. | Full refresh | — | — |
sync_runs | A single execution of a Census sync, including its status, timing, and per-run record counts. | Full refresh | — | — |
sources | A Census data source: a connected warehouse or database Census reads records from. | Full refresh | — | — |
destinations | A Census destination: a connected SaaS tool or warehouse Census writes records to. | Full refresh | — | — |
Sync modes
All Census tables use full refresh. Census's API does not expose a server-side filter for update time, so incremental syncing is not available.
| Table | Sync method |
|---|---|
syncs | Full refresh |
sync_runs | Full refresh |
sources | Full refresh |
destinations | Full refresh |
Full refresh syncs reload all data on each run.
Available tables
| Table | Description |
|---|---|
syncs | Census sync configurations that move data from a source model to a destination object, including schedule, field mappings, and alerting. |
sync_runs | Execution records of Census syncs, including status, timing, and per-run record counts. |
sources | Data sources connected to Census – warehouses or databases that Census reads from. |
destinations | Destinations connected to Census – SaaS tools or warehouses that Census writes to. |
The connection_details field is automatically removed from the sources and destinations tables. This field contains warehouse account identifiers (account name, user, warehouse name) that shouldn't be accessible to all project members.