# Rokt Audiences (Actions) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Rokt Audiences (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

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 Rokt Audiences (Actions)

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.

## Getting started

### Prerequisites:

Before connecting to the Rokt Audiences destination, you must have an account with Rokt and receive your API key.

### Add the destination:

To add the Rokt Audiences (Actions) destination:

1. From your Segment workspace, go to **Connections > Catalog** and select the **Destinations** tab of the catalog.
2. Search for **Rokt Audiences (Actions)** and select the destination.
3. Click **Add destination**.
4. Select the space in Engage to use as the Source as this destination only supports sending Engage Audiences to Rokt.
5. On the **Settings** tab, enter the name of your destination. For example, `Rokt audiences – <audience name>`.
6. 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](https://docs.rokt.com/developers/integration-guides/rokt-ads/account-id/#account-id).
7. Click **Save Changes**.
8. 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.
9. Go to the **Settings** tab and select the toggle to **Enable** the destination.
10. Select your space, and navigate to **Engage > Audiences**. Select the source audience that you want to send to your Rokt Audiences (Actions) destination.
11. Click **Add Destinations** and select the Rokt Audience (Actions) destination you created.
12. In the settings that appear on the right-hand side, toggle on the **Send Track** and **Send Identify** option.
13. Select **Default Setup**.
14. 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.

## Destination Settings

| Field           | Description                                  | Required | Type     |
| --------------- | -------------------------------------------- | -------- | -------- |
| Rokt Account ID | Rokt ID assigned to your particular account. | Yes      | string   |
| Rokt public key | Rokt public key, starts with \`rpub-\`       | Yes      | string   |
| Rokt secret key | Rokt secret key, starts with \`rsec-\`       | Yes      | password |

## Available Presets

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 |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Rokt Audiences-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Sync Engage Audience to Rokt](#sync-engage-audience-to-rokt)

### Sync Engage Audience to Rokt

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"`

| Field                       | Description                                                                                                                                  | Required | Type    |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- |
| Custom Audience Name        | Name of custom audience list to which emails should added/removed                                                                            | Yes      | STRING  |
| Segment Computation Action  | Segment computation class used to determine if action is an 'Engage-Audience'                                                                | Yes      | STRING  |
| Email                       | User's email address to be included/excluded from the custom audience.  One of either email\_sha256 or email must be specified.              | No       | STRING  |
| Email SHA256                | User's SHA256-hashed email address to be included/excluded from the custom audience. One of either email\_sha256 or email must be specified. | No       | STRING  |
| traits or properties object | Object which will be computed differently for track and identify events                                                                      | Yes      | OBJECT  |
| enable batching to rokt api | Set as true to ensure Segment infrastructure uses batching when possible.                                                                    | No       | BOOLEAN |