What do you like best about the product?

What makes Hightouch stand out is the quality of the tool itself. With ETL or reverse ETL tools, consistency and delivery quality are all that matter. You can see and feel that in every part of Hightouch, from UX, UI, connectors quality...
Also, the team is approachable and highly open to discussing new features and user insights. That's why we use HT for standard use cases (marketing audiences, CRM attributes) as well as our main bridge between Data & Tech teams.

What do you dislike about the product?

Not much! We hit some road bumps during +2 years of usage, but the HT team fixed or released a new feature in no time. I guess that's another plus.

What problems is the product solving and how is that benefiting you?

When your data warehouse reaches a certain amount of qualified data, it is time to model it and send it back to 3rd party SaaS.
Before Hightouch, you'd employ data engineers and make them work full-time on the same code for Facebook audiences, Intercom contact updates; you name it.
Just buy Hightouch, and make your DEs work on something more interesting.

What do you like best about the product?

The most helpful aspect of Hightouch is ...

1) Ability to quickly access and synchronize DBT models built on Snowflake.
2) Ability to quickly setup existing integrations and new integrations with webhooks.
3) Ability to pass any data model object, especially things not typically seen in the world of legacy CDPs.

Together these things allow our team to pass custom data quickly and easily, spending less time thinking about "how" we'll send data and more time thinking about "why" and "what's next". This is the tool that allows growth teams to spend their time crafting growth levers and data and martech teams supporting them in executing.

What do you dislike about the product?

It's hard to specify what I dislike because there is so much I love, and a lot more that I dislike, but understand. Products like this are immensely powerful and with that comes a tradeoff between feature overload and discrete, focused capabilities.

With Hightouch, they have all the things most modern marketing tech teams want to do (syncs, variety of destinations, variety of ways to build against webhooks), most of the things Data teams care about (syncs, pager dutu, model loading), and things for folks in between like Audiences.

What is hard about the RETL space in general is that event instrumentation still lives upstream in the CDP. It would be great to see ETL/Event instrumentation abilities brought into an RETL suite that way technical teams could actually make a choice between pure CDP or a decomposed stack.

What problems is the product solving and how is that benefiting you?

Hightouch solves problems across our business, sales, marketing, growth and data teams. We use Hightouch to:

A) Load updates into Hubspot and Salesforce, keeping our data clean and enriching it with transformations data that otherwise would be very hard to do.
B) Capture, transform and load bottom of funnel, non user/event oriented data back into our ad conversion APIs (FB, TikTok, Google, Bing, Impact Radius and Fintel).

We are just scratching the surface of what is possible in Hightouch, but it provides us a flexible tool to do load advanced, modeled data into tools without thinking twice.

What do you like best about the product?

The level of flexibility Hightouch has to offer has been truly amazing. Even for tasks the tool wasn't originally designed to do, it's been easy to find solutions to the problems we're trying to solve. Their support has been incredible, and I wish all our vendors were this easy to work with.

What do you dislike about the product?

So far, my only complaints have been minor UI features that don't impact the tool's usability in any significant way. They're still working on improving the experience of moving things from a testing environment to a production environment. Still, their support engineer was incredibly helpful in providing the information I needed to create a bash script to do the job.

What problems is the product solving and how is that benefiting you?

We have several systems that require entering the same information. With Hightouch it has been easy to set up new destinations and populate data from one system into others via our data warehouse. It reduces manual data entry, giving our staff more time to work on high-value tasks.

I first took Hightouch for a spin to complete a CRM migration. We had two separate CRM instances that needed to be migrated to a single Salesforce instance with a vastly different data model. Having the ability to set up models with custom SQL and transform data with their template engine made the massive job much easier to handle.

What do you like best about the product?

The dashboard and user interface are so user-friendly. So simple in use and self explanatory.

What do you dislike about the product?

So far, it has covered everything that I want. Nothing to dislike.

What problems is the product solving and how is that benefiting you?

It is helping us replicate a wide variety of different data sources to single target.
Example.
we are replicating Postgres DB , Oracle DB , Oracle EBS, Oracle Net suite to Redshift Cluster.
Hightouch takes care of everything.

What do you like best about the product?

Hightouch makes it incredibly easy to sync your data. The error logging is very detailed. You can just set up your models and syncs are you are good to go.

What do you dislike about the product?

We've had some issues with the total number of operations that were performed in sync. But it is a rare occurrence.

What problems is the product solving and how is that benefiting you?

Hightouch is helping us keep all of our data in sync across multiple sources. Hightouch also uses diffs to ensure that you're not repeatedly sending over the same data.

What do you like best about the product?

Great UI
Easy to set up first time
Documentation is clear
Amazing support (slack channel, dedicated success team you got to know)
Many targets and sources to choose from

What do you dislike about the product?

Some tiny nasty small mishaps that would bother only users working with large volumes of data (me 😁). For example, we had a couple of cases when due to some bug our query fully resynced. If there are 100K records, that's completely manageable, but if this happens for 11M, you had to wait for a couple of days till the query is finished, that's a pain and causes a delay in our internal processes. Especially if knowing that we didn't have changes to the model and that was just athena error or something. I think Peter (Tran) knows all details if you'd want to investigate more.

One more thing, we couldn't sync hubspot associations by external ids. We're syncing contacts as users, accounts as a custom object, then associating both objects via bridge table. The bridge table contains only external ids on the day we create a record in hubspot. Right now we can associate contact and account object only by **hubspot** object id, which is not available right away in dw. So we're creating first contacts and accounts, waiting one day and then creating associations between them, which is a bit confusing to our stakeholders.

Would be amazing if we could somehow filter some errors in syncs. For example, we have some bad email data that got rejected. Right now, the only way is to filter it out in the model which is a bit time-consuming. If we could do some checkmark 'don't sync again this record' - that would be amazing.

One more trouble we run into is also related to volume. We're always afraid that updated records amount from our model is basically uncontrolled (that's on our side). We can have on average 10-20K records a day and then due to some metric bump - 500K. This impacts our API usage for outgest and ingest. If we're using webhooks for particular data ingest - webhook can't ingest such amount of data and got stuck. Answer to this is to have some limits in hightouch and not update so many records at once. So far there are options to do that, but those seem more like a workaround than a product feature. Will be amazing if could set the limit of, say, 100K a day, and if we have more records - update the rest on the next run in a queue. Or at least if we have some big update - receive notifications so we can respond to this proactively, not reactively.

What problems is the product solving and how is that benefiting you?

We used to have an extensive custom python code for outgest in multiple CRM systems. It works very slowly and is not transparent. Hightouch enables us to use data from data warehouse we're confident of and document the logic of the model for each property we sync. This way is much more transparent for end users.

What do you like best about the product?

We've been using Hightouch for different use cases. The ability to read SQL databases and post to REST APIs or sending notifications to Slack is really powerful.

What do you dislike about the product?

I would like to create pipelines between projects. We have a staging project and a production one. We can export the staging project to production, but still, this happens outside the tool and with several manual steps. I'd like to have a process inside the tool to promote a staging sync to a production one.

What problems is the product solving and how is that benefiting you?

- Keeping old and new service databases in sync while we replace old services for newer ones
- Running queries and detecting eventual inconsistencies in the database and triggering alerts for them
- Data migration
Among others.

What do you like best about the product?

very easy setup with good notification and dbt support and a great selection of destinations.

What do you dislike about the product?

An integration for data catalogues would be useful to provide an end-to-end perspective of the data flow.

What problems is the product solving and how is that benefiting you?

We are using Hightouch to distribute data Salesforce and marketing vendor systems like Braze.

What do you like best about the product?

Incredibly simple to use and extract value from. The implementation goes incredibly quickly and you're up and running within minutes.

What do you dislike about the product?

Error states could be more descriptive sometimes (it's not always clear what caused an execution error), but generally Hightouch just works

What problems is the product solving and how is that benefiting you?

Hightouch allows us to get information from our data warehouse back into the tools we use to interface with customers. Doing so allows us to drive top-of-the-line customer satisfaction.

What do you like best about the product?

Right with the setup or configuring the various objects and integrating the pipelines to move data from the warehouse to the source system. The documentation was very clear on how to get things done.

What do you dislike about the product?

Limited features and destinations which we as a company use.

What problems is the product solving and how is that benefiting you?

It helps integrate the data back into the source system where the stakeholders can view the reports. Hightouch helps resolve retries and API limits that need to be custom build inhouse. Also this can be used by analysts/business users with ease.