Zero Volume Active Snap Events
You have Snap events marked active in Events Manager that have logged zero events. An active event with no volume usually means a broken trigger, a tag that never fires, a blocked request, or a rule scoped so narrowly that no real user matches it. Either way, the event is dead weight: it occupies a slot in the objective dropdown and the audience list, but it cannot be optimised against.
Why It Matters
Snap shows three event states: active (eligible to receive volume), paused (intentionally stopped), and inactive (not eligible). A zero-volume active event is the most ambiguous of the three. From Snap's perspective, the event is ready to receive data. From your perspective, no data is coming in. The gap is always somewhere in your implementation. The four common causes: First, the tag never fires. A GTM trigger is wired to an element selector that no longer exists on the page after a redesign. The tag is enabled, but no event ever matches the trigger. Second, the request is blocked. A consent platform, ad blocker, or CSP rule prevents `snaptr` calls from reaching Snap. The tag executes, the call queues, the network request fails. Events Manager sees nothing. Third, the event name was renamed and the old name is still in the active list. You moved to `PURCHASE` from `Purchase`, but the `Purchase` event is still flagged active with zero new volume. Fourth, the rule is too narrow. A custom event is gated behind a parameter check that almost no user satisfies.
How To Fix It
- For each zero-volume active event, identify the source tag in GTM or the hardcoded snippet.
- Reproduce the triggering action in a browser with the Snap Pixel Helper extension open. Confirm whether `snaptr('track', ...)` actually fires.
- If the tag does not fire, fix the trigger (selector change, page path mismatch, consent gate). If the tag fires but the request is blocked, check the network tab for blocked requests to `sc-static.net` or `tr.snapchat.com`.
- If the event is a renamed legacy, pause or archive it in Events Manager.
- If the rule is too narrow, broaden the trigger or accept that the event has no audience and archive it.
Example
Active events with zero volume: 'Lead', 'PURCHASE_v2', 'TestCheckout'Your Snap Pixel has events marked active in Events Manager with zero recorded volume. Per Snapchat's Snap Pixel documentation, an active event is eligible to receive data, so zero volume points to an implementation gap rather than a Snap-side issue. Common causes include GTM triggers wired to selectors that no longer exist after a site redesign, consent platforms or ad blockers blocking the network request to `tr.snapchat.com`, renamed events left active under their old name with no new traffic, or overly narrow rule conditions that no real user satisfies. Each zero-volume event still occupies a slot in the objective dropdown and audience list while delivering nothing optimisable. Fix: reproduce the triggering action with the Snap Pixel Helper, verify whether the tag fires and the request leaves the browser, fix or archive each event accordingly. 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