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 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 supported events the following events are automatically sent from chord to snap pixel page viewed product viewed cart viewed checkout started order completed email captured (if supported by snap pixel api) these events help power snap’s pixel based audiences, conversion campaigns, and performance analytics 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 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