Hightouch is a Reverse ETL solution that makes it easy to pipe data from your data warehouse into downstream tools like Correlated. With our custom destination, you can pull pre-modeled data from your data warehouse directly into Correlated. Also, Hightouch makes it possible for Correlated to smartly infer how your data is important and why it matters so that you can get started with more populated views throughout the Correlated product with limited configuration on your part.
To get started, here's what you should have:
- A Hightouch Account
- Existing Sources that contain the data you want to connect
- A Correlated Account
It's helpful to have existing Models, but you can also connect Hightouch to Correlated first to see what data we support before creating your Models.
Correlated accepts Account and User fields from Hightouch
You can pipe data from Hightouch to Correlated as long as that data describes either an Account or a User. We provide some default fields that you can sync, as well as custom fields.
Note: The entire Hightouch integration can be configured entirely in Hightouch.
- Sign in to Correlated
- Click the Integrations tab in the left bar navigation
- Find the "Hightouch" card and click Connect
- You'll be prompted to create a Hightouch API key. Hit Create.
- Copy the API key displayed
Now, you're ready to set up a destination in Hightouch.
- Navigate to the "Destinations" tab on the left navigation
- Click "Add Destination" in the top right
- Select "Custom Destination"
- In the form, fill in the URI field with: https://collector.getcorrelated.com/hightouch/v1. In the Headers field, type in "Authorization". Copy in your Correlated API Key in the "Value of Authorization" field.
- Finally, finalize your settings with a Name and Slug, following the instructions shown in Hightouch, and hit "Finish".
- Navigate to the "Syncs" tab in Hightouch
- Click "Add Sync" on the top right
- Select the model you want to connect to Correlated
- Select the object type you want to sync to. Accounts must be identified with the same Account ID that you are using to identify Accounts in other data sources. Users must be identified with the same User ID that you are using to identify Users in other data sources.
- Continue to follow the prompts in Hightouch until you hit "How should records between query results and destinations be matched?". At this point, you'll be prompted to select your Account IDs or User IDs depending on which object type you are trying to sync to.
- Next, you'll be able to add as many columns as you want and map them to fields in Correlated. These will appear as Dimensions in Correlated. By default, you must provide a User ID and Email for User objects and an Account ID and Company Name for Account objects. You can also add additional mappings. Correlated offers a list of common fields by default, and you can also create custom fields.
Dimensions describe who the customers are - for example, how many seats they have, what region they are based in, how many employees they have, etc.
Adding Custom Fields
By mapping your modeled data columns to existing Correlated fields, you'll be able to benefit from out-of-the-box views since we'll be able to leverage the context you are providing to show the most relevant views. However, you can add custom fields to fully customize your Correlated experience. All you have to do is fill in the last step in the Hightouch configuration setup.
- Repeat steps 1-3 from above
- When you get to object type, select Events in order to pipe Metrics into Correlated
- Continue to follow the prompts in Hightouch until you hit "How should records between query results and destinations be matched?" To configure the sync, we will need:
- A column that contains your Event Name
- A column that contains your Timestamp
- A column that contains your User ID (the same User ID you're using to identify Users from other data sources)
Recommended: Add Account ID
Although not required, it is also highly recommended that you click the "Add mapping" button and add additional mapping to your Account ID, in order to access events on the account level. See screenshot below:
- Next, you'll be able to add as many columns as you want and map them to fields in Correlated. These will appear as Metrics in Correlated. You can also add additional mappings. Correlated offers a list of common fields by default, and you can also create custom fields - see Adding Custom Fields section.
Metrics describe what your customers are doing in your product - for example, sign-ins, page views, feature usage, etc.
Updated 4 months ago