What it is
The Snap Pixel reports events to Snapchat Ads for optimisation and attribution. Its presence and purpose should be determined from the live site and advertising configuration, not inferred from the site’s audience.
It is worth noting alongside the children’s-privacy provisions now appearing in several regimes: an audience skew towards minors changes the analysis around advertising technology, whatever the consent interface says.
What a scan matches
A verification scan drives a real browser and records the outbound requests observed during its configured journeys, so Snap Pixel is identified by request hosts and paths rather than by source-code claims. Requests on unvisited paths, after unperformed interactions or solely on the server remain outside that observation.
- tr.snapchat.com: the pixel endpoint
- snapchat.com
- sc-static.net: where the script is served
Cookies are classified by name before domain because many analytics and advertising tags write first-party cookies through the page, which places a vendor-related identifier on your domain. Matching known names helps attribute those values without assuming that every first-party cookie came from your own application.
| Cookie | What it is for |
|---|---|
| _scid | The Snap browser identifier |
| _sc*_id | Related Snap identifiers, matched by pattern |
Controlling it with consent
No named adapter. Gate it as a custom script attached to marketing, or as a container tag.
No named adapter: choose the appropriate control
The product ships named adapters for Google Tag Manager, Google Analytics, the Meta and TikTok pixels, and Klaviyo. Choose the control route that fits this technology: a custom HTTPS script declaration for a browser loader, an individual consent condition inside a tag manager, a platform or app setting, or a click-to-load placeholder for a frame. Server-side integrations need their own enforcement because a browser runtime cannot stop them.
What breaks if it is refused: Snapchat campaign measurement for refusing visitors.
Verifying it
Before consent there should be no request to tr.snapchat.com or sc-static.net and no _scid cookie.
- Before a choice: optional tracking endpoints and optional identifiers are absent; any intentionally loaded necessary or functional surface matches the control model described above
- After rejecting optional categories: optional activity remains absent and the refusal persists across a reload
- After granting the relevant category: the expected loader or embed appears and the feature behaves normally
- After withdrawing: new optional activity stops; where the vendor supports a consent signal, verify that the signal is sent as well as checking network behavior
Common questions
Does an audience of minors change what I need to do?
It can, significantly. Several regimes have or are developing specific children’s codes, and advertising technology is usually the first thing they restrict. This is a question to take to counsel rather than to resolve in a consent configuration.
Sources and verification
Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.
- Snap Business: Snap Pixel FAQ
Vendor documentation
Checked
See what your own site is loading
A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.