What is the sc_at cookie?
The sc_at cookie is placed by Snapchat (Snap Inc.) on websites that integrate the company's tools, such as Snap Pixel, Snapchat share buttons, or Snapchat login widgets. Its name suggests it functions as an "authentication token" tied to a Snap advertising session.
It typically appears when a visitor interacts with an embedded Snapchat element on the page, or when the tracking pixel loads in the background, regardless of whether the user has an active Snapchat account.
What data it stores
The cookie stores a unique identifier that Snapchat uses to link activity on the third-party site to a Snap advertising session or profile. Snap does not publicly document the exact value format, and it may vary, so no assumptions should be made about its structure.
Data collected through sc_at is sent to Snap Inc.'s servers and may be combined with other signals (IP address, device type, pages visited) for conversion attribution and ad campaign optimization.
What it is used for
For Snapchat, sc_at helps measure the effectiveness of advertising campaigns (Snap Ads) – how many users who saw an ad on Snapchat later visit the advertiser's website and what actions they take there (purchase, sign-up, etc.).
For the site owner, this cookie enables conversion reporting in Snapchat Ads Manager and the creation of retargeting or lookalike audiences based on existing visitors.
Does it require consent?
In CookieFix's classification, sc_at falls under the marketing category (advertising/tracking). Under GDPR and the ePrivacy Directive (2002/58/EC), marketing cookies cannot be set before obtaining the user's explicit consent.
- The site owner must list
sc_atin the cookie policy, with its provider, purpose, and duration. - The Snap Pixel script or Snapchat widgets must load only after consent is given, not on page load.
- Declining consent must be as easy as accepting it, per applicable data protection authority guidance.
How to block or delete sc_at
A visitor can manually delete or block sc_at from browser settings (Chrome, Firefox, Safari, Edge) under the cookie and site data management section. Tracker-blocking extensions can also prevent it from being set.
For site owners, blocking it automatically before consent is the recommended approach: a CMP like CookieFix can stop Snapchat scripts (Snap Pixel, share buttons) from loading until the visitor gives consent, preventing the cookie from being set prematurely.
Frequently asked questions
It's not malicious, but it is a tracking cookie used for advertising purposes, which is why it requires user consent under GDPR.
The typical duration is around 13 months from when it's set or from the last interaction, depending on Snap's configuration.
It's a third-party cookie, set by the Snapchat/Snap Inc. domain when one of their tools is embedded on the visited site.
Yes, since it's a marketing cookie, it must be explicitly listed with its provider, purpose, and duration, and its setting must depend on user consent.