Hightouch is currently the independent leader of the reverse-ETL layer. It turns your modelled warehouse into an activation source without duplicating the data. Composable, not packaged.
What is Hightouch?
Hightouch pushes data from the warehouse back into the operational tools where marketing and sales work. An audience modelled in the warehouse lands in Google Ads, Meta, the CRM, or the email tool, without anyone filing an engineering ticket. That's reverse-ETL: not loading data into the warehouse, but activating modelled data out of it.
Customer Studio makes that step marketer-friendly. Audiences are defined through a UI, but the logic stays bound to the warehouse models. One definition, one source of truth.
When Hightouch fits, and when it doesn't
A fit when:
- the warehouse is your golden record
- marketers need audiences without an engineering dependency
- you want to avoid a packaged CDP and its data duplicates
- activation should run into many destinations at once
Less so when:
- no cleanly modelled warehouse exists yet
- the data foundation still has to be built
- nobody maintains the audience logic
Packaged CDP vs. composable with Hightouch
| Criterion | Packaged CDP | Hightouch (composable) |
|---|---|---|
| Data storage | own store, duplicated | in the warehouse |
| Source of truth | two systems | one, the warehouse |
| Modelling | in the CDP tool | in dbt, once |
| Cost | storage plus licence | activation on what exists |
| Consistency | sync risk | one definition |
What Datascale builds with Hightouch
We build the activation layer on the modelled warehouse:
- audience models in dbt as the foundation
- setup of Hightouch on BigQuery or Snowflake
- syncs into ads, CRM, email, and other destinations
- field mapping and PII control per destination
- monitoring of syncs and data quality
The full picture lives in the Marketing Data Lakehouse and Revenue Intelligence. Activation comes after the foundation: first the model with dbt, then the sync.
