Hightouch
HighTouch is a customer data platform that enables clients to easily send data to third-party platforms through data integrations. With HighTouch’s existing Rokt Destination, users can effortlessly send conversion data from their HighTouch account to Rokt, enabling more precise targeting, better personalization, and improved campaign outcomes.
This guide outlines the steps required to set up your Rokt integration within HighTouch to easily send comprehensive and enriched conversion data to Rokt to connect marketing activity, such as a Referral, to outcomes that drive business value, such as a customer Conversion (e.g., purchases, subscriptions, or application downloads).
Integration Setup
Authentication
Authenticating with the Rokt Events Connector requires an AppId, AppSecret and Account ID. Read Generating AppId & AppSecret for more information.
Creating a Rokt Destination
Log in to your HighTouch account and click on the WorkSpace that you want to connect Rokt to
Click on Destinations in the left toolbar and then click on Add Destination
Search for Rokt, click on Rokt and Click Continue
Add your App ID, App Secret and Account ID here. Please note that you do not need the API key for the event integration.
Click Continue
Name your connection ie Rokt Integration
Click Finish
Click Test Connection - If you did the above correctly, you should see a success message
You are now finished with establishing Rokt as a destination
Add a Sync
Click on Sync in the left hand toolbar and then choose Add Sync
Choose your Model
Select the created Rokt Destination created above in the previous step
Configure and Map all necessary attributes
Please note that the mapping of attributes is very important to ensure that the integration is set up correctly. To ensure conversions and associated metadata are sent to Rokt in the correct format, the following elements must be captured and ultimately received by Rokt’s:
| Parameter | Description | Required / Recommeneded |
|---|---|---|
| Event Type | Type of Event or Action | Required |
| Event ID | An identifier used to uniquely identify an event | Required |
| Event Time | Time of the event in UTC | Required |
| Email passed as plain text, lowercase and without trailing spaces | One email field is necessary. Raw is preferred but hashed is acceptable. Raw and hashed is recommended. | |
| Email (already SHA256 hashed) | SHA-256 hash of email address, already hashed | See Above |
| Email (apply SHA256 hash) | SHA-256 hash of email address. Tealium will hash | See Above |
| Rokt Tracking ID | A Rokt-generated ID used to match conversion events to the originating click | Recommended |
| Mobile | Mobile phone number of converting customer | Recommended |
| First Name | Customer's first name | Recommended |
| Last Name | Customer's last name | Recommended |
For a full list of supported parameters, refer to the Event API documentation. We recommend you include fields like transaction amount, currency code, product details, and payment method to provide context for better targeting and optimizations.
Choose No where it asks if we want HighTouch to automatically detect PII
Click Continue
Choose the cadence at which you want to run this Sync note the more real time, the better the performance
Click Finish and then Run
You are now finished! For questions and concerns, please reach out to your Rokt contact or account manager.