The Snapchat Conversion API integration is a server-to-server integration that allows advertisers to pass web, app, and offline events from mParticle directly to Snap. Data shared through the Snapchat Conversions API is processed similarly to events passed through the Snap Pixel or App Ads Kit (SDK). By passing events, advertisers can access post-view and post-swipe campaign reporting to measure performance and incrementality. Depending on the data shared and timeliness of integration, it’s also possible to use events passed through the Conversions API for campaign optimization, ad targeting and measurement of conversions that resulted from your Snapchat campaigns.
Conversions API Token: This is Snap’s new static long lived token used for authentication. To find your Conversions API Token, go to the Business Details view on your Snap dashboard. You will see a section called Conversions API Tokens. Please note that you must be an Organization Admin to view this section of the page.
Snap App ID: In order to forward
MOBILE_APP events you will need your Snap App ID. To find your Snap App ID, go to the Apps view on your Snap Ads dashboard. Click on an App to see the App Details view. Your Snap App ID is labeled App ID.
iOS App ID: When setting up a connection via iOS, you will need your iOS App ID. To find your iOS App ID, go to the Apps view on your Snap Ads dashboard. Click on an App to see the App Details view. Your iOS App ID is labeled iOS App ID.
Android App URL: When setting up a connection via Android, you will need your Android App URL. To find your Android App URL, go to the Apps view on your Snap Ads dashboard. Click on an App to see the App Details view. Your Android App URL is labeled Android App URL.
Pixel ID: In order to forward
OFFLINE events you will need your Pixel ID. To find your Pixel ID, go to the Events Manager view on your Snap Ads dashboard. You will see your Pixel’s name and directly underneath its ID.
The following set of mParticle events are supported by this integration.
mParticle supports standard event mappings for the following Snapchat event types:
|Snapchat Event||mParticle Event|
||Application State Transition with
||Application State Transition with
Incoming Commerce events to mParticle are expanded before being sent out to Snapchat.
Example: One incoming
purchase Commerce event to mParticle with three products will go out to Snapchat as three
To support refund events, Snapchat recommends using our Custom Event Mappings to set up one of Snapchat’s five custom event types and passing the refund amount as its price.
In order to support alternative Snapchat event types that don’t map one-to-one with mParticle events, we allow customers to manually configure Custom Mappings for a particular connection within our UI. This feature allows incoming mParticle events to be mapped to known Snapchat event types, including with specific attributes and outgoing parameters.
Some of the Snapchat event types that can be mapped to include:
All Snapchat event types support the properties
event_tag. Custom events support all properties. In addition, the following event types support additional properties:
For events originating from iOS with version 14.5 or greater, ATT Authorization Status is taken into account when determining whether or not to forward IDFA.
To specify ATT Authorization Status for a given user on an incoming event batch, reference our ATT Authorization Status guide.
In order to distinguish between
OFFLINE events for Snapchat, mParticle will look for a Custom Flag on each valid incoming event called
page_urlis specified, the outgoing
page_urlisn’t specified, the outgoing
The Snapchat Conversions API includes Deduplication Support through the
client_dedup_id field, based on a 48 hour window as per Snapchat. While this field can be used to account for both single and multi source redundancy, mParticle only supports single source redundancy. To facilitate this, this field is set according to the given event’s unique ID field.
mParticle sends a variety of user data fields to Snapchat for advanced matching.
|mParticle Field||Snapchat Field||Description||Required|
|event_type||event_type||Set depending on the incoming event type.||Yes|
|timestamp_unixtime_ms||timestamp||Event timestamp. This must be in millisecond resolution (ex.1455236520490)||Yes|
|user_identities.email||hashed_email||Lowercase SHA256 hash of normalized email.||Events without either email, phone number, or IP & user agent will be rejected.|
|user_identities.mobile_number, user_identities.phone_number_2, user_identities.phone_number_3||hashed_phone_number||Lowercase SHA256 hash of normalized phone number.||Events without either email, phone number, or IP & user agent will be rejected.|
|ip||hashed_ip_address||Hashed IP Address (SHA-256) of origin||Events without either email, phone number, or IP & user agent will be rejected.|
|device_info.http_header_user_agent||user_agent||Hashed IP Address (SHA-256) of origin||Events without either email, phone number, or IP & user agent will be rejected.|
|device_info.ios_advertising_id, device_info.android_advertising_id||hashed_mobile_ad_id||Lowercase SHA256 hash of normalized MAID (IDFA or AAID).||No|
|device_info.ios_idfv||hashed_idfv||Lowercase SHA256 hash of normalized IDFV.||No|
|Setting Name||Data Type||Description|
|Conversions API Token||
||Long lived token used by Snapchat for authentication.|
|Snap App ID||
||The Snap App ID associated with your app (a unique code generated in Snap Ads Manager and included in your MMP dashboard). Example:
||The mParticle User Identity type to forward as a
|Setting Name||Data Type||Platform||Description|
|Apple App Id||
||iOS||The unique iOS App Id assigned to a given Snap App. It should be numeric. Example:
|Android App URL||
||Android||The unique Android App URL assigned to a given Snap App. It should be a human interpretable string. Example:
||Web||The Pixel ID for the Ad Account in question. Example:
Was this page helpful?