Snapchat Custom Audience
Overview
Section titled “Overview”Signals syncs customer segments from your own systems into Snapchat, so campaigns can target or exclude people you have already identified.
Signals watches the source for the attributes that define each segment and keeps the matching audience in Snapchat in step with it, rather than uploading a list once and leaving it to go stale.
Supported sources
Section titled “Supported sources”Sources supported by Snapchat Custom Audience
| Category | Supported |
|---|---|
| API | |
| CRM | |
| Database | |
| File & storage | |
| Warehouse |
Prerequisites
Section titled “Prerequisites”Before connecting Snapchat Custom Audience, make sure you have:
- A Snapchat Ads account.
- A Snapchat Business Manager account with access to the ad account the audience should live in.
- A Datahash Studio account with the target project selected.
- A source connected in the same project with the Integration Type set to Audience.
Authentication
Section titled “Authentication”In Studio, open Destinations, find Snapchat, and click the Custom Audience tile. This connector uses single sign-on, so there is no key or token to manage.
- Click Sign in with Snapchat.
- Complete the Snapchat consent screen and approve the requested permissions.
- Click Finish.
Sign in with an account that already has access to the ad account the audience should live in. Datahash reads as that account.
Configuration
Section titled “Configuration”There is nothing to configure. Signing in completes the setup, because this connector takes everything it needs from two places you have already set: the ad account comes from the Snapchat account you authenticated with, and the audience comes from the Audience name field you map under Data & identifiers.
That makes the signed-in account the only way to control where the audience lands. If the audience needs to sit in a different ad account, sign in again with an account that has access to that one.
Manage instance
Section titled “Manage instance”To change the instance, open it from Manage Instances, use the menu in the top right and choose Edit, update the fields and click Finish. Cancel keeps the previous configuration running, so updates apply only after you finish.
Data & identifiers
Section titled “Data & identifiers”Send identifiers already hashed where you can. Plain text also works: they are normalized and SHA-256 hashed before they reach Snapchat.
Required
Section titled “Required”| Field | When it is required |
|---|---|
| Audience name | Always. It is what determines which audience in Snapchat a record lands in. |
| Last modified date | Always. It is how Signals knows a record has changed and the audience needs updating. |
| Email address | Always. Hashed. |
| Phone number | Always. Up to three numbers per person, and at least one is required. Hashed. |
Optional
Section titled “Optional”| Field | Format |
|---|---|
| Email address 2 and 3 | Two further addresses per person. Hashed. |
| Mobile advertiser ID | Accepted in place of email and phone where neither is available. Hashed. |
| IDFA | As above, for Apple devices. Hashed. |
The match depends on email, phone and mobile advertising ID.
Best practices
Section titled “Best practices”- Send up to three email addresses and three phone numbers where you hold them. Contact points are the main lever on match rate for this destination.
- Keep formatting clean at source: lowercase email, no stray whitespace, phone as digits. A badly formatted value hashes to something that will never match.
- Make sure the last modified date changes when a record changes, or the audience will drift out of date without anything appearing to be wrong.
- Keep the audience name stable. Changing it creates a second audience rather than renaming the first.
- Verify in Snapchat Ads Manager under Audiences, and expect a delay before an audience is large enough to be usable for targeting.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”The consent screen does not complete. Confirm the account you are signing in with has access to the ad account.
The audience appears but stays empty. Confirm the source is connected in the same project with the Integration Type set to Audience, and that the audience name field is populated.
Match rates are low. Add more contact identifiers per person and check formatting at source.
Records land in the wrong audience. The audience name values on the source are not what you expected. They are the only thing that decides which audience a record joins.
The audience is not updating. The last modified date is probably not changing when records change.
Sync stopped. The sign-in grant may have been revoked, or the authenticating user may have lost access to the ad account. Reconnect.