Hightouch shifts toward composable CDP

This launch shows Hightouch moving from being a pipe that moves warehouse data into apps, to being the system that decides which records belong to the same customer. That matters because identity resolution is the hard part of building a usable customer profile. It turns scattered emails, device IDs, account records, and event logs into one profile that marketing, sales, and support can actually act on, without forcing the company to adopt a separate CDP database.

• Zapier, Tray.io, and Workato mainly connect app A to app B. Hightouch starts with the warehouse, where the full customer record already lives, then writes the cleaned profile back out to tools like Salesforce and ad platforms. That makes it much closer to a warehouse-native CDP than a generic automation tool.
  1 sacra 3 hightouch 4 sacra
• The closest reverse ETL comparable, Census, is described around syncing modeled warehouse data into business apps, with audience building and transformations. Hightouch adds identity resolution on top, which pushes it further into customer unification, a function historically owned by CDPs like Segment and mParticle.
  1 sacra 2 hightouch 4 sacra 5 sacra
• In practice, identity resolution removes a painful manual step. Data teams no longer have to stitch together duplicate people and accounts in SQL models before every campaign or CRM sync. Hightouch can build an identity graph in the warehouse, create a customer 360 profile, and let non technical teams use that profile in audience builders and downstream workflows.
  1 sacra 2 hightouch 3 hightouch 6 hightouch

The next step is clear, Hightouch is expanding from reverse ETL into the broader composable CDP layer. If it keeps owning identity, audience creation, and activation on top of the warehouse, it will compete less with automation tools and more with traditional CDPs that charge for storing and governing the customer profile themselves.