Hightouch Data Activation Platform

To resolve order associations and identity resolutions, we primarily use Hightouch to retrieve data from our database, which is our source of truth, and then push it back into our CRM platform so that the sales and marketing teams have all information without discrepancies.

Our main use case for Hightouch is to ensure that all information in our portal and database matches in HubSpot, as sales and marketing professionals use the CRM platform to make calls, schedule meetings, and log activities, with HubSpot being the primary source of truth. We must ensure that whatever information we have in our database and warehouse is reflected in HubSpot as well. We also create various segments and perform other derived calculations at the database level, such as creating deals, which we push back into HubSpot so the team knows whom to target and call, in terms of lead scoring and other activities.

Hightouch has positively impacted our organization by creating a ripple effect that has definitely improved our data accuracy, which in turn leads to better business decisions. We have managed to resolve many issues in HubSpot mainly through Hightouch, enabling us to create custom objects, sync them back, and use those custom objects to better validate and resolve any issues in HubSpot. Hightouch is one of the tools we use primarily to populate the right set of data back into the CRM platform, speeding things up and improving our data accuracy, which leads to better business decisions.

Our data accuracy has improved significantly by at least 30%, and the time saved from installation and other activities is approximately three to four hours.

Hightouch's best features include a simple and easy-to-navigate user interface, which means there is not much of a learning curve involved, simplifying the process of setting it up and selecting desired fields along with using the query editor. The user interface is so simplistic that it did not take us much time figuring out where each button is and what they do.

My experience with the query editor and field selection is that it was very easy for me to identify where I need to edit the query, and I could easily spot the fields and buttons that help me in creating the models for the sync. This was self-explanatory for me and something I really appreciate about Hightouch.

I do not see anything that needs improvement. Since we are relatively new to using Hightouch, we have not explored all functionalities yet, so I cannot comment on what can be improved at this time. I do not think there is anything minor or something I wish existed in the platform that needs to be added.

We have been using Hightouch for the past six months primarily for reverse ETL to fix our issues in HubSpot, which is our primary CRM tool used by both sales and marketing people.

Hightouch is stable.

Hightouch's scalability is quite good.

Hightouch's customer support is quite good.

We did not use a different solution before Hightouch.

We have definitely saved time and improved our data accuracy.

My experience with pricing, setup cost, and licensing was smooth.

Before choosing Hightouch, we did not evaluate other options.

I rate Hightouch an eight on a scale of one to ten based on all the comments I have made. Regarding Hightouch's artificial intelligence capabilities, I think its governance and security are aligned with industry standards.

I think Hightouch's accuracy is quite good, and while we have not explored many of Hightouch's artificial intelligence capabilities yet, we are still creating all syncs and models manually to ensure everything is placed in the right location.

My main use case for Hightouch is as a composable data platform, which works differently from traditional customer data platforms. Unlike them, Hightouch allows us to operate on top of our data warehouse, whether it's Snowflake, DataBricks, or any SQL-supported warehouse, leading to almost negligible data movement and improving our data latency through reverse ETL.

In a specific workflow at Lululemon, Hightouch made a significant difference as it helped our team build and activate customer journeys through various channels such as email, integrating with services such as Salesforce Marketing Cloud and allowing marketers to log in, use stitched customer profiles to create segments, and activate them.

I find Hightouch valuable because it avoids data duplication and unnecessary costs associated with moving large amounts of data, enabling us to work on real-time data through its composable solution. Although Hightouch is still evolving with many improvements possible, it operationalizes a marketer's approach to utilizing customer data for personalized use cases.

Hightouch has positively impacted my organization by allowing us to address more real-time use cases, which is beneficial, although the stitching process for profiles still lacks features such as unmerging, with the current capabilities being deterministic. I look forward to seeing enhancements in this area in future product releases.

We have been able to activate on abandoned cart and abandoned browse use cases with Hightouch, making it a powerful tool for our marketing strategy.

The best features that Hightouch offers, in my opinion, include a flexible and convenient UI that is easy for marketing personnel to use, complemented by decent security features such as role-based access, which allows for controlled data access, alongside the ability to define a more understandable schema for business users. However, integrating Hightouch requires significant effort to set up those integrations and datasets.

The feature that made the biggest difference day-to-day is Hightouch's ability to create normalized, performant data models, which could truly aid enterprises dealing with a variety of data systems. Additionally, although the UI is user-friendly, the limitation to specific compute platforms such as Snowflake and the need for support in hybrid landscapes are areas for future improvement.

A lot of data engineering still needs to be handled by companies themselves, as Hightouch does not fully address this issue, and I believe it is an area for them to focus on.

Hightouch could be improved by adding probabilistic stitching for ID resolution, enabling incremental ID resolution to avoid full identity graph generation each time, enhancing support for hybrid data landscapes, and improving explainability and reliability in production support.

I have been using Hightouch since my previous company when I was working at Lululemon, where we migrated from Treasure Data Acquia to Hightouch, and I personally led that entire implementation.

Hightouch is a mature product, although it still needs to catch up with leading CDPs. Nevertheless, it is comparatively cheaper than larger competitors, offering significant cost-saving potential along with many capabilities. My advice for others considering Hightouch would be to take this into account.

Regarding Hightouch's AI capabilities, I have not had the opportunity to work with them personally, and although I know they are publishing various AI agents, I did not encounter any AI functionalities during my time at Lululemon as they were not available in the product at that moment.

I would rate Hightouch a six out of ten. I chose this rating because Hightouch has plenty of room for improvement, and although I have explained the shortcomings, I recognize that as a young company, they are likely prioritizing these enhancements.

A specific example of how I use Hightouch for my marketing and email campaigns is that if we pull web analytics data from our flagship sites like Toyota or Lexus.co.uk, we can use that data to identify or categorize customers into hot or warm prospects and then send them a bespoke email, essentially encouraging them to come in for a test drive.

I have other examples regarding my main use case with Hightouch. For example, we have a flat battery campaign where we want to reduce our stay callers. They have an old car and they haven't had a battery replacement in a while. We realized there was a cost-saving initiative by predicting people with batteries that could be replaced and replacing them, which would ultimately save us money by preemptively replacing the batteries rather than waiting for their battery to go flat. We worked with AA to receive that data and built a pipeline around that, which identifies customers, and we pushed that to Hightouch.

Out of those features, the one my team uses the most is probably the schema and the model integration, which allows data engineers to sync data from their warehouse or lake house to Hightouch. Journeys and audiences can be built on top of that by non-technical users, which I find so valuable.

Regarding Hightouch's governance and security, I think they are good because I think it is a composable data platform, so it does not make a copy of our data, which is always a plus, and I do not see risk of any PII data being exposed on it.

Regarding Hightouch's accuracy and reliability of output, that is something we have not used much of. In all honesty, that is something which we have left unexplored.

My recommendation to others reading reviews on PeerSpot is that they should really clarify whether they need Hightouch or not. If you think you can work with non-technical people to build journeys and audiences, then it is worthwhile, and that is where you can save time.