Snapchat Conversions API

introduction the snapchat conversions api is a server side tool that lets advertisers send web and app conversion events—like purchases, sign ups, or form submissions—directly from their backend to snapchat it’s designed to complement or replace browser based tracking methods (like the snap pixel), offering more reliable and complete data getting started you need your snapchat pixel id from your snapchat ad account and snapchat conversions api access token to connect this destination you can find the api access token for your snapchat ads account in the business details section within your snapchat account connecting to the snapchat conversions api destination 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 in the destination name and the snapchat pixel id and api access token click "create" to connect chord events relevant for destination not all chord tracking events are used downstream in your configured destinations the most relevant and important events in the chord tracking plan are mapped within the cdp destination, relayed and then ingested in the destination the chord tracking plan events used by the the https //developers snap com/api/marketing api/conversions api/parameters#server parameters destination are chord tracking event destination event checkout started start checkout order completed purchase page page view product added add cart product added to wishlist add to wishlist product list viewed view content products searched search promotion clicked ad click promotion viewed ad view signed up sign up only events matching any of the explicitly defined list above wil be sent through to the snapchat conversions api destination events without a matching preset are skipped, including custom events 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