# Snap Audiences (Actions) Destination

> \[!IMPORTANT]
>
> This feature is in active development and may change before general availability.

## Destination Info

* Accepts [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Snap 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.**

[Snap Ads](https://forbusiness.snapchat.com/advertising/targeting/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) provides a way to target advertisements to a global audience and drive meaningful results.

This destination is maintained by Segment. For any issues with the destination, [contact the Segment support team](mailto:friends@segment.com).

> \[!WARNING]
>
> This page is about the [**Actions-framework**](/docs/segment/connections/destinations/actions/) Snap Ads Segment destination. See the [Snapchat Audience destination documentation](/docs/segment/connections/destinations/catalog/snapchat-audiences/) for the **non-Actions** Snap Ads destination.
>
> **Both destinations receive data from Segment**.

## Benefits of Snap Ads (Actions) vs Snapchat Audience Classic

Snap Audiences (Actions) provides the following benefits over the classic Snapchat Audience destination:

* **Multiple concurrent identifiers**. Email, phone number and Mobile Advertising IDs are supported concurrently. There's no need to select only one type of user identifier to sync with.
* **Improved match rates**. Improved match-rate when multiple identifiers per profile are synced.

## Getting started

### Create the destination and authenticate to Snap Ads

1. In Segment, go to **Engage**, and select your workspace.
2. Navigate to **Engage Settings** and select the **Destinations** tab.
3. Click **Add destination**.
4. Search for "Snap Audiences (Actions)" and configure the destination.
5. On the Snapchat Audiences configuration screen, click **Connect to Snap Audiences (Actions)**. Log in to Snapchat with an account that has access to Ads Manager. Once authenticated, confirm the connection to Segment.
6. Select the Snap Ads account to receive audience data. This account represents an advertising entity or business, and not your personal Snapchat user account. You might belong to several Ad Accounts; make sure to select the correct account. After the Ad Account is specified, the destination is active.

### Configure mappings

1. In Segment, go to **Connections > Destinations** and find the Snap Audiences (Actions) Destinations you just created.
2. Click on the **Mappings** tab, then **New Mapping**, then the **Sync Audience** Action. There should be no need to edit any of the Mapping fields, so click the **Next** button.
3. Give the action a name, then click **Save and Enable**.

### Connect and sync your audience

Next, add the Snapchat Audiences Destination to an existing Engage Audience.

1. Navigate to **Engage > Audiences**. Find and click on the Audience you'd like to sync.
2. Click **Add destination**.
3. The configured Snap Audiences (Actions) destination should appear in the **Send as User List** category of available destinations.
4. Provide values in the **Audience Name** and **Audience Description** fields.
5. Ensure that **track** is selected under **Connection Settings**. You can ignore the **Send Mobile IDs** as you can configure Mobile Advertising IDs in the next step.
6. Click on **Customized Setup** and add the identifiers you'd like to sync with. These should include one or more of: `email`, `phone`, `android.idfa`, `ios.idfa`. If you choose to sync `android.idfa` and/or `ios.idfa`, you must update the destination mappings to use underscores: `android_idfa` and `ios_idfa`.

   ![Image showing how to configure identifiers using ID Sync.](https://docs-resources.prod.twilio.com/cd65ae1980216abf722408d6cd64b1b18d005dbbff722609ef3633cfea733012.png)
7. Click **Save** then **Add 1 Destination**.

Your audience should now be configured to sync to Snap Ads. The initial synchronization of audience data may take several hours, depending on the size of the audience. Once the initial sync occurs, you'll notice a new audience in the Snap Ads dashboard.

## Destination Settings

| Field         | Description                   | Required | Type   |
| ------------- | ----------------------------- | -------- | ------ |
| Ad Account ID | The ID of the Snap Ad Account | Yes      | string |

## Available Presets

Snap Audiences (Actions) has the following presets

| Preset Name          | Trigger                                        | Default Action |
| -------------------- | ---------------------------------------------- | -------------- |
| Sync Engage Audience | Event type = "track", Event  type = "identify" | Sync Audience  |

## Available Actions

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

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

* [Sync Audience](#sync-audience-6)

### Sync Audience

Sync Engage Audiences to Snap

Sync Audience is a **Cloud** action. The default Trigger is `type = "track"`

| Field                 | Description                                                                                                                                                                                                                                                                | Required | Type   |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------ |
| Phone                 | If using phone as the identifier an additional setup step is required when connecting the Destination to the Audience. Please ensure that 'phone' is configured as an additional identifier in the Audience settings tab.                                                  | No       | STRING |
| Email                 | The user's email address.                                                                                                                                                                                                                                                  | No       | STRING |
| Mobile Advertising ID | If using Mobile Ad ID as the identifier an additional setup step is required when connecting the Destination to the Audience. Please ensure that 'ios.idfa' is configured to 'ios\_idfa' and 'android.idfa' is configured to 'android\_idfa' in the Audience settings tab. | No       | STRING |

## FAQs

#### Which identifiers types are supported?

The Snap Audience (Actions) destination supports syncing using `email`, `phone` number and `Mobile Advertising IDs`. `email` is the default identifier; other identifiers should be configured using [ID Sync](/docs/segment/engage/trait-activation/id-sync/).

#### Why aren't Mobile Advertising IDs syncing properly?

Mobile Advertising IDs need to be correctly configured using [ID Sync](/docs/segment/engage/trait-activation/id-sync/). Note the underscores for `android_idfa` and `ios_idfa`.

![Customized setup for Snap Audiences configuring Android and iOS IDFA with ID Sync.](https://docs-resources.prod.twilio.com/48738c638f3d7297d84120d945ec9129ec298b69a328a95173ba2769e2d07f36.png)

The field mapping for the **Mobile Advertising ID** field must also be correct. By default, it'll be configured as follows when the Mapping is created.

![Coalesce function with Primary Value and Fallback Value defined.](https://docs-resources.prod.twilio.com/9db89af37435d2b6276dcc74d4bc3c130a9733e7958f1e09641793b85e7ab404.png)

. Again, note the underscores for `android_idfa` and `ios_idfa`.

#### Why can't I select our Ads Account during the destination setup?

Ensure the following criteria are met:

* Your personal Snapchat login has appropriate permissions within your business. Snapchat Account Admin or Data Manager permissions are required to configure and add audiences.
* Your Snap Ads account is in `Active` status.

#### How do I view the sync status?

The status is shown in the Event Delivery tool. When you view the audience, open the side bar which directs you to [Event Delivery](/docs/segment/getting-started/06-testing-debugging/#event-delivery).

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to Snap Audiences (Actions)  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field         | Description                   | Required | Type   |
| ------------- | ----------------------------- | -------- | ------ |
| Ad Account ID | The ID of the Snap Ad Account | Yes      | string |