Rokt Destination Setup Guide

Private Beta

Set up and configure Rokt as a destination in RudderStack.

3 minute read

The Rokt destination integration is currently in Private Beta, where we work with early users and customers to test new features and get feedback before making them generally available.
Reach out to Customer Success if you’re interested in enabling this destination for your workspace.

This guide helps you set up Rokt as a destination in the RudderStack dashboard. It also lists the configuration settings required to send data from the supported sources to Rokt.

Connection compatibility

Destination Information
Status: Private Beta Supported sources: Android (Java) , Android (Kotlin) , iOS (Obj-C) , iOS (Swift) , Web, Unity, AMP , Cloud, React Native , Flutter, Cordova, Shopify Refer to it as Rokt in the Integrations object.

Connection Modes
Source	Cloud mode	Device mode	Hybrid mode
AMP
Android (Java)
Android (Kotlin)
Cloud
Cordova
Flutter
iOS (Obj-C)
iOS (Swift)
React Native
Shopify
Unity
Web

Supported Message Types
Source	Identify	Page	Track	Screen	Group	Alias	Record	AudienceList
Cloud mode
Supported sources

Setup

In your RudderStack dashboard, add a source. Then, from the list of destinations, select Rokt.

Connection settings

Setting	Description
Destination name	Assign a name to uniquely identify the destination.
Rokt account	Select or create a Rokt account.

To create an account, select the API Key connection method and configure the following fields:

Setting	Description
Account name	Enter a name to identify the Rokt account in RudderStack, for example, `Rokt production`.
Server to Server Key	Enter the Server to Server Key from your mParticle Custom Feed.
Server to Server Secret	Enter the Server to Server Secret from your mParticle Custom Feed. RudderStack stores this as a secret and does not display it again.

Rokt event delivery connects through an mParticle Custom Feed. Find the server-to-server credentials in mParticle under Setup > Inputs > Feeds after saving your Custom Feed.

Event mapping settings

Use the event mapping settings to map RudderStack track events to Rokt conversion types.

Setting	Description
Event mappings	Map RudderStack `track` event names to Rokt conversion types. You can configure only one Rokt conversion type per RudderStack event name.
RudderStack event name	Enter the source `track` event name you want to map, for example, `Order Completed`.
Rokt conversion type	Enter the Rokt conversion type that should receive the event, for example, `purchase`.

Only events with a mapping are delivered to Rokt. Events without a matching RudderStack event name are dropped.

Setting	Description
Consent management settings	Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. Rokt supports Custom, iubenda, Ketch, and OneTrust providers. For the Custom provider, also choose whether all configured categories (AND) or at least one category (OR) must have consent. See Consent Management in RudderStack for more information on this feature.

Setting

Description

Consent management settings

Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. Rokt supports Custom, iubenda, Ketch, and OneTrust providers. For the Custom provider, also choose whether all configured categories (AND) or at least one category (OR) must have consent.

See Consent Management in RudderStack for more information on this feature.

Next steps

Send events in cloud mode