Skip to content

Commit 56dd182

Browse files
committed
build: flip destination to public
1 parent 93a90c6 commit 56dd182

File tree

1 file changed

+8
-8
lines changed
  • src/connections/destinations/catalog/actions-rokt-audiences

1 file changed

+8
-8
lines changed

src/connections/destinations/catalog/action-rokt-audiences/index.md renamed to src/connections/destinations/catalog/actions-rokt-audiences/index.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,20 +3,20 @@ title: Rokt Audiences (Actions) Destination
33
hide-personas-partial: true
44
hide-boilerplate: true
55
hide-dossier: false
6-
private: true
7-
hidden: true
6+
private: false
7+
hidden: false
88
id: 643697130067c2f408ff28ca
99
---
1010
{% include content/plan-grid.md name="actions" %}
1111

1212
Rokt Audiences (Actions) destination enables advertisers to send Segment Persona Audiences to Rokt using Rokt's Audience API.
1313

14-
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.
14+
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.
1515

1616
## Benefits of Rokt Audiences (Actions)
1717

1818
Benefits of the Rokt Audiences (Actions) destination include:
19-
- **Improved email matching**: This integration creates a direct connection between Segment and Rokt for a 100% match rate of email identifiers.
19+
- **Improved email matching**: This integration creates a direct connection between Segment and Rokt for a 100% match rate of email identifiers.
2020

2121
- **Easy setup**: This destination only requires your Advertiser API key.
2222

@@ -45,11 +45,11 @@ To add the Rokt Audiences (Actions) destination:
4545

4646
6. Enter your Rokt **API key**.
4747

48-
7. Click **Save Changes**.
48+
7. Click **Save Changes**.
4949

5050
8. In the **Mappings** tab, click **+ New Mapping** and select **Add Users to Audience**. Don't change any defaults.
5151

52-
9. Under the **Configure actions fields**, set **Enable Batching** to *Yes* and click **Save**.
52+
9. Under the **Configure actions fields**, set **Enable Batching** to *Yes* and click **Save**.
5353

5454
7. Repeat steps 8 and 9 for **Remove Users from Audience**.
5555

@@ -59,9 +59,9 @@ To add the Rokt Audiences (Actions) destination:
5959

6060
10. Select your space, and navigate to **Engage > Audiences**. Select the source audience that you want to send to your Rokt Audiences (Actions) destination.
6161

62-
11. Click **Add Destinations** and select the Rokt Audience (Actions) 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+
11. Click **Add Destinations** and select the Rokt Audience (Actions) destination you created. In the settings that appear on the right-hand side, toggle the **Send Track** option on and **Send Identify**. Click **Save**.
6363

64-
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.
64+
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.
6565

6666
> warning ""
6767
> 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.

0 commit comments

Comments
 (0)