Snapchat Conversions Connector Setup Guide
This article describes how to set up the Snapchat Conversions connector.
How it works
The Snapchat Conversions connector uses the Snap Conversions API. The Snap Conversions API is a structured, privacy-centric interface that allows you to directly pass web, app, and offline events to Snap via a Server-to-Server (S2S) integration. This API supports similar event tracking as the Snap Pixel and broken out into the Device Type used to make the conversion as well. This trigger allows for the Snap App ID to be used for mobile conversions and the Pixel ID for web and offline conversion events.
Snap Conversions API can be deployed standalone or in-conjunction with the client side Snap Pixel.
For more information about Snap’s Conversions API, see the Conversion API article in the Snapchat documentation.
API Information
This connector uses the following vendor API:
- API Name: Snapchat Marketing API - Conversion API
- API Version: v2
- API Endpoint:
https://tr.snapchat.com/v2/conversion
Prerequisites
- After adding the connector, you must invite asintegrations@tealium.com to your Snapchat Business manager with the Member role and assign to applicable Ad Account with the Data Manager role.
This step may take up to three working days for approval. You can confirm whether the invitation has been accepted by viewing the users in your Snapchat Ads account.
For additional information, see: Manage Members and Roles.
Considerations
- To unlock campaign optimization, we recommend that you send events as soon as they occur, ideally within an hour of the event occurring.
- We strongly recommend passing data in real-time. By doing so, you will see your campaign-driven results more quickly and ensure your bids are staying competitive with current marketplace demand.
- Conversions API requests are tied to unique identifiers that link server events back to your Snapchat ad account. We use your Pixel ID for web and offline events and your Snapchat App ID for app events.
Batch Limits
This connector uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 2000
- Max time since oldest request: 10 minutes
- Max size of requests: 2 MB
Deduplication
The Snap Conversions API can be used as a standalone API or alongside other Snapchat solutions. To minimize signal loss and create more efficient results, we recommend passing the same events through the Snap Conversion API that you have configured in your Snap Pixel.
Snap Conversions API shows only Event Deduplication if the following conditions are met:
- Snap App ID and/or Pixel ID has multiple sources (API, SDK, etc.)
- Events are for the same conversion type (Web, App, or Offline)
- The selected event is added on 2 or more sources
Tealium has deduplication recommendations based on your integration configuration:
- Single source redundancy - The duplication of events sent in the same integration.
If you send the conversion multiple times through the same integration source, we highly recommend passing consistent information. - Cross source redundancy - The duplication of events sent from multiple integrations.
When sending data from multiple integrations, we recommend sending redundant data to ensure the best optimization, targeting, and measurement capabilities.
Depending on your deduplication use case, use the following parameters:
- Client dedup ID - Deduplicates unique events for web and offline channels. Allows for a 48 hour deduplication window.
- Transaction ID - Eligible for deduplicating purchase events for all channels (web, mobile, and offline). Allows for a 30 day deduplication window.
- Mobile Ad ID - Use a shared device identifier like AAID or hashed IDFV for unique event deduplication.
For more information, see the Deduplication section of the Snap Conversions API documentation.
Automatic deduplication
When the Automatic Deduplication value is populated, the connector looks for the corresponding event attribute. You are no longer required to add an Client Dedup ID if this section is populated and you are using Tealium iQ. However, the following approach may still be needed when using EventStream without Tealium iQ.
The connector order of operations is as follows:
- If Automatic Deduplication is populated, and the value is found in the data layer, (for example,
6V5xX1T0n9pC42luElKD
) this value supersedes anything mapped in Client Dedup ID. - If Automatic Deduplication is populated, but it cannot find the tag ID version, but it can find the legacy version (with no ID attached), that value is used (for example,
6V5xX1T0n9pC42luElKD
). - If Automatic Deduplication is populated, but the value isn’t found, the mapped Client Dedup ID is used, if it is populated.
Connector Actions
Action Name | AudienceStream | EventStream |
---|---|---|
Send Conversion | ✓ | ✓ |
Configure Settings
Go to the Connector Marketplace and add a new connector. See the Connector Overview for general instructions on how to add a connector.
After adding the connector, configure the following settings:
- Long Lived Token: This method of authentication does not need the 3-legged OAuth flow and does not expire. For more information, see Snapchat: Static Long Lived Tokens
Action Settings - Parameters and Options
Click Next or go to the Actions tab. This is where you configure connector actions.
This section describes how to set up parameters and options for each action.
Action - Send Conversion
Parameters
Parameter | Description |
---|---|
Event Type |
|
Event Conversion Type |
|
Pixel ID |
|
App ID |
|
Snap App ID |
|
Event Tag |
|
Timestamp |
|
Description |
|
Number Items |
|
Currency |
|
Transaction ID |
|
Level |
|
Client Dedup ID |
|
Data Use |
|
Search String |
|
Page Url |
|
Sign Up Method |
|
Item Category |
|
Item ID |
|
Price |
|
Email Address (apply SHA256 hashed) |
|
Email Address (already SHA256 hash) |
|
Mobile Ad ID (already SHA256 hashed) |
|
Mobile Ad ID (apply SHA256 hash) |
|
Phone Number (already SHA256 hashed) |
|
Phone Number (apply SHA256 hash) |
|
IP Address (already SHA256 hashed) |
|
IP Address (apply SHA256 hash) |
|
Vendor Identifier (already SHA256 hashed) |
|
Vendor Identifier (apply SHA256 hash) |
|
User Agent |
|
Automatic Deduplication
Parameter | Description |
---|---|
Tealium iQ Tag ID | When the Tealium iQ Tag ID is provided, the connector automatically looks for the Client Dedup ID value that is sent from Tealium iQ. |
This page was last updated: November 9, 2022