Snapchat Pixel audit

Your Snap Pixel is installed and may be firing PAGE_VIEW, but none of the standard conversion events Snap optimises against are active. Without at least one of PURCHASE, SIGN_UP, SUBSCRIBE, or START_CHECKOUT, you cannot run conversion campaigns, build value-based audiences, or measure cost per acquisition in Ads Manager. The pixel is acting as a traffic counter, not a measurement system.

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.

Your Snap Pixel ID is missing, truncated, or does not match the UUID shape Snapchat issues (e.g. `12345678-1234-1234-1234-123456789012`). Until the ID is correct, your `snaptr('init', ...)` call routes events to nothing. PAGE_VIEW and PURCHASE will appear to fire in the browser, but Snapchat Events Manager will not see them, and the ad account they are supposed to feed will sit empty.

Your Snap PURCHASE events are firing with non-zero volume but the `price` field is zero or missing. Without value, Snapchat cannot compute ROAS, cannot run value-based bidding (target ROAS, value optimisation), and reports the campaign as if every order were worth nothing. Conversion counts look fine while the revenue column stays at zero.

Your Snap Pixel and Conversions API (CAPI) are sending the same PURCHASE event from both the browser and the server, but they do not share an `event_id` for deduplication, and the currency on the two payloads does not match. Snapchat ends up counting one order as two conversions, and the value column in Events Manager mixes USD with whatever your CAPI integration is sending, so the totals stop describing a single set of orders.

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.

Your business is configured as e-commerce, but the Snap Pixel is not tracking the full funnel from PAGE_VIEW through VIEW_CONTENT, ADD_CART, START_CHECKOUT, and PURCHASE. Snapchat's audience tools and Smart Bidding expect those five events as the canonical shopper path. Any gap means lookalikes and retargeting pools draw from a partial picture, and Snap cannot model intent steps between landing and purchase.

You have events marked as standard in the Snap Pixel that do not match Snap's canonical list (PAGE_VIEW, VIEW_CONTENT, SEARCH, ADD_CART, ADD_BILLING, ADD_TO_WISHLIST, START_CHECKOUT, PURCHASE, SIGN_UP, SUBSCRIBE). Snap will not treat these as standard for objective selection, audience templates, or dynamic product ads. They behave as custom events even though they are flagged as standard.

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.

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.