Snapchat Conversions API for server-side Snap ads tracking
Snap ads can learn from every order. Trakero sends the server copy with the Snap click id and cookie, and the Pixel copy with the same id, so Snap counts one.
Illustration of the event flow
What you get
Click id and cookie
The SDK keeps the ScCid from the landing URL and the _scid cookie; both are sent with the server event.
Deduplication
Pixel client_dedup_id equals the server event_id (48 hours), and purchase transaction ids match order ids (30 days).
Where browser-only tracking loses the sale
Pick a situation your shoppers are in and watch one order take both paths.
A shopper from your Facebook ad places an order.
Illustration of what happens on shoppers' devices, not a measurement.
Set up in minutes
- 1Events Manager → your Snap Pixel: copy the Pixel ID and generate a Conversions API token.
- 2Add the Snapchat destination in Trakero.
- 3Optionally add the Snap Pixel under Browser tags.
Questions
Which events are sent?+
Page views, product views, searches, add to cart, checkout, payment info, purchases, sign-ups, subscriptions and trials, using Snap's own event names.
Platform rules from Snap: Conversions API.