What TSO does with Snapchat
- Conversions API: conversions with click ID, Snap cookie and hashed contact details, with the same event ID as the pixel.
- Snap Pixel: loaded through the TSO script if you like.
More on the conversion API page.
Conversions server-side to Snap through the Conversions API, deduplicated with the Snap Pixel.
| Field | Meaning |
|---|---|
| Event | The conversions you allow; a lead goes as CUSTOM_EVENT_1. |
| Event ID | The same ID as the pixel or tag, so each event counts once. |
| Click ID and Snap cookie | From the ad click and the Snap Pixel. |
| Contact details | Email, phone and name, normalized and hashed with SHA-256. |
| Value and currency | For payments and won deals. |
More on the conversion API page.
| Problem | Solution |
|---|---|
| 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. |
No, there is no cost import for Snapchat. Conversions go to Snap through the Conversions API and the pixel.