Skip to content

Snapchat Conversions API with TSO

Conversions server-side to Snap through the Conversions API, deduplicated with the Snap Pixel.

What is transferred

FieldMeaning
EventThe conversions you allow; a lead goes as CUSTOM_EVENT_1.
Event IDThe same ID as the pixel or tag, so each event counts once.
Click ID and Snap cookieFrom the ad click and the Snap Pixel.
Contact detailsEmail, phone and name, normalized and hashed with SHA-256.
Value and currencyFor payments and won deals.

Setup

  1. 01Connect the Snap PixelThe pixel ID is in Snapchat Events Manager at the pixel.
  2. 02Create a tokenThe Conversions API token is created by an organization admin in Ads Manager under "Business Details" → "Conversions API Tokens".
  3. 03Set the rulesDecide which data goes to Snapchat and which conversions count.
  4. 04TestWith a test code the events go to Snap as test events and appear in Snapchat Events Manager.
  5. 05Load the pixel (optional)Load the Snap Pixel through the TSO script if the page doesn't have its own yet.

Common problems and solutions

ProblemSolution
Contact or deal events don't arrive.Events Snap doesn't know (e.g. contact or deal stages) aren't sent. A lead goes as CUSTOM_EVENT_1.
The token can't be created.Only an organization admin can do that in Ads Manager.
Events are counted twice.Don't load the pixel or tag through TSO as well if the page already has its own.

Frequently asked questions

Are costs imported from Snapchat?

No, there is no cost import for Snapchat. Conversions go to Snap through the Conversions API and the pixel.

More integrations

Find out which ads pay off.

Hosted in Germany · Built in Austria