Overview
Snap Pixel is Snapchat's conversion tracking and audience management tool for advertisers running campaigns on the Snapchat platform. Operated by Snap Inc. (headquartered in Santa Monica, California), the pixel fires on advertiser websites when visitors complete actions such as purchases, sign-ups, or page views — attributing those conversions to Snapchat ad exposures. The data feeds Snap Ads Manager for campaign optimization, return on ad spend (ROAS) reporting, and powers Snap Audience Match for retargeting people who previously visited the advertiser's site.
What This Script Does
Script Files and Domains
The Snap Pixel base code loads https://sc-static.net/scevent.min.js — Snap's universal pixel script. Some implementations load from tr.snapchat.com. Event data is transmitted to tr.snapchat.com/p via HTTPS POST requests. The pixel is initialized with a Snap Pixel ID (formatted as a UUID).
Cookies Set
_scid— Snap's primary cross-site visitor identifier. Persistent, 13-month expiry. Set as a first-party cookie on the advertiser's domain (when using first-party cookie mode) or as a third-party cookie onsc-static.net. Used for attribution and audience matching._scid_r— A redundant copy of_scidused for cross-domain reconciliation. Persistent, 13-month expiry._sctr— Session token for within-session event deduplication.
Standard Events Captured
Snap Pixel supports these standard event types: PAGE_VIEW (fires on all pages automatically), VIEW_CONTENT (product pages), ADD_CART (add to cart), START_CHECKOUT, ADD_BILLING, PURCHASE (with price, currency, and item identifiers), SIGN_UP, SAVE, SEARCH, SUBSCRIBE, AD_CLICK, AD_VIEW, COMPLETE_TUTORIAL, INVITE, LOGIN, SHARE, SPEND_CREDITS. Purchase events transmit transaction value, currency code, item IDs, and optional client deduplication IDs.
Snap Audience Match
The pixel feeds Custom Audiences built from site visitors, enabling retargeting campaigns to reach previous site visitors with Snap ads. Lookalike Audiences are generated by Snap's algorithm from Custom Audience behavioral patterns.
Advanced Matching (Snap Pixel Enhanced)
When enabled, the pixel can transmit hashed (SHA-256) user data including email address and phone number. Snap performs server-side matching against its user graph to improve attribution accuracy across devices and browsers where cookies are unavailable.
Conversions API (Server-Side)
Snap offers a server-side Conversions API that complements the browser pixel, allowing event data to be sent directly from the advertiser's server to tr.snapchat.com/v2/conversion — closing attribution gaps from ad blockers and Safari's ITP cookie restrictions.
Consent & Compliance
Category: Marketing
Under GDPR, the Snap Pixel requires explicit prior consent. It sets persistent cookies, builds behavioral advertising profiles, and transmits personal data to Snap's US-based servers. Snap participates in IAB TCF 2.2 as a registered vendor (Vendor ID 27). Relevant TCF purposes exercised include Purpose 1 (Store/access information on device), Purpose 3 (Create personalised ads profile), Purpose 4 (Select personalised ads), and Purpose 7 (Measure ad performance).
Snap Inc. is registered under the EU-US Data Privacy Framework (DPF) for GDPR-compliant transatlantic data transfers. The UK ICO has issued guidance that advertising pixels like Snap's require PECR-compliant consent (active opt-in) before cookies are set.
Under CCPA/CPRA, sharing website visitor data with Snap for cross-context behavioral advertising constitutes "sharing" of personal information. The opt-out mechanism must suppress the pixel for California residents who exercise their rights.
ePrivacy: The _scid and _scid_r cookies are persistent advertising identifiers — not strictly necessary — and require prior consent.
Should You Block This Without Consent?
Yes. The Snap Pixel sets persistent tracking cookies, transmits behavioral data to Snap's advertising infrastructure, and builds audience profiles for ad targeting and campaign optimization. It provides no functionality for site visitors. Block until explicit marketing consent is obtained.
Consent Categories
Also Known As
Industries
Tracked Domains (2)
sc-static.netMarketingtr.snapchat.comMarketingFrequently Asked Questions
Is the Snap Pixel subject to consent requirements?
Yes. The Snap Pixel is IAB TCF 2.2 Vendor ID 27 and requires explicit prior consent under GDPR. It sets persistent tracking cookies and transmits behavioral data to Snap's US servers for advertising attribution and audience building across Snapchat campaigns.
What cookies does the Snap Pixel set on my site?
It sets _scid (13-month primary visitor identifier), _scid_r (redundant cross-domain copy), and _sctr (session deduplication token). The _scid and _scid_r cookies are persistent advertising identifiers that require prior consent before being written to the browser.
How does ConsentStack manage the Snap Pixel?
ConsentStack treats the Snap Pixel as a marketing vendor and blocks it by default. The pixel fires only after the visitor grants marketing consent. Consent withdrawal on subsequent visits suppresses loading, and ConsentStack can pass a valid TCF 2.2 signal to Snap when using a TCF-compatible configuration.
Related Vendors
Manage consent for Snap Pixel
ConsentStack automatically detects and manages Snap Pixel trackers so your site stays compliant with global privacy regulations.