Snapchat Conversions API

the snapchat conversions api (capi) is a server side integration that sends event data directly from chord cdp to snapchat's servers unlike the snap pixel (which runs in the browser), the conversions api operates in cloud mode — events are sent server to server, making them resilient to ad blockers and browser tracking restrictions snapchat recommends using the conversions api alongside the snap pixel for maximum data coverage when both are configured, snapchat automatically deduplicates events using the client dedup id field, which chord cdp sets to the event's messageid on both sides getting started this is a cloud mode destination you will need pixel id — found in your snapchat ads manager under events manager > pixel details access token — your conversions api token, found in snapchat ads manager > business details optionally test mode — when enabled, events are sent to snapchat's /validate endpoint and appear in the snap events manager debug tool without affecting live reporting product content id field — which product field to use as item id when sending events sku , product id , or variant id defaults to sku if the configured field is absent on a product, it falls back through sku → variant id → product id → id this must match the item id format in your snap product catalog and must be set to the same value as the snap pixel destination connecting to the snapchat conversions api cdp destination warning before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream log into the chord data platform navigate to the cdp click the "add" button next to destinations select snapchat conversions api from the destination catalog enter the destination name, pixel id , and access token optionally configure test mode and product content id field click "create" to connect event mapping chord event snap event page page view order completed purchase product added add cart product viewed view content checkout started start checkout subscription created subscribe products searched search payment info entered add billing product added to wishlist add to wishlist signed up sign up page, track, and screen events are forwarded identify events are not forwarded common event fields these fields are included on every event sent to snapchat snap field chord source notes event name (mapped from event — see table above) event time timestamp event id messageid used for deduplication with the snap pixel event source url context page url data processing options (hardcoded) false user data snap field chord source (priority order) notes external id userid > anonymousid array email context traits email phone context traits phone gender context traits gender firstname context traits firstname lastname context traits lastname birthday context traits birthday city context traits address city state context traits address state zip context traits address zip > context traits address postalcode country context traits address country client ip address context ip not hashed client user agent context useragent not hashed madid context device advertisingid mobile ad id idfv context device id ios identifier for vendor sc click id properties click id > integrations\["snap conversions api"] click id > sccid query parameter from page url snap click id sc cookie1 integrations\["snap conversions api"] uuid c1 snap cookie value custom data these fields are sent in the custom data block on all events snap field chord source (priority order) notes currency properties currency defaults to "usd" value properties value total value after quantity ( price × qty per the chord tracking plan) num items count of products with a resolvable item id order id properties order id search string properties query > properties search string products sent as a products array on events that include product data omitted if no products are present snap field chord source (priority order) notes item id configured field → sku → variant id → product id → id must match item id in snap catalog item category properties products\[] category brand properties products\[] brand deduplication chord cdp sends the same messageid as client dedup id on both the snap pixel and the conversions api snapchat uses this field to automatically deduplicate events when both destinations process the same user action for purchase events, snapchat additionally deduplicates on transaction id chord cdp sets this to properties order id on both the pixel and capi, so no additional configuration is required for deduplication to work correctly both the snap pixel and snapchat conversions api destinations must be enabled in chord cdp product content id field must be set to the same value in both destinations testing and validation after connecting the destination enable test mode in the destination settings to send events to snapchat's /validate endpoint trigger test events and confirm they appear in the snap events manager debug tool disable test mode before going live after 24–48 hours, check events manager > diagnostics to verify match rates and deduplication rates updated 23 apr 2026