Rokt Audiences (Actions) Destination
Rokt Audiences (Actions) destination enables advertisers to send Segment Persona Audiences to Rokt using Rokt's Audience API.
By using Segment's Persona Audiences with Rokt, you can increase the efficiency of your ad campaigns through suppression and targeting of existing or new customers.
Benefits of the Rokt Audiences (Actions) destination include:
- Improved email matching: This integration creates a direct connection between Segment and Rokt for a 100% match rate of email identifiers.
- Easy setup: This destination only requires your Advertiser API key.
- Batching events and support for large audiences: This destination supports batching which enables Rokt to receive large audiences without discrepancies.
- Near real-time audience updates: The actions destination helps Rokt receive real-time events and add or remove users from Rokt audiences appropriately.
Before connecting to the Rokt Audiences destination, you must have an account with Rokt and receive your API key.
To add the Rokt Audiences (Actions) destination:
- From your Segment workspace, go to Connections > Catalog and select the Destinations tab of the catalog.
- Search for Rokt Audiences (Actions) and select the destination.
- Click Add destination.
- Select the space in Engage to use as the Source as this destination only supports sending Engage Audiences to Rokt.
- On the Settings tab, enter the name of your destination. For example,
Rokt audiences – <audience name>. - Enter your RPub, RSec, and Account id values in the integration. Your Rokt account manager can share RPub/RSec values with you. Rokt Account ID can be found by following instructions here.
- Click Save Changes.
- In the Mappings tab within the Rokt Audience destination, click + New Mapping and select Sync Engage Audience to Rokt under the "Actions" tab. Don't change any defaults.
- Go to the Settings tab and select the toggle to Enable the destination.
- Select your space, and navigate to Engage > Audiences. Select the source audience that you want to send to your Rokt Audiences (Actions) destination.
- Click Add Destinations and select the Rokt Audience (Actions) destination you created.
- In the settings that appear on the right-hand side, toggle on the Send Track and Send Identify option.
- Select Default Setup.
- Click Save in the top right corner.
Your Rokt Audiences (Actions) destination is now ready to receive audiences, and your Persona audiences are now accessible in your Rokt Advertiser dashboard. Keep in mind that it can take 12-24 hours for the first sync when the number of email identifies are in the millions.
Warning
You can only connect one Engage audience to a single instance of the Rokt Audience (Actions) destination. If you have multiple audiences, repeat the above process to create a new Rokt Audience (Actions) destination and connect the audience to a new destination each time.
Rokt ID assigned to your particular account.
Rokt public key, starts with rpub-
Rokt secret key, starts with rsec-
Rokt Audiences (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Sync Engage Audience to Rokt | Event type = "track", Event type = "identify" | Sync Engage Audience to Rokt |
Build your own Mappings. Combine supported triggers with the following Rokt Audiences-supported actions:
Mapping limits per destination
Add/Remove users from Rokt custom audience list. Both identify() and track() calls are supported
Sync Engage Audience to Rokt is a Cloud action. The default Trigger is type = "track" or type = "identify"
Name of custom audience list to which emails should added/removed
Segment computation class used to determine if action is an 'Engage-Audience'
Optional
User's email address to be included/excluded from the custom audience. One of either email_sha256 or email must be specified.
Optional
User's SHA256-hashed email address to be included/excluded from the custom audience. One of either email_sha256 or email must be specified.
Object which will be computed differently for track and identify events
Optional
Set as true to ensure Segment infrastructure uses batching when possible.