Skip to content

Commit 51c84bc

Browse files
committed
rokt action destination doc
1 parent d248d76 commit 51c84bc

File tree

1 file changed

+68
-0
lines changed
  • src/connections/destinations/catalog/action-rokt-audiences

1 file changed

+68
-0
lines changed
Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: Rokt Audiences Destination
3+
hide-personas-partial: true
4+
hide-boilerplate: true
5+
hide-dossier: false
6+
id:
7+
redirect_from:
8+
- "/connections/destinations/catalog/actions-rokt-audiences"
9+
---
10+
{% include content/plan-grid.md name="actions" %}
11+
12+
Rokt Audiences enables advertisers to send Segment Persona Audiences to Rokt using Rokt's Audience API.
13+
14+
By using Segment's Persona Audiences with Rokt, you can increase the efficieiny of your ad campaigns through suppression and targeting of existing or new customers.
15+
16+
## Benefits of Rokt Audiences
17+
18+
Benefits of the Rokt destination include:
19+
- **Improved email matching**: This integration creates a direct connection between Segment and Rokt for a 100% match rate of email identifiers.
20+
21+
- **Easy setup**: This destination only requires your Advertiser API key.
22+
23+
- **Batching events and support for large audiences**: This destination supports batching which enables Rokt to receive large audiences without discrepancies.
24+
25+
- **Near real time audience updates**: Actions destination helps Rokt receive real-time events and add or remove users from Rokt audiences appropriately.
26+
27+
## Getting Started
28+
29+
### Prerequisites:
30+
31+
Before connecting to the Rokt Audiences destination, you must have an account with Rokt and receive your API key.
32+
33+
### To Add the Rokt Audiences Destination:
34+
35+
1. From your Segment workspace, go to **Connections > Catalog** and click **Destinations**.
36+
37+
2. Search for **Rokt Audiences** in the Destinations Catalog and select the destination.
38+
39+
3. Click **Configure Rokt Audiences**.
40+
41+
4. Select the space in Engage to use as the Source as this destination only supports sending Engage Audiences to Rokt.
42+
43+
5. On the **Settings** tab, name your destination. For example, `Rokt audiences – <audience name>`.
44+
45+
6. Enter your Rokt API key.
46+
47+
7. Click **Save Changes**.
48+
49+
8. In the **Mappings** tab, click **New Mapping** and select **Add Users to Audience**. Don't change any defaults.
50+
51+
9. Under the **Configure actions fields**, set **Enable Batching** to *Yes* and click **Save**.
52+
53+
7. Repeat steps 8 and 9 for **Remove Users from Audience**.
54+
55+
8. **Enable** both mappings.
56+
57+
9. Go to the **Settings** tab and **Enable** the destination.
58+
59+
10. Select your space, and navigate to **Engage > Audiences**. Select the source audience that you want to send to your Rokt Audiences destination.
60+
61+
11. Click **Add Destinations** and select the Rokt Audience destination you created. In the settings that appear on the right-hand side, toggle the **Send Track** option on and **Send Identify**. Click **Save**.
62+
63+
Your Rokt destination is now ready to receive audiences, and your Persona audiences are now accessible in your Rokt Advertiser dashboard. Be aware, it can take 12-24 hours for the first sync when the number email identifies are in the millions.
64+
65+
> warning ""
66+
> You can connect **ONE** Engage audience to a single instance of Rokt Audience destination. If you have multiple audiences, repeat the above process to create a new Rokt audience destination and connect the audience to new destination each time.
67+
68+
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)