Snapchat Conversions API
Server-side conversions to Snap CAPI v3 with hashed match keys and click ids.
Snapchat's Conversions API v3 mirrors Meta's shape, so the integration behaves like the Meta one: conversions are delivered server-to-server with hashed identifiers, and the shared event id keeps a browser pixel (if you run one) deduplicated against the server event.
Credentials
| Field | Where to find it |
|---|---|
| Pixel ID | Snapchat Ads Manager → Events Manager → your pixel. |
| Access token | Ads Manager → Business settings → Conversions API tokens. Stored encrypted. |
Connect both under Integrations → Snapchat Conversions API.
Matching
Events carry whichever of these exist: hashed email and phone, the ScCid
click id (captured automatically from Snap ad landings and persisted across the
session), the _scid browser cookie, plus IP and user agent. More keys means a
higher match rate in Snap's attribution.
Event mapping
| PixelFox conversion | Snap event |
|---|---|
| view_content | VIEW_CONTENT |
| add_to_cart | ADD_CART |
| initiate_checkout | START_CHECKOUT |
| add_payment_info | ADD_BILLING |
| purchase | PURCHASE |
| search | SEARCH |
| lead | SIGN_UP |
| subscribe | SUBSCRIBE |
| page_view | PAGE_VIEW |
Conversions without a Snap equivalent map to the nearest accepted event, because Snap silently drops unknown names.