Keitaro Snapchat Integration: Tracker Postbacks Into the Conversions API
Keitaro Snapchat integration is the wiring that turns tracker postbacks into Snapchat Conversions API events - with one Snap-specific twist: Snap rejects events without a match key outright, so the pipeline's first job is guaranteeing the identifier set, not just the conversion record. Keitaro keeps the click identity; the delivery layer assembles Snap's payload.
Register Snapchat as a Traffic Source
Snap appends its click identifier to landing URLs as the &ScCid= query parameter. Declaring it in a custom Keitaro traffic source makes every click from Snapchat ads carry that value into the tracker's click record, where it stays attached to the campaign, offer, and sub IDs. The source registration flow is documented in Keitaro's guide to adding a traffic source - the only Snap-specific part is the parameter name.
The S2S Postback: Identity Out of the Tracker
Conversions enter Keitaro from the network and leave through the S2S postback: a URL template fired per conversion with macros substituted at send time. For the Snapchat pipeline the postback carries two identity values. The stored ScCid travels back so the delivery layer can fill Snap's click_id field - Snap encourages passing it, alongside the full landing URL in page_url. The tracker's transaction identifier becomes the deduplication identity: Snap's client_dedup_id must match what the Snap pixel emitted for the same event, and transaction_id covers order-level identity for purchases.
Delivering the Payload With Match Keys
| Snap field | Source from the Keitaro pipeline |
|---|---|
| match key | Hashed email or phone if the funnel captured them; client IP address and user agent from the click record, unhashed |
| click_id | The stored ScCid value, unhashed |
| client_dedup_id / transaction_id | The tracker's transaction identifier, identical to the pixel side |
| event type | Mapped from the postback status: sale to purchase, lead to sign_up |
| event timestamp | Send time - Snap accepts events up to 37 days old |
The event type enum, hashing rules, and response behavior are documented in Snapchat conversion events and Snapchat Conversions API errors. The Meta-side pattern is the Keitaro Facebook CAPI integration; owning only the postback and letting an automation assemble the payload is what MOST does across six networks, with Pixel Activator for single manual tests. The cluster map is in the complete guide.
Frequently asked questions
Sources
Sources
- Manual testing and validation: Pixel Activator fires free test events while you tune parameters.
- Automated delivery: Most routes conversions from your tracker or CRM continuously, with deduplication and retries handled.