Skip to article
On this page

Snapchat Pixel explained: what it tracks on your site

NyXi

NyXi

7 min read

What the Snap Pixel is, why its ID is a long UUID, the upper case event names Snapchat expects, how the Conversions API fits in, and what to do about a pixel left over from a finished campaign.

If Tag Explorer has drawn an Advertising card on your site with a long string like 6abc82ca-4a3a-4391-98ba-0317a8471234 as the title, you are looking at the Snap Pixel. It is Snapchat’s conversion tracking tag, and it is there because somebody has run Snapchat ads from your site, or once intended to. Paste your page into Tag Explorer to see this tag on your own site.

The pixel exists to close a loop. Snapchat already knows who saw an ad and who tapped it. The pixel is the only way it learns what happened next on your site, so it is the thing that turns “three hundred taps” into “eleven enquiries and two sales”.

What it actually does

The Snap Pixel loads a small script from Snapchat and exposes a function called snaptr(). Your site calls that function twice: once to initialise the pixel with your pixel ID, and then again each time something worth counting happens.

Three things follow from that.

  • Conversion reporting. Snapchat can attribute a sale or a lead back to a specific ad, ad set and campaign rather than to Snapchat in general.
  • Optimisation. Once enough conversions are recorded, Snapchat’s bidding chases people who resemble the ones who converted, instead of the ones who merely tapped.
  • Retargeting. Visitors can be gathered into audiences, for example everyone who reached a checkout page and did not finish.

The first is reporting. The second and third are what actually change what your money buys, and both are starved if the pixel only ever sends page views.

What the ID means

A Snap Pixel ID is a UUID: thirty two hexadecimal characters in five hyphenated groups, in the shape xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. It looks like a database key because that is what it is. No prefix, no account name, nothing readable, which is precisely why it is worth writing yours down somewhere you can find it again.

Yours lives in Snapchat Ads Manager under Events Manager, listed against the pixel. Compare it character for character with what a scan of your site reports. A pixel ID that matches nothing in your own Events Manager belongs to a different ad account, and in practice that usually means a previous agency’s.

The UUID shape also makes Snapchat easy to tell apart from its neighbours on a scan. A Meta Pixel ID is a long run of digits, a Reddit pixel ID starts with t2_, and a TikTok pixel ID is a shorter block of mixed case characters.

The event names Snapchat expects

Snapchat’s standard events are written in upper case with underscores, and that is a real difference from the platforms sitting next to it on your scan rather than a cosmetic one. PAGE_VIEW, VIEW_CONTENT, ADD_CART, START_CHECKOUT, PURCHASE and SIGN_UP are the common ones, and Snapchat reserves a set of numbered custom events for anything that does not fit.

Spelling matters more than people expect. Send Purchase or add_to_cart and Snapchat records something, but not the standard purchase event, so the reporting stays empty and the optimisation you are paying for never receives the signal. If Snapchat shows you plenty of traffic and no conversions, mismatched event names are the first thing to check, well ahead of anything more exotic. Snapchat’s own pixel documentation lists the accepted names.

Advanced matching and the Conversions API

Snapchat supports advanced matching: sending a hashed email address or phone number alongside the event so a conversion can still be tied to a Snapchat account when cookies do not survive the journey. The value is hashed before it leaves the browser. Check your privacy policy covers it before you switch it on.

The server side companion is the Snap Conversions API, where your own server reports the event to Snapchat directly rather than depending on the visitor’s browser. Browser tags are increasingly blocked, truncated or stripped of context, so the direction of travel is to send the important events both ways and let Snapchat match them up. That matching relies on a shared event ID being present on both copies. Running both without one is how a business ends up reporting twice the sales it made and then bidding as if that were true.

What this looks like in Tag Explorer

Tag Explorer draws your page as a tree. Each Google Tag Manager container is a branch, the tags inside it are leaves beneath it, and anything hard coded into the page HTML sits under DIRECT ON PAGE.

The Snap Pixel appears as an Advertising card with the UUID as the card title and the tag type as the subtitle. If it was installed as a Custom HTML tag rather than the official template, expect less detail on the card, and possibly a Custom card instead.

Worth reading there:

  • Where it sits. Under a container is tidy. Under DIRECT ON PAGE and under a container is the shape of a double install.
  • The info icon, which opens a short definition plus the Learn more link that brought you here.
  • A duplicate banner and a red attention badge, which appear when the same pixel ID is found from two sources.
  • The insights panel below the tree, which raises softer advisories such as two different Snapchat IDs on one page.

Two limits, stated plainly. The published container file carries the tag type and the tracking ID but never the human names you gave your tags, so a scan cannot tell you a tag is called “Snap Purchase”. And the tool reads the published container only, so a Snap Pixel sitting unpublished in a Tag Manager workspace will not appear at all.

A scan proves the pixel is installed. It cannot prove it fired. That is what Snapchat’s own pixel helper, Tag Manager Preview mode and the browser DevTools Network tab are for.

What to do if it is missing, duplicated or dead

Missing. If you are spending on Snapchat and no Snap card appears, the campaign is running blind and the bidding is guessing. Confirm the pixel exists in your container, that its trigger covers every page rather than just the homepage, and that the container version was actually published. Scan a second page too, because a pixel that loads only on the homepage is an easy miss.

Duplicated. The same pixel ID arriving from two sources doubles every event. Conversions inflate and the optimisation learns the wrong lesson. Keep the copy in Tag Manager and remove the hard coded one from the page template, since that is the copy nobody remembers editing. Two different pixel IDs is a separate fault: one almost always belongs to an ad account you no longer use, so decide which is live and delete the other.

Dead or stale. The Snap Pixel is current, so it is never dead by age. It goes stale instead. A pixel left behind after a campaign finished still loads for every visitor, still adds weight to every page, and still feeds audiences into an account nobody opens. If Snapchat is not in the plan for the next few months, take it out.

Run your site through Tag Explorer and check the pixel ID on the card against the one in your own Events Manager. If they disagree, or nobody can remember adding it, sort that out before the next campaign starts. Our ChatGPT ads work begins the same way: making sure the measurement underneath a campaign tells the truth before any budget goes near it.

Frequently asked questions

What does a Snap Pixel ID look like?

It is a UUID: thirty two hexadecimal characters in five hyphenated groups, for example 6abc82ca-4a3a-4391-98ba-0317a8471234. There is no prefix and nothing human readable in it. You will find yours in Snapchat Ads Manager under Events Manager, listed against the pixel.

Why are Snapchat's event names in capitals?

Snapchat's standard events are written in upper case with underscores, such as PAGE_VIEW, ADD_CART and PURCHASE. That is simply the convention Snapchat chose, and it differs from the platforms likely sitting beside it on your scan. Sending Purchase instead of PURCHASE will not populate the standard purchase reporting, so campaign optimisation never gets the signal.

Do I need the Snap Conversions API as well as the pixel?

They do the same job from different places: the pixel reports from the visitor's browser, the Conversions API reports from your own server. Browser tags are increasingly blocked or cut short, so sending your important events both ways is the direction of travel. If you do run both, send a shared event ID so Snapchat can deduplicate, or you will report every sale twice.

Should I remove a Snap Pixel after the campaign ends?

Yes, if Snapchat is not in your plans for the next few months. A leftover pixel loads for every visitor on every page, builds audiences into an account nobody logs into, and returns nothing. It takes minutes to put back, and the retargeting audience you lose was decaying anyway.

More articles