The Snap Pixel on Shopify
Also called Snapchat pixel · Updated
Snapchat’s pixel is straightforward to install and easy to mis-map, because its event names are written in upper case with underscores rather than the CamelCase Meta uses. ADD_CART is not AddToCart, and Snapchat will silently ignore a name it does not recognise.
Snap Pixel at a glance
- ID format
- A UUID-style string: eight characters, then three groups of four, then twelve
- Where to find the ID
- Snapchat Ads Manager → Events Manager → your pixel
- Server-side API
- Conversions API
- Ad surfaces covered
- Snap Ads, Story Ads, Collection Ads, Dynamic Ads
Copy the ID from Snapchat’s own dashboard rather than typing it — a transposed digit produces a pixel that installs cleanly and reports nothing.
Events the Snap Pixel accepts on Shopify
| Event name | When it fires |
|---|---|
PAGE_VIEW | Every page. |
VIEW_CONTENT | Product pages. |
ADD_CART | Not ADD_TO_CART. The shorter name is the correct one. |
START_CHECKOUT | First checkout step. |
PURCHASE | Order confirmation. |
SEARCH | Storefront search. |
Server-side tracking: Conversions API
Snapchat’s CAPI accepts the same events server-side and deduplicates against the browser pixel using a shared client dedup ID.
What goes wrong with the Snap Pixel on Shopify
- Snapchat’s audience skews younger and more mobile, which means a higher share of in-app browser sessions and a correspondingly larger gain from server-side tracking.
- Dynamic Ads need a product catalog feed as well as a pixel. A firing pixel with no feed will not produce Dynamic Ads.
- Snap deduplication keys off a client dedup ID you must send on both copies of the event, not off the order number.
Mobile-first traffic and what it does to tracking
Snapchat has effectively no desktop audience. Every session is a mobile session, most inside Snapchat’s own in-app browser, on a device population that skews younger and newer — which means newer iOS versions with tracking prevention on by default. If you have measured event loss on any other platform, assume Snapchat’s is worse.
That makes the Snapchat Conversions API less of an upgrade and more of a prerequisite. A browser-only Snap Pixel on a Shopify store is measuring a minority of what it should, and optimising campaigns on that data trains delivery toward whichever customers happened to be trackable rather than whichever customers were valuable.
Snapchat deduplication is not Meta’s deduplication
Meta merges duplicate events by matching an event_id you send on both the browser and server copy. Snapchat uses a client deduplication ID for the same purpose, and it must be present on both copies of the event — not derived independently on each side, and not the Shopify order number unless you send that same value both times.
Get this wrong and the failure is quiet in the worst way: nothing errors, and your Snapchat purchase count simply doubles. Because Snapchat volumes are usually smaller than Meta’s, the inflation is easy to miss until ROAS numbers stop reconciling with actual revenue.
Step-by-step installation
This page is the reference. For the click-by-click walkthrough, including the Events Manager side of the setup, read the full guide.
Adding Snapchat and Pinterest pixels to Shopify →Related reading
- The Facebook Conversions API on Shopify
How the Meta Conversions API recovers Shopify conversions lost to iOS 14, ad blockers and Safari, what event deduplication does, and how to set it up.
- How to add a TikTok pixel to Shopify
Install a TikTok pixel on Shopify without editing your theme, connect the TikTok Events API for server-side tracking, and confirm Complete Payment fires.