Hightouch warehouse-first CDP activation

Hightouch won by turning the warehouse from a back office database into the place where marketers actually run targeting. In a traditional CDP, customer data is collected into the vendor’s own profile store and audience builder. Hightouch kept storage and modeling in Snowflake, BigQuery, Databricks, or Redshift, then layered audience building, identity resolution, and syncs on top, which let enterprises avoid copying data into a second system and reuse the same SQL models across marketing, sales, and support.1 2 3 4 5

• Segment’s original advantage was owning the event pipe and unified profile inside application code. That made it easy to route web and app events to many tools, but it also centered the customer model inside Segment’s system. Hightouch attacked that architecture by making the warehouse the system of record and the CDP the activation layer.2 3 4
• The practical buyer difference is who has to change their workflow. With Hightouch, a data team can keep defining customers, accounts, or custom objects in SQL and a marketer can build audiences on top of those tables. That matters most for enterprises with messy schemas, multiple business entities, or non standard destinations that do not fit a default CDP object model.1 3 5
• This shift also changed the revenue opportunity. Reverse ETL alone was too narrow, so Hightouch moved up from moving rows between systems to giving marketers audience building, match boosting, and campaign tools. That move helped it scale to an estimated $100M ARR by April 2026, while much of the standalone reverse ETL category consolidated.1 6

The category is heading toward a split where storage matters less and activation matters more. Traditional CDPs are adding warehouse connections, while Hightouch is adding more marketer facing workflow and AI layers. The likely winner is the platform that can sit on top of the warehouse and still make campaign execution feel as simple as a packaged SaaS app.1 4 5 6