Reverse-ETL reads computed results — audience segments, propensity scores, enriched attributes — from a cloud data warehouse and syncs them to downstream activation systems (ESPs, ad networks, CRMs, push-notification platforms). It is the activation layer of the composable CDP stack.
Why "reverse." Traditional ETL moves data from source systems into the warehouse. Reverse-ETL moves data in the opposite direction: from the warehouse (where it was computed) out to operational tools (where it is acted upon).
The composable-vs-packaged divide. In a packaged CDP, activation is native — the platform manages destination connections and audience sync with its own tooling. In a composable stack, reverse-ETL tools fill this role. The customer gets choice of destination, but absorbs the operational cost of maintaining reverse-ETL pipelines and managing destination-specific quirks.
Operational considerations.
- Sync frequency: Most reverse-ETL tools offer scheduled (15-min cadence typical) or event-triggered syncs. Sub-5-minute freshness has historically added cost and operational complexity. Fivetran Activations (formerly Census, acquired May 2025) introduced Live Syncs (GA), enabling sub-second real-time reverse ETL from BigQuery and supported CDWs — extending composable CDP activation into the latency-tier.intra-session range for supported source+destination pairs, without requiring a custom streaming pipeline. The latency floor of reverse-ETL as a category has shifted materially downward; the "15-minute minimum" assumption is now a conservative default, not an architectural ceiling.
- Identity mapping at the destination: Each destination system accepts a different identifier (email for ESP, customer ID for CRM, hashed email for ad network). Reverse-ETL tools must map warehouse identifiers to destination identifiers — a configuration burden that grows with each destination added.
- Diff-based syncing: Good reverse-ETL tools compute membership diffs (new entrants and exits from a segment) rather than full refreshes, reducing API call volume and cost at destinations.
Vendors providing this capability. Specialist tools: vendor.hightouch, vendor.census (now Fivetran Activations, acquired May 2025). Packaged-CDP alternative: vendor.adobe-experience-platform Destinations framework (governed by constraint.aep-second-gen-export-1500kb and constraint.aep-second-gen-data-access-api-200kb). Databricks Lakebase reverse-ETL (vendor.databricks) is an emerging native CDW alternative for Databricks-anchored stacks.