Hightouch is a composable CDP and reverse ETL platform that operates directly on existing cloud data warehouses — Snowflake, BigQuery, Databricks, Redshift — without requiring a separate data copy or proprietary profile store. One of four Leaders in the 2026 Gartner Magic Quadrant for CDPs; the first warehouse-native CDP vendor to reach the Leader quadrant.
Role in composable CDP architecture. Replaces a packaged CDP's built-in destination connectors. The marketing or data engineering team defines audiences via SQL or dbt models; Hightouch handles sync, identity mapping per destination, and diff computation (only changed records synced, reducing API call volume and destination costs). 400+ destination connectors.
Zero-copy architecture. Data remains in the CDW; Hightouch reads and syncs without staging copies. Eliminates a second profile store, removes data-residency risk from a third-party profile copy, and avoids per-profile-per-year export quotas that apply to packaged CDPs (constraint.aep-second-gen-export-1500kb).
Agentification model. The source.martechtherapy-com analysis frames Hightouch as the canonical example of the "agentification" model: CDP as a lightweight, composable AI-agent data layer with no data lock-in. Contrasts with the "platformization" model (Salesforce Data 360) in which the CDP is the foundation for a broad enterprise application ecosystem.
Lightning Sync Engine. Hightouch's near-real-time sync engine for audience activation to supported destinations. Operates at sub-minute cadences — enables time-sensitive use cases (same-session retargeting, triggered suppression) without requiring a separate event streaming layer. Not sub-second; for the latency distinction relative to AEP edge processing, see capability.streaming-ingestion.
Match Booster. Identity enrichment for advertising destinations. Supplements standard audience syncs to ad platforms with additional identifier types (email hashes, phone hashes, device IDs) to improve downstream audience match rates. Particularly relevant for performance marketing use cases where audience scale directly affects campaign delivery efficiency.
Event Streaming. Routes raw event streams from Hightouch sources to streaming endpoints (Azure Event Hubs, AWS Kinesis, Confluent Kafka) in real time. Distinct from audience sync: Event Streaming activates individual events as they occur; audience sync activates segment membership changes on a cadence. Both modes can be combined — audience sync populates downstream profile stores; Event Streaming feeds real-time decisioning pipelines.
Customer Studio Journeys. Visual journey orchestration within Customer Studio. Enables multi-step, cross-channel journeys built on CDW-native audience data without writing SQL for each step. Positioned between full-stack packaged CDP journey logic (AEP Journey Optimizer, Salesforce Marketing Cloud) and pure audience-activation reverse ETL.
Where it fits. Organizations with a mature CDW seeking marketing activation without adopting a packaged CDP. Also fits organizations running the pattern.aep-as-edge-node pattern who want to push CDW-assembled audiences into AEP for activation without paying AEP ingestion costs.
Where it is less suited. Organizations with thin data engineering staffing that cannot maintain SQL/dbt audience models. Organizations that prefer vendor-curated activation with pre-built journey logic (packaged CDPs such as vendor.salesforce-data-360 or vendor.adobe-experience-platform serve this need). Organizations whose backbone is Databricks-native may find Lakebase eliminates the need for a separate reverse ETL layer.