Empower your marketing team by delivering up-to-date event data to Rokt straight from your warehouse
|Sync Type||Description||Supported Sync Modes||API reference|
|Events||Sync data from any source to events||Insert||Event API docs|
|Segments||Create and update audiences||Add||Custom Audience API|
Connect to Rokt
Go to the Destinations overview page and click the Add destination button. Select Rokt and click Continue. You can then authenticate Hightouch to Rokt by entering the following required fields into Hightouch:
- App ID
- App Secret
- Account ID: You can find this in the URL of your Rokt account. Go to your profile settings and the URL will look like this:
You can find the the AppID and the App Secret at the bottom of your Rokt profile settings. If you haven't created an app yet, create an app and generate the two values. For more information, refer to Rokt's docs.
If you plan on syncing audience segements, you also need to enter your API Key. You can retrieve one by following these instructions in Rokt's docs.
Once you've set up your Rokt destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Rokt destination you want to sync to.
When syncing events, Hightouch treats any records added to your source as new events and sends them to Rokt when your sync runs.
Rokt's Event API requires the following event parameters:
The sync configuration form ensures all these are set and provides some additional options.
You can optionally select a column that contains timestamps of when events occurred. If this field is empty, Hightouch uses the time the event arrives at the server. Hightouch syncs the timestamp as the
eventTime parameter the Event API requires.
If you select a column, it should be in in UTC and RFC 3339. The request will be rejected if it contains an event with a timestamp that is older than 18 months or more than 5 minutes into the future from the time that the Event API receives it. Events with timestamps that are outside of this range are not processed.
You can sync model columns to Rokt's event properties, including custom fields. You must include mappings for the Client Event ID and Event Type fields.
Handling PII and hashing
By default, Hightouch automatically hashes the following fields before sending them to Rokt:
- Mobile Phone
- First Name
- Last Name
- IP Address
You can disable this behavior in the sync configuration. If disabled, the data from the model should be appropriately normalized and hashed according to Rokt's hashing requirements.
You can use these lists to target or exclude specific customers in your campaigns. You can also use these lists to determine which customers experience Rokt on your site.
The Rokt API enables you to create an audience using email information. You select which type of email field to use in the field mapping portion of sync configuration.
To identify which users to add or update in an audience, select model columns that contain the users' email, email (MD5 Hash), or email (SHA256 Hash).
Select an existing audience or create a new one
You can create a new audience or use an existing one. When creating a new audience, you can optionally enter a name; otherwise, Hightouch defaults to the name of the associated model. To use an existing audience, select the desired audience from the dropdown.
Handling PII and hashing
By default, Hightouch automatically hashes unhashed emails before sending them to Rokt. You can disable this behavior in the sync configuration.
Tips and troubleshooting
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.
Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.