Census (reverse ETL)
Census is a reverse-ETL (data activation) tool: it takes modeled data from your warehouse and syncs it into operational tools — CRMs, ad platforms, support and marketing apps — so teams can act on warehouse-defined audiences and metrics. It runs in the opposite direction to ingestion tools, which load data into the warehouse rather than out of it.
What this means
Census reads from your warehouse — typically tables modeled by a tool like dbt — and syncs selected rows and fields into operational destinations on a schedule, keeping them in sync as the source changes. This is 'reverse ETL': data flows out of the warehouse into apps where people work.
The pattern keeps metric and audience definitions in the warehouse, then activates them where teams act, rather than redefining them in each tool.
What to weigh
Reverse ETL is the opposite direction from ingestion: ingestion loads sources into the warehouse, reverse ETL pushes modeled results out. Choosing it assumes the warehouse is your source of truth and you have clean models to sync.
- Syncs modeled warehouse data into operational tools
- Opposite direction to ingestion (EL) tools
- Keeps definitions in the warehouse, activates them downstream
Where it fits
It sits at the end of a warehouse-centric stack, after modeling. Sync mappings and schedules determine freshness in the destination tools, and the warehouse model determines correctness.
How it appears in analytics and logs
If a downstream tool shows the wrong audience, the cause is usually the warehouse model or the sync mapping, not the destination app — Census reflects what the model produces.
Diagnostic use case
Use Census to push warehouse-modeled segments, traits, or metrics into operational tools so the warehouse stays the single source of truth for definitions.
What WebmasterID can help detect
WebmasterID is a first-party measurement tool; this page explains reverse ETL so you can see how warehouse-modeled analytics get activated in operational systems.
Common mistakes
- Confusing reverse ETL with ingestion — the direction is reversed.
- Syncing un-modeled data and pushing inconsistent definitions out.
- Moving personal data downstream without reviewing consent and routing.
Privacy and accuracy notes
Reverse ETL moves data, possibly personal, from your warehouse into third-party tools; routing, consent, and region are your responsibility. This is factual, not legal advice.
Related pages
- Hightouch (reverse ETL)
Hightouch is a reverse-ETL and data-activation platform that syncs modeled data from a warehouse into operational and marketing tools, and supports audience building on top of warehouse data (a 'composable CDP' pattern). Like other reverse-ETL tools it moves data out of the warehouse, keeping the warehouse as the source of truth for definitions.
- Reverse ETL
Reverse ETL is the practice of taking modeled data from your data warehouse and syncing it back into operational tools — CRMs, ad platforms, marketing tools, support systems. Where ETL loads data into the warehouse, reverse ETL pushes warehouse-computed audiences and attributes out for activation, making the warehouse the source of truth even for operational use.
- dbt and the analytics stack
dbt (data build tool) is a transformation framework that runs SQL SELECT statements as version-controlled models inside your data warehouse, turning raw loaded tables into clean, documented, tested datasets. It handles the 'T' in ELT — it does not move data in or visualize it. It adds software-engineering practices (testing, lineage, docs) to analytics SQL.
- Web analytics
First-party web measurement overview.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.