With Hightouch you can send in enriched data to Chameleon and leverage it when targeting, personalizing, and analyzing your Experiences.

Hightouch is a Reverse ETL tool that helps manage and sync your warehouse data back to your tool stack so teams can easily use it to make better decisions and improve efforts. Use Hightouch to connect the tools that help you drive success, for finer user targeting in Chameleon.

You can configure Chameleon as a data destination in Hightouch to create hyper-targeted Segments and deliver a better user experience.


Quick access


What is Reverse ETL?

The 'Extract-Transform-Load' process is used to replicate data from your many sources to a single repository - your data warehouse. And yes, this is a great way to create a centralized source of truth to back up your decisions. But as a warehouse is usually only available to technical users and you have multiple further uses for your data, Reverse ETL is the way to go.

Through Reverse ETL you can easily copy the data you have in your central warehouse to your tools (e.g. Segment, Salesforce, Zendesk, Mixpanel) and leverage it across your marketing, reporting, or development efforts. This means you can get enriched data that is combined from all your other tools, and put it to work further down the pipeline.

Hightouch Webhooks

You can use Hightouch to send enriched data from your tool stack to Chameleon, and use it to create better product guidance.

To configure this, you'll need to add a Chameleon Webhook endpoint to Hightouch to allow it to communicate with Chameleon. You can view the Chameleon Webhook endpoints on the custom Integrations page in the Dashboard.

👉 You can learn more about using Webhooks in Chameleon from this article.

Hightouch setup

  1. Add a source

First, you'll have to pick your data warehouse, customer data platform, or even a spreadsheet, to connect as a source from your Hightouch account.

2. Add a destination

In your Hightouch account, go to the Destinations page and click "Add destination" to configure Chameleon as a data receiver. Chameleon is not a native result in the 'Destination' list yet, so you'll choose "HTTP Request" as the destination.

When setting up the HTTP Request destination for the first time, you can optionally provide headers to be included in each outbound HTTP request. These headers often include access tokens used for authentication. That's it for destination setup. Endpoints, payloads, and other parameters are defined later during sync setup.


👀 Coming soon: native integration with Hightouch to help you seamlessly send your data to Chameleon.


Finalize creating the destination with a clear name so your team can use this data efficiently.

3. Define a model

Now that you have Chameleon as a destination, you can define a model (most often with SQL) to tell Hightouch how to and what data to sync between your source and your destination.

4. Sync Hightouch data with Chameleon

Finally, you'll add a sync between your source and your destination to configure how this data should be sent to Chameleon. On Chameleon's Webhooks page you'll find the three different attributes endpoints that you can use, each with its unique URL:

  • user properties

  • company properties

  • user events

You'll use these URLs to authenticate the sync between Chameleon from your Hightouch dashboard. Depending on the type of data you want to send in, copy the unique Webhook URL and use it when configuring your sync.

For example, if I were creating a sync to add a new user profile to Chameleon from one that is added from my source, the sync setup would look like this:

Creating a sync is also where you'll:

  • customize your payload -- Tell Hightouch how to build the request payload using data from your model.

  • adjust rate limit and concurrency -- Tell Hightouch how to avoid overwhelming your web service with requests.

  • set how often this data should be sent -- Your data can be synced at per minute, hourly, daily, and weekly intervals.

  • map out specific fields -- You can map out data in Hightouch via basic columns, or using advanced techniques like variables, or liquid language.

The process is the same when using either of the Webhooks but the data you map out will differ.

When mapping out your fields, make sure to match them with the correct attributes you are sending to Chameleon (e.g. user vs company properties). The uid is an essential property to look out for, but you can easily send in trial, account status, or plan renew attributes and map them out here.


Note: You will need to make sure you are sending the same uid to both Hightouch and Chameleon.


💡 When syncing event data, select a frequency that allows you to benefit from your users' responses but doesn't overburden you.

Click "Save" from the Hightouch dashboard to add this sync and test it out to make sure it runs correctly.

With every successful sync, you'll find your Hightouch properties available as filters when creating your audience in Chameleon. But you can also leverage the user properties you send in to personalize the Experiences you create in Chameleon.

This way you can connect valuable data across your tool stack and put it to work when guiding users in your product.


Go further

Did this answer your question?