Census + clariBI
Connect Census with your API key, sync your data-activation sync status, and see sync health next to the rest of your business data.
Native Census data-source connector.
Paste your Census API key, sync your sync status, and clariBI pulls each sync with its current health into preprocessed datasets and auto-generated dashboards, right next to your other tools. Access is read-only. This is sync-operations data, not the customer data your syncs move.
What is Census?
Census is a reverse-ETL platform that activates data from your warehouse into the tools your teams use, running each mapping as a sync.
clariBI reads Census through its REST API using your own API key: your syncs with their status and timestamps. This is sync-operations data (how your data activation is running), not the customer rows the syncs move. Access is read-only, and clariBI never edits or triggers a sync.
Learn more at getcensus.com
Connect Census in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source, find Census, and paste your API key (Census workspace settings, API access). The key is Fernet-encrypted at rest.
Choose what to sync
Pick the syncs resource to pull. clariBI reads it read-only.
Sync, then get dashboards
clariBI syncs the sync status, preprocesses it, and builds an insights dashboard. Ask "How many of our syncs are failing right now?" and the AI engine queries the synced status data.
What you can analyze
Out of the box with the Census connector:
- Syncs created over time
- Syncs by status (ready, up to date, failing)
- Paused versus active syncs
- Sync operation mix (mirror, upsert, append, update)
- Sync health lined up with releases or warehouse changes
- Cross-source: sync health → downstream tool freshness → team activity
Census is one of many data sources you can connect to clariBI. See the full list →
What gets synced
clariBI pulls your syncs through the Census REST API, paginates the full list, lands it as a preprocessed dataset, and refreshes it on your schedule. Access is read-only.
clariBI syncs each sync with its created date, status, operation, and paused flag, then builds an insights dashboard you can query, extend, or pull into reports. This is sync-operations data, the health and cadence of your data activation, not the customer rows the syncs move.
clariBI only ever reads. It never edits or triggers a sync in Census.
Cross-source questions Census makes possible
Census data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
Census × Reliability
"Is our sync failure rate getting worse?"
Planner: read sync status over time from Census, compute the share failing by week, and report the trend.
Census × Releases
"Did the warehouse change break any syncs?"
Planner: read sync status from Census, align to the change date, and flag syncs that started failing afterward.
Census connector FAQ
What do I need to connect Census?
Your Census API key (workspace settings, API access). You paste it into clariBI once; the key is Fernet-encrypted at rest.
Does this connector read the customer data my syncs move?
No. It reads sync-operations data: the status, operation, and timestamps of your syncs. It does not read the customer rows a sync moves, and it never edits or triggers a sync.
Which clariBI plan includes the Census connector?
Data-source connectors are available on the Trial, Starter, Professional, and Enterprise plans. You can connect it during the free 14-day trial.
Start your free trial and connect Census in a minute
API key in, read-only, synced sync-status dashboards in seconds.
Start free trial