Snap Audiences (Actions) Destination

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.

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.

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.

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.

   Expand image

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.

Snap Audiences (Actions) has the following presets

Build your own Mappings. Combine supported triggers with the following Snap Audiences-supported actions:

• Sync Audience

Sync Engage Audiences to Snap

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

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.

Mobile Advertising IDs need to be correctly configured using ID Sync. Note the underscores for android_idfa and ios_idfa.

Expand image

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.

Expand image

. Again, note the underscores for android_idfa and ios_idfa.

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.

The status is shown in the Event Delivery tool. When you view the audience, open the side bar which directs you to Event Delivery.

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an 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.

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