mParticle is a third-party customer data platform tool that clients can use to send custom audiences to Rokt. These files will be loaded into the Rokt Data Platform and will be functionally identical to custom audience files delivered via other pathways such as secure file transfer, API, or UI upload.
Sending custom audiences from mParticle to Rokt
All Rokt accounts are enabled by default to receive data from mParticle. You can configure your data deliveries directly from mParticle’s UI with two main steps.
- Configure Rokt as a destination for your account.
- Connect your audience(s) to the destination created in step 1.
For more information, you can read the mParticle documentation on configuring audience destinations.
Step 1: Configure Rokt as a destination in mParticle
To set up an audience delivery from mParticle to Rokt, first search for Rokt in mParticle’s directory.
Click on the Rokt tile to start an Audience Configuration.
Enter the following information:
- Configuration Name: Defined by you. This is how you identify the integration in other parts of the mParticle UI.
- API Key: Ask your Rokt account manager for your unique API key.
- Rokt Account ID: Ask your Rokt account manager for your account ID.
Note: If you have multiple Rokt accounts (e.g., one account for U.S. campaigns and one account for Australian campaigns), you need to set up a separate mParticle audience configuration for each account.
Step 2: Deliver your audience to Rokt
Once Rokt has been configured as an audience destination, navigate to the Audiences tab, click into the audience(s) you would like to send to Rokt, and connect Rokt as an output.
Once the integration has been set to active, mParticle will begin pushing your audience data over to Rokt. It will be visible in the Rokt UI and available for use in under 24 hours. Furthermore, Rokt continually processes membership changes to that audience. As users are added and removed in mParticle, they are also automatically added and removed in the Rokt platform.
Once the data arrives in the Rokt platform it is available as a custom audience. The audience name in the Rokt platform is the same as the audience name configured in the mParticle UI (Note: The audience name is not the same as the configuration name).
Anything else to know about this integration?
The mParticle integration with Rokt is based on email addresses. Rokt cannot ingest mobile device IDs, cookies, or other types of identifiers. Therefore you can only send custom audiences that use an email address as an identifier. If you try to integrate an audience consisting only of cookies or device IDs, Rokt will not receive any data.
Also, while mParticle supports other types of integrations, Rokt currently only supports custom audiences. If you are interested in other types of integrations with mParticle, please contact your Rokt account manager.