Snapchat Pixel Events on Shopify: Full Reference Guide
Pixel Tracker maps your Shopify store's actions to Snapchat's own event taxonomy automatically, so there's no manual event builder to configure. Snapchat's standard events use SCREAMING_SNAKE_CASE names like PAGE_VIEW, VIEW_CONTENT, ADD_CART, START_CHECKOUT, and PURCHASE, and Pixel Tracker sends all five directly from the ScriptTag it installs on your storefront.
This page breaks down what each event means, when it fires, and what it tells Snapchat's ad system. If you've confirmed events are set up but they're not showing up in Ads Manager, the troubleshooting guide covers the common causes, from Pixel ID mismatches to ad blockers.
PAGE_VIEW: Every Storefront Page Load
PAGE_VIEW fires on every page a shopper loads across your store, not just product pages. It's the broadest signal Pixel Tracker sends to Snapchat and forms the baseline traffic data Snapchat uses for retargeting audiences and lookalike modeling. It's also the first event worth checking if something looks off, since a store with zero PAGE_VIEW activity almost always points to an installation problem rather than an event-mapping one.
VIEW_CONTENT: Product Page Visits
VIEW_CONTENT fires when a shopper lands on a specific product page, and it carries the item ID and price along with it. Snapchat uses this to build catalog-based retargeting ads, showing shoppers the exact products they looked at rather than generic store ads. Because it carries item-level detail, VIEW_CONTENT is also what makes dynamic product ads possible for stores with larger catalogs.
ADD_CART: Add to Cart Actions
ADD_CART fires whenever a product is added to the cart, whether from the product page or a cart drawer. This is the event behind most Snapchat cart abandonment campaigns, since it marks a shopper who showed real purchase intent but didn't finish checking out. It typically shows meaningfully less volume than VIEW_CONTENT, since only a fraction of product viewers add anything to their cart, and that drop-off is expected rather than a sign of broken tracking.
START_CHECKOUT: Checkout Initiation
START_CHECKOUT fires when a shopper moves from the cart into Shopify's checkout flow. It's one of the more valuable mid-funnel signals for Snapchat's ad optimization, since it separates casual browsers from shoppers who are close to converting. A healthy gap between ADD_CART and START_CHECKOUT is normal too, cart abandonment is a well-documented shopping behavior, not evidence the pixel missed something.
PURCHASE: Completed Orders
PURCHASE fires on Shopify's order confirmation page and includes order value and currency. It's the conversion event Snapchat campaigns optimize toward, and also the event most affected by ad blockers, iOS privacy settings, and Snapchat's own reporting delay. Because of that delay, don't expect PURCHASE counts in Ads Manager to match your Shopify order count in real time, they typically catch up within a day or two.
Frequently asked questions
Which Snapchat events does Pixel Tracker send automatically?
PAGE_VIEW, VIEW_CONTENT, ADD_CART, START_CHECKOUT, and PURCHASE, all mapped from standard Shopify storefront and checkout actions with no manual setup.
Do I need to name events in SCREAMING_SNAKE_CASE myself?
No. That naming convention is just how Snapchat's own system labels and expects events. Pixel Tracker handles the mapping so you never touch event names directly.
Why does VIEW_CONTENT show far more volume than PURCHASE?
That's expected. Most shoppers browse products without buying, so VIEW_CONTENT naturally has the widest funnel and PURCHASE the narrowest. A large gap between the two reflects normal funnel drop-off, not a tracking problem.
Can I add custom Snapchat events beyond the standard five?
Not currently. Pixel Tracker sends the five standard events mapped from Shopify's own storefront and checkout actions, and there's no custom event builder in the app today.
Where do I check which events Snapchat actually received?
Snapchat Ads Manager's Events Manager shows a per-event breakdown of what's come through. If counts look wrong, the troubleshooting guide walks through the most common causes.