Connect Snap Ads
Connect a Snap ad account with an OAuth app and a refresh token, add a Snap Pixel, and send conversions through the Conversions API.
TrueEngage sends mapped events to Snap as conversions, through the Snap Conversions API. You connect by pasting a set of credentials from an OAuth app you own. There is no Snap sign-in screen, and Snap takes events only: audiences are not supported.
Before you start
- You need Create and manage on Ad platforms.
- You need a Snap ad account, and a Snap user who can use it.
- To send conversions you need a Snap Pixel in that account.
- You need an OAuth app in Snap Business Manager. If Snap tells you the app cannot use the Marketing API, ask your Snap contact to enable it for the app.
Find the values
| Value | Where to find it |
|---|---|
| Ad account ID | In Snap Ads Manager or Business Manager, open Ad Accounts and choose the account. Use the ad account ID, not the organization ID |
| Pixel ID (optional) | In Snap Ads Manager, open Events Manager and choose your Snap Pixel. Without it the connection saves, but no events are sent |
| Client ID | In Snap Business Manager, open Business Details, then OAuth Apps. Create an app, or open an existing one. The client ID is listed with the app |
| Client secret | Snap shows it once, when you create the app. If it was not saved, create a new secret for the app |
| Refresh token | Authorise your OAuth app once, as a user who has access to the ad account, with the Marketing API scope (snapchat-marketing-api). Exchange the code Snap returns for tokens, and keep the refresh token |
TrueEngage uses the refresh token to get fresh access tokens itself. You never paste an access token.
Connect
- Open Data, then Ad platforms.
- On the Snap Ads card, select Connect with credentials.
- Enter a Name, the Ad account ID and, if you have it, the Pixel ID. Select Continue.
- Enter the Client ID, Client secret and Refresh token. The secret and the token fields hide what you paste.
- Select Connect and check.
- Read the checks, then select Open connection.
TrueEngage verifies the credentials while it saves them. If Snap refuses them, the dialog stays on the credentials step and says why, and nothing is saved. Fix the value and select Connect and check again.
TrueEngage stores the client secret and refresh token encrypted and never shows them again.
Read the checks
| Check | Passes when |
|---|---|
| Access to the ad account | Snap accepts the credentials and the ad account can be read |
| Test event accepted | Snap's validation endpoint accepts a test event for your pixel. Shown only when a Pixel ID is set |
If a check fails, the message under it says what to change. See Ad platform error codes for the codes.
What is sent
- Events go to your Snap Pixel through the Conversions API.
- People are matched on a hashed email and a hashed phone number. TrueEngage hashes them with SHA-256 before they leave. Nothing else identifies the person, so users with no email and no phone are skipped.
- Each event carries the event ID you set on the mapping. Snap uses it to drop duplicates.
- Snap accepts events up to 28 days old. TrueEngage queues only events inside that age.
- Snap Ads has no audiences. The connection has no Audiences tab.
Choose which events to send in Send events as conversions. Snap's standard event names, such as PURCHASE and SIGN_UP, are offered as destinations. A PURCHASE needs a value.
Replace credentials
When Snap stops accepting the credentials, the connection shows Reconnect needed. Open it, select Enter new credentials, and paste only the values that changed. Leave a field empty to keep what is stored. TrueEngage checks the new values before it resumes sending. See Fix connection errors and reconnect.
Common problems
- Snap does not accept these credentials. Check that the client ID, client secret and refresh token come from the same OAuth app, and that the refresh token has not been revoked. Authorise the app again to get a new refresh token.
- The ad account cannot be reached. Check the ad account ID, and that the user who authorised the app has access to that account.
- Snap is busy. Wait a few minutes and check again. Snap rate limits requests.
- The test event is not accepted. Check that the pixel belongs to this ad account.
What happens next
Was this page helpful?