Snapchat Conversions API
Snap's conversions API within the familiar server-to-server model
Snapchat's Conversions API follows the same architecture as Meta CAPI and TikTok's Events API: server-side event delivery to Snap directly, bypassing the Snap Pixel's browser-side limitations, intended to run alongside the Pixel (not replace it) for the most complete signal. The strategic motivation is identical across all these platforms — recovering signal lost to ITP, ad blockers, and increasingly restrictive mobile tracking defaults.
Click and identity signals specific to Snap
Snap's click identifier is captured via the ScCid URL parameter appended to landing pages from ad clicks, functioning the same way fbclid/ttclid do for Meta/TikTok — it must be captured client-side and persisted so it's available for the later server-side event. Snap also supports the Snap Pixel's own first-party cookie identifier for matching anonymous browser sessions to server-side events, and accepts the standard hashed PII fields (email, phone, mobile ad ID) as additional matching signals, following the shared SHA-256 hashing convention used across the industry's conversions APIs.
{
"event_type": "PURCHASE",
"event_conversion_type": "WEB",
"event_tag": "order_4821",
"timestamp": 1735689600000,
"hashed_email": "f660ab912ec121d1b1e928a0bb4bc61b15f5ad44d5efdc4e1c92a25e99b8e44",
"hashed_phone_number": "374f6de9b1a01d8e57c0b4c9fce5e8e4a1cf6c9b8ce3b3f0e0a7f1cf7b2b8c88",
"click_id": "ScCid_1a2b3c4d",
"client_ip_address": "203.0.113.42",
"user_agent": "Mozilla/5.0 ...",
"price": 149.50,
"currency": "USD"
}event_tag doubles as the deduplication key
event_tag field plays the same role as Meta's event_id and TikTok's event_id — a shared identifier sent from both the client-side Snap Pixel and the server-side Conversions API call for the same real-world event, letting Snap recognize and deduplicate the pair into a single counted conversion rather than two.Integration paths: direct API, server-side GTM, or a partner integration
Teams generally reach Snap's Conversions API through one of three paths: a direct backend integration calling Snap's REST endpoint, a server-side GTM container configured with a Snap tag template (community or custom-built, since Snap isn't always a first-class default template the way Google's own products are), or a partner platform integration (Shopify's native Snap integration, for instance, handles much of this automatically for ecommerce merchants). The right choice depends mostly on whether a server-side GTM container already exists for other platforms — if so, adding Snap as another destination tag inside it is usually the lowest-friction path.
Integration path tradeoffs
| Path | Effort | Best for |
|---|---|---|
| Direct backend-to-Snap API integration | Highest — custom code and credential management | Teams with no existing server-side tagging infra |
| Server-side GTM tag | Moderate — reuses existing sGTM container and event routing | Teams already running sGTM for other platforms |
| Native platform integration (e.g. Shopify) | Lowest — largely configuration, not code | Ecommerce merchants on a supported platform |
Verify event_type mapping against Snap's standard event list
event_type values (PURCHASE, SIGN_UP, START_CHECKOUT, etc.) for its optimization and reporting to correctly categorize events. A custom or mismatched event type is accepted by the API but won't register against campaign optimization goals expecting a specific standard event — always confirm the mapping against Snap's current documented event list rather than assuming names are interchangeable across platforms.What's Next?
With Meta, TikTok, and Snap's server-side conversions APIs following the same core pattern, Pinterest and LinkedIn round out the major social ad platforms — and the remaining engineering effort shifts from learning new concepts to simply mapping the same fields into each platform's specific schema.
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.