What It Means When Your Reverse-ETL Specialist Gets Acquired: The Fivetran-Census Story

Angle

In May 2025, Fivetran — the dominant ELT data movement platform — acquired Census and rebranded it as Fivetran Activations. The acquisition is significant for two reasons that point in opposite directions. The positive: Live Syncs (sub-second reverse ETL from BigQuery) went GA, making Fivetran Activations the first reverse-ETL tool to operate at intra-session latency tiers — a genuine capability upgrade from Census's previous near-real-time ceiling. The concern: organizations that chose Census specifically because it was an independent specialist are now inside a larger platform — one that also competes with the warehouse tools their CDW runs on. The article asks the question buyers should ask about any composable stack specialist: what changes when the independent tool becomes a platform division? And what signals indicate when to stay vs. when to reassess?

Key decision this helps with

What organizational and technical signals should cause a team using Census / Fivetran Activations to reassess their reverse-ETL tool choice, and what signals should cause them to stay?

Tradeoffs the article will map

• Fivetran Activations (post-acquisition): 700+ connectors, sub-second Live Syncs, tighter CDW integration — capability-expanded but platform-concentrated; separate MAR meters for connection, activation, and transformation
• Hightouch (independent specialist): remains independently focused on activation; 200+ destinations; growing audience builder UI — potentially benefits from Fivetran's platform direction if buyers prioritize independence
• Databricks Lakebase native reverse ETL: CDW-native activation from the lakehouse — the most platform-concentrated option, but eliminates the activation specialist dependency entirely for organizations already on Databricks

Open questions / uncertainties

• Fivetran's pricing model for Activations uses separate MAR meters — how this interacts with existing Fivetran ELT contracts is not publicly documented; buyers should confirm with their Fivetran account team before assuming pricing continuity
• Live Syncs sub-second latency is confirmed GA for BigQuery; which other CDWs support Live Syncs at sub-second is not fully documented in available public sources — verify with Fivetran before generalizing the capability claim to Snowflake or Databricks

Knowledge-graph nodes this draws from

• vendor.census
• vendor.hightouch
• vendor.databricks
• capability.reverse-etl
• latency-tier.intra-session