Hightouch Faces Snowflake and Databricks

The real risk is not that Snowflake or Databricks copy a sync job, it is that they absorb the whole workflow around warehouse data activation and make reverse ETL feel like a feature instead of a product. Reverse ETL started as one layer in the modern data stack, but the market has already shifted toward bundling. Hightouch’s response has been to move up from moving rows into apps to giving marketers identity resolution, audience building, and campaign tooling on top of warehouse data.1 2 3 4 5

• Databricks has already moved in this direction. In June 2026 it launched CustomerLake, a native CDP on Databricks with identity resolution, segmentation, activation, and personalization. That is exactly the kind of platform level move that can compress standalone reverse ETL vendors.4
• The category has already consolidated. Reverse ETL proved important as a capability, but too narrow as a standalone market. Census sold to Fivetran in May 2025, and broader research across the modern data stack shows buyers cutting add on tools when ROI is hard to tie to revenue or conversion lift.1 3 6
• Hightouch has been building the buffer against this risk. Customer Studio lets marketers build audiences and journeys from warehouse data without SQL, and Identity Resolution writes unified customer tables back into the warehouse. That gives Hightouch product surface above raw data movement, where teams can justify spend through campaign performance and targeting outcomes.1 2 5 7 8

This is heading toward a fight between horizontal data platforms and warehouse native marketing suites. Snowflake and Databricks can keep pushing upward into activation, so Hightouch’s best path is to keep owning the marketer facing layer, where identity, audiences, decisioning, and execution are packaged into a system that is easier to buy than raw warehouse plumbing.1 3 4 5 7