Similar Snap Event Names
Your Snap Pixel has events with names that look like typos or variants of each other (for example, `purchase` and `Purchase`, or `ADD_CART` and `AddToCart`). Snap treats each unique string as a distinct event, so similar names split what should be one signal across two streams. Both streams end up below the volume Snap needs to optimise reliably.
Why It Matters
Snap event names are case-sensitive strings. `PURCHASE`, `Purchase`, and `purchase` are three different events to Events Manager. The same goes for spacing and separators: `ADD_CART` is not the same event as `AddCart` or `ADD CART`. When two tags fire what was intended to be the same business action under slightly different names, both events appear in the event list, both accumulate volume, and the Conversions objective dropdown shows both as selectable. This matters because Snap's optimisation engine needs roughly 50 events per week per event to bid well. Splitting one stream across two names cuts each in half. Two underpowered events optimise worse than one event at full volume. It also confuses reporting. Analysts see two PURCHASE-like events in the dashboard, do not know which one to trust, and either sum them (risking double counting if both fire on the same order) or pick one arbitrarily. The usual cause is a migration where the new tag introduced a different casing convention than the old one, or a custom event that should have been mapped to a Snap standard event but was given a bespoke name instead.
How To Fix It
- Review the flagged event pairs and identify the canonical name. For Snap standard events, the canonical name is the all-caps version listed in the standard events documentation (`PURCHASE`, not `Purchase`).
- Update the tag firing the non-canonical name to use the canonical one.
- If both names have historical volume, decide whether to keep the old name as a deprecated audience source or delete it.
- Reload affected pages with the Snap Pixel Helper and confirm only the canonical name fires.
- Re-baseline the canonical event's volume over the next week.
Example
Flagged pair: 'PURCHASE' and 'Purchase'
Flagged pair: 'ADD_CART' and 'AddToCart'Your Snap Pixel has events with similar names that likely represent the same business action. Per Snapchat's standard events documentation, event names are case-sensitive strings and each unique name is treated as a distinct event by Events Manager and the Conversions objective optimiser. When near-duplicate names split one business action across two streams, each stream ends up below the roughly 50 events per week per event threshold Snap needs to optimise reliably, and reporting becomes ambiguous about which event represents the true conversion. Fix: identify the canonical name (the all-caps form for standard events), update the offending tag to use it, 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