Missing Snap PAGE_VIEW Event
The Snap Pixel snippet is on the site, but PAGE_VIEW is either not firing or is paused. PAGE_VIEW is the base signal Snap uses to confirm the pixel is alive and to seed broad audiences. Without it, Events Manager shows no baseline traffic, retargeting pools cannot be built from site visitors, and Snap will surface the pixel as inactive even if conversion events occasionally fire.
Why It Matters
When you install Snap, the base code includes a `snaptr('track', 'PAGE_VIEW')` call that runs on every page load. That single event does a lot of work: it confirms the pixel is reachable from the user's browser, it populates the broadest retargeting audience (all site visitors in the last N days), and it serves as the denominator for funnel diagnostics so Snap can show conversion rates from view to purchase. With PAGE_VIEW missing or disabled, all of that breaks. Events Manager shows the pixel as low- or zero-volume and may flag it as unhealthy. Site-visitor retargeting either doesn't exist or relies on a custom event with much lower coverage. Funnel reports show conversion rates over an unknown base because Snap doesn't know how many pages were viewed. The usual cause is one of two things. Either the base code was modified to remove the auto PAGE_VIEW call (often done deliberately for SPAs where developers plan to fire it manually on route changes, then forget the manual call). Or the entire base snippet is gated behind a consent banner that never grants consent because of a misconfiguration.
How To Fix It
- Load any tracked page and open the Snap Pixel Helper extension. Confirm PAGE_VIEW appears in the event list.
- If missing, check the base snippet in source view. The default snippet includes `snaptr('track', 'PAGE_VIEW')` at the bottom.
- For SPAs, ensure a manual `snaptr('track', 'PAGE_VIEW')` fires on every route change, not just the initial load.
- If consent gating is the cause, confirm the consent platform is granting Snap the right purpose before the base snippet runs.
- After fixing, confirm PAGE_VIEW volume in Events Manager grows over a 24-hour window.
Example
Base snippet ends with: snaptr('track', 'PAGE_VIEW');
Observed: line removed or never executedYour Snap Pixel is installed but PAGE_VIEW is not firing. Per Snapchat's Snap Pixel installation documentation, the base snippet auto-fires PAGE_VIEW on every page load, and this event acts as the health check, broad retargeting seed, and funnel denominator for the pixel. When PAGE_VIEW is absent, Events Manager may flag the pixel as inactive, broad site-visitor retargeting cannot be built, and conversion-rate reporting loses its base. Common causes include a modified base snippet on single-page apps without a replacement manual fire on route changes, or a consent banner gating the snippet without granting the right purpose. Fix: restore the auto PAGE_VIEW call, instrument route changes on SPAs, verify consent flow grants Snap, and confirm volume with the Snap Pixel Helper. Source: businesshelp.snapchat.com/s/article/snap-pixel-about.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.
References
Audit your own files for this check
AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.
Run a free audit