Snap Conversions API: how to set up server-side conversion tracking on Snap.

Snap Conversions API is the server-to-server endpoint that Snap uses to receive conversion events directly from your server, bypassing the browser pixel. The API was built (or rebuilt) after iOS ATT (April 2021) broke pixel-based conversion tracking. Most advertisers running paid Snap campaigns in 2026 need CAPI implemented. The standard pattern is to run the browser pixel and the server-side CAPI in parallel with event deduplication; the browser captures what the server cannot see, the server captures what the browser cannot send. Together they rebuild most of the conversion signal lost in 2021.

By David Schaefer · LinkedIn · Updated · 12 min read · 5 sources cited

Key takeaways

  • Snap Conversions API is Snapchat's server-to-server endpoint, launched 2020.
  • Snap's iOS-heavy user base makes CAPI more impactful than on platforms with older users.
  • Pixel-only match rates: 35-55 percent post-ATT. With CAPI: 65-80 percent.
  • Required for Goal-Based Bidding (GBB) to optimize properly.
  • Same dual-implementation pattern: Snap Pixel + CAPI with event_id deduplication.
  • Standard event names: SIGN_UP, ADD_TO_CART, START_CHECKOUT, PURCHASE. Custom names hurt optimization.

What Snap Conversions API is

Snap Conversions API (CAPI) is Snapchat's server-to-server endpoint for conversion events. Snap launched CAPI in 2020 as the iOS-ATT response. The setup pattern is identical to Meta and TikTok: run the Snap Pixel and CAPI in parallel, deduplicate by event_id, recover the conversion signal that the Pixel cannot capture post-ATT. Snap CAPI is mandatory for advertisers running Goal-Based Bidding (the equivalent of Meta's CBO and Google's Max Conversions).

Why Snap advertisers need CAPI

Snap's user base skews young and iOS-heavy — the demographics hit hardest by ATT. Pixel-only match rates on Snap typically drop to 35-55 percent post-ATT, the lowest of any major platform. Snap CAPI plus Pixel deduplication brings rates back to 65-80 percent, which is the difference between optimization signal that works and optimization signal that does not.

Setup walkthrough

  1. Generate a Snap CAPI access token.Ads Manager > Business Settings > Conversion API > Generate access token.
  2. Set up sGTM or a custom integration.Snap publishes REST endpoints. sGTM has community templates for Snap CAPI.
  3. Map web events to Snap event names.SIGN_UP, ADD_TO_CART, START_CHECKOUT, PURCHASE. Use Snap's standard names for best optimization.
  4. Add event_id for deduplication.Both Pixel and CAPI events must share event_id.
  5. Send hashed PII.email, phone_number, external_id (hashed user ID). SHA-256 hashed.
  6. Validate in Snap Ads Manager.Events Manager shows received events, match rates, and deduplication status.

Payload format

Standard Snap CAPI event includes pixel_id, event_type (PURCHASE, etc.), event_conversion_type (WEB / OFFLINE / MOBILE_APP), timestamp, event_id (deduplication), and hashed_email/hashed_phone_number/hashed_external_id for user matching. ecommerce events also include price, currency, and item details.

Deduplication

Same pattern as Meta and TikTok. Both Pixel and CAPI events must share event_id. Snap deduplicates within 72 hours and counts the conversion once. Without matching event_ids, double-counting.

Common implementation mistakes

Three failures. Implementing CAPI without dropping or deduplicating the Pixel (double-counting). Sending unhashed PII (rejected). Treating Snap CAPI as optional when Snap's user demographics make it the highest-impact platform for ATT recovery.

Quick answers

What is Snap Conversions API?
Snapchat's server-to-server endpoint for conversion events. Launched 2020 in response to iOS ATT. Same pattern as Meta CAPI and TikTok EAPI.
Do I need Snap CAPI more than other platforms?
Yes, especially. Snap's user base is the most iOS-heavy of major platforms, so ATT impact is the largest. CAPI recovery is most valuable here.
What match rate should I expect?
65-80 percent with proper Pixel + CAPI deduplication. 35-55 percent for Pixel-only post-ATT. Material difference for bidding.
What event names should I use?
Standard Snap names: SIGN_UP, ADD_TO_CART, START_CHECKOUT, PURCHASE, etc. Custom names hurt Snap's optimization.
How long does implementation take?
2-4 weeks. Same complexity as Meta CAPI.
Is Snap CAPI required for Goal-Based Bidding?
Effectively yes. GBB depends on accurate conversion signal. Without CAPI the signal is too noisy.

Frequently asked

What is Snap Conversions API?

Snapchat's server-to-server endpoint for conversion events, launched in 2020 as the iOS-ATT response. Setup pattern matches Meta CAPI and TikTok EAPI — run the Snap Pixel and CAPI in parallel with event_id deduplication.

Why is Snap CAPI especially important?

Snap's user base skews young and iOS-heavy, the demographics hit hardest by iOS ATT. Pixel-only match rates on Snap drop to 35-55 percent post-ATT, the lowest of major platforms. CAPI recovery is materially more impactful on Snap than on platforms with older or more Android-heavy users.

How is Snap CAPI different from Meta CAPI?

Same architecture, different payload. event_type names differ (Snap uses uppercase SIGN_UP, ADD_TO_CART; Meta uses PascalCase Lead, AddToCart). Snap's external_id is the user matcher; Meta's is fbp.

What are Snap's standard event names?

SIGN_UP, PAGE_VIEW, ADD_TO_CART, START_CHECKOUT, PURCHASE, VIEW_CONTENT. Snap's Goal-Based Bidding optimizes against these standard events; custom names hurt optimization.

Is Snap CAPI required for Goal-Based Bidding (GBB)?

Effectively yes. GBB depends on accurate conversion signal to optimize bids. Pixel-only conversion data post-ATT is too noisy for GBB to perform. Snap's documentation strongly recommends CAPI for GBB-enabled campaigns.

How long does Snap CAPI implementation take?

2-4 weeks for a mid-market advertiser. Similar complexity to Meta CAPI but slightly simpler payload format.

What is the typical match rate improvement?

From 35-55 percent Pixel-only post-ATT to 65-80 percent with Pixel + CAPI deduplication. The 20-30 percentage point improvement directly impacts bidding efficiency.

Does Snap CAPI work with sGTM?

Yes. Community-maintained Snap CAPI templates exist for Google Tag Manager Server-Side. sGTM is the recommended implementation path.

Sources cited on this page

  1. Meta — Conversions API documentation.
  2. Google — Google Ads Conversions API documentation.
  3. Apple — App Tracking Transparency framework.
  4. Simo Ahava — Most-cited resource on server-side GTM and CAPI.
  5. Real Growth Matters Inc. — Internal CAPI implementation audits, 2024-2026.