Duplicate Snap Event Names
You have multiple Snap Pixel events firing under the same name (for example, two PURCHASE events from a GTM tag and a Shopify integration, or two PAGE_VIEW events from a hardcoded snippet and a tag manager). Snapchat treats each as a separate stream when you optimise against it, which means one business action ends up split across two signals and neither has the volume Snap needs.
Why It Matters
Snap Pixel events are keyed by name. When `snaptr('track', 'PURCHASE', ...)` fires twice for the same order from two different sources, Events Manager logs both. The deduplication mechanism Snap provides is `event_id`, not the event name itself, so name collisions without matching event IDs produce true duplicates rather than dedup candidates. The common cause is migrations that leave the old implementation live. A team installs Snap via Shopify, then later adds a GTM container with its own PURCHASE tag for richer parameters. Nobody removes the original. Both fire on the order confirmation page. PURCHASE volume in Ads Manager doubles overnight and ROAS appears to spike before anyone realises it is double counting. The second cause is parameter forks. A team wants to test sending extra parameters on PURCHASE, copies the tag, edits the copy, forgets to pause the original. Now half the orders get the new payload and half get both.
How To Fix It
- Open Events Manager and look at the event list for the affected pixel. Sort by volume and identify names with suspicious traffic spikes.
- In GTM, search for every tag that calls `snaptr('track', ...)` and document which event names each one fires.
- Cross-reference with hardcoded site snippets and commerce integrations (Shopify, WooCommerce). Snap is often installed in more than one place.
- Pick one canonical source per event and pause or delete the duplicates.
- Reload the affected pages with the Snap Pixel Helper extension and confirm each event fires exactly once per business action.
Example
PURCHASE x 2 (one from Shopify integration, one from GTM)
PAGE_VIEW x 2 (one hardcoded, one from GTM)Your Snap Pixel has duplicate event names firing from more than one source for the same business action. Per Snapchat's standard events documentation, each business action should map to one event name and one firing source so Ads Manager volume describes real user behaviour rather than instrumentation overlap. Duplicate PURCHASE or PAGE_VIEW events inflate Events Manager totals, distort ROAS, and feed Snap's optimisation engine a doubled signal that biases bidding. Deduplication in Snap relies on `event_id`, not name collision, so two tags with the same name and no shared event ID produce true duplicates. Fix: identify every source firing each event name (GTM, hardcoded snippets, Shopify or other commerce integrations), pick one canonical source per event, pause the rest, and verify single-fire behaviour with the Snap Pixel Helper. Source: businesshelp.snapchat.com/s/article/standard-events.
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