Rokt Conversions
Use warehouse conversion events for Rokt campaign measurement.
Connect this destination to write warehouse conversion events onto Rokt, for use in campaign measurement.
This destination writes to your Rokt account and is a good fit when you want to:
- Get measurement for Rokt conversions
- Use a warehouse table that has an event ID, event type, and event time
This maps to GrowthLoop Syncs:
| Use it for | Syncs |
|---|---|
| Sending conversion events for measurement | ✓ |
You already connected Rokt as a destination. Do not use this workflow to add contacts to a custom audience. To activate customers for targeting or suppression, use Rokt.
Prerequisites
Make sure you have:
- Rokt connected as a destination, including App Id and App Secret.
- A warehouse table of conversion events.
Create a sync in GrowthLoop
Create a sync from a warehouse table to write conversion events onto Rokt. See Syncs for information on how to complete those steps.
Select an Object Type:
| Object | Use it for | Sync modes |
|---|---|---|
| Event | Conversion events for Rokt measurement | Insert |
When you configure the sync:
- Connection: Select your Rokt destination.
- Object Type: Select Event.
- Update Rule: Choose Insert. This destination adds new conversion events and does not update or remove previously uploaded events. See Sync behavior.
- Dataset/Table: Select the table that holds your conversion events. Use a unique event key so you do not re-send the same conversion.
- Match Field: Map Event Id.
After you map fields, click Save Route or Update Route. Enable the sync with the toggle at the top of the page.
When you update mappings on an existing sync, choose Updates only unless you need Back-fill. Back-fill rewrites already synced rows and can be expensive on your warehouse.
Conversion fields
| Destination field | Required | Description |
|---|---|---|
| Event Id | Yes | Unique ID for the event |
| Event Type | Yes | Typically conversion. GrowthLoop does not restrict this to a list |
| Event Time | Yes | When the event happened |
| No | Plaintext email | |
| Email (sha256) | No | SHA-256 hashed email |
| Passback conversion Id | No | Rokt conversion tracking ID |
| Amount | No | Conversion amount |
| Currency | No | ISO currency code |
| Quantity | No | Item quantity |
| Conversion Type | No | The action, such as purchase, signup, or subscription |
| Product name, Sku, Payment Type, Product Subcategory, Product Brand ccbin, Margin | No | Product and payment details |
| Transaction id, Confirmation ref | No | Transaction identifiers |
| First name, First name (sha256), Last name, Last name (sha256) | No | Name fields |
| Mobile, Mobile sha256 | No | Phone number |
| IP address, IP address (sha256) | No | Client IP address |
| User agent, Device Type, OS, OS version, Browser, Browser version | No | Device and browser fields |
| Title, Gender, DOB, Age, Language | No | Profile fields |
| Unit no, Address 1, Address 2, City, State, Zip code, Country | No | Address fields |
See Rokt's Events API for the event and conversion type values they accept.
Sync behavior
| Behavior | What happens |
|---|---|
| When it runs | GrowthLoop sends the sync as a batch on the next successful run. |
| Insert | GrowthLoop adds new conversion events. Syncs do not update or remove previously uploaded events. |
| Match | Map Event Id, Event Type, and Event Time. |
| Audience membership | This sync does not create a Rokt custom audience. |
| Deletes | GrowthLoop does not delete previously uploaded conversion events. |
Rows without Event Id, Event Type, or Event Time fail.
Confirm the export was successful
When the run finishes, confirm you can use the data in Rokt.
- Conversion sync: Confirm the conversion events on the connected account.
This workflow does not create a targeting audience.
In GrowthLoop, confirm the sync appears in the Syncs table. See Syncs for more information.
Congrats on successfully exporting to Rokt Conversions!
Troubleshooting
These are the issues we see most often. You can always email us at [email protected] for help.
| Problem | Cause | Resolution |
|---|---|---|
| You do not have a Rokt destination | The Ads destination is not connected yet | Connect Rokt first |
| A conversion sync fails with an auth error | App Id or App Secret is missing or wrong | Edit the Rokt destination and paste credentials from Generate Personal API Credentials |
| A conversion sync fails | Event Id, Event Type, or Event Time is missing | Map all three required fields |
| A sync did not change Audiences | This sync writes conversion events, not custom audiences | Export an audience on Rokt to create or update a custom audience |
Updated about 2 hours ago