Snap Pixel ID Format
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.
Why It Matters
The Snap Pixel snippet starts with `snaptr('init', '<PIXEL_ID>')` and every subsequent `snaptr('track', ...)` call binds to whatever ID that init received. Snapchat issues Pixel IDs in a UUID v4 shape: eight hex, four hex, four hex, four hex, twelve hex, separated by hyphens. Anything else is a copy-paste error or a leftover placeholder from a code sample. When the ID is wrong, the JavaScript still executes. `snaptr` is defined, the queue receives the call, the request leaves the browser. Snapchat just drops the event because no Pixel claims that ID. Events Manager shows zero traffic. Your audiences never populate. CAPI events may still arrive on the server side under a different ID, so the account looks half-broken in a way that is annoying to diagnose. The second failure mode is two pixels on one site. A migration leaves the old ID in the GTM tag and the new ID in the Shopify integration. Both fire. Snapchat sees a split account and neither pixel reaches the volume Snap needs for reliable optimisation.
How To Fix It
- Open Snapchat Ads Manager, go to Events Manager, and copy the Pixel ID directly from the pixel detail page.
- Search the GTM container, hardcoded site tags, and every commerce integration (Shopify, WooCommerce, BigCommerce) for `snaptr('init'` and confirm a single canonical ID is used everywhere.
- Validate the shape: 36 characters, four hyphens, lowercase hex.
- Publish, load a page with the Snap Pixel Helper extension active, and confirm PAGE_VIEW reaches the expected pixel.
- Fire one PURCHASE through a test order and confirm it appears in Events Manager under the right asset.
Example
Expected shape: 12345678-1234-1234-1234-123456789012
Observed: 12345678-1234-1234 (truncated)Your Snap Pixel is initialised with an ID that does not match the UUID format Snapchat issues. Per Snapchat's Snap Pixel installation documentation, the Pixel ID must be the exact identifier shown on the pixel detail page in Events Manager, formatted as a UUID (eight-four-four-four-twelve hex characters separated by hyphens). When the ID is malformed or stale, `snaptr` continues to execute in the browser but Snapchat drops the events because no pixel asset claims that identifier, leaving Events Manager empty and audiences unable to populate. Fix: copy the Pixel ID from Events Manager, replace every occurrence in GTM, hardcoded site tags, and commerce integrations, then validate with the Snap Pixel Helper. Source: businesshelp.snapchat.com/s/article/snap-pixel-installation.
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