Snap Pixel

introduction snap pixel helps you attribute purchases to ads, build custom audiences, and optimize performance for ecommerce growth campaigns the snap pixel cdp destinatiom allows you to send commerce events from your storefront (via chord) directly to snapchat this enables conversion tracking, retargeting, and ad performance measurement in your snapchat ads manager what the snap pixel destination does once connected, chord automatically sends real time storefront events to snapchat via snap pixel enables campaign tracking, roas measurement, and retargeting workflows maps your chord event data to snapchat’s standard event model getting started before you begin make sure you have an active snapchat ads manager account create or locate your snap pixel id within the snap dashboard ensure chord is actively tracking events on your storefront connect snap pixel in chord 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 chord navigate to cdp > destinations click add destination select snap pixel from the destination list enter a display name (e g , “snap pixel – production”) paste your snap pixel id click create to activate the destination events event mapping true 244,244 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type page fires a snap pixel page view event snap sdk call snaptr("track", "page view", { client dedup id }) no additional attributes are sent with page events identify re initializes the snap pixel with user data for enhanced matching the event is skipped if neither email nor phone is available snap sdk call snaptr("init", pixelid, userdata) true 162,162,164 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type track order completed fires a purchase conversion event with order and product data snap sdk call snaptr("track", "purchase", orderdata) true 162,162,164 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type product added fires an add to cart event using the first product from properties products snap sdk call snaptr("track", "add cart", productdata) true 162,162,164 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type product viewed fires a content view event using the first product from properties products snap sdk call snaptr("track", "view content", productdata) same attributes as product added above checkout started fires a checkout started event with order and product data snap sdk call snaptr("track", "start checkout", orderdata) same attributes as order completed above subscription created fires a subscribe event with order and product data snap sdk call snaptr("track", "subscribe", orderdata) same attributes as order completed above products searched fires a search event with the search query snap sdk call snaptr("track", "search", searchdata) true 162,162,164 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type payment info entered fires a billing info event no additional attributes beyond the dedup id snap sdk call snaptr("track", "add billing", { client dedup id }) product added to wishlist fires a wishlist event using the first product from properties products snap sdk call snaptr("track", "add to wishlist", productdata) same attributes as product added above signed up fires a sign up event no additional attributes beyond the dedup id snap sdk call snaptr("track", "sign up", { client dedup id }) initialization the plugin initializes by loading https //sc static net/scevent min js and calling snaptr("init", pixelid) (optionally with user email and user phone number if available on the triggering event) before the script loads, a queue buffers any calls to snaptr the plugin manages sdk loading state ( fresh → loading → loaded / failed ) to prevent duplicate script loads if the script fails to load, subsequent events are silently dropped csp requirements if your site uses a content security policy, allow the following domains true 244,244 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type verification & testing after setup use the snap pixel helper chrome extension to confirm events are firing from your site in events manager , validate incoming events (may take a few minutes to appear) test conversion workflows and confirm attribution in ads manager best practices do not install snap pixel manually in shopify if you’re using chord to manage events — this may cause duplicate firing coordinate with your paid media team to ensure the correct pixel is used across campaigns event mappings follow snapchat’s standard ecommerce schema; custom events can be added by request