Analytics Cookies

Adobe Analytics uses cookies to differentiate requests from different browsers and to store helpful information that an application can use later. They may also be used to associate browsing information to customer records.

In particular, Analytics uses cookies to anonymously define new visitors, help analyze clickstream data, and track historical activity on the website, such as response to particular campaigns or the length of the sales cycle.

More information is available in Analytics help about First-Party Cookies.

Cookie Name: s_ecid

Attribute Description
Information Stored Contains a copy of the Experience Cloud ID (ECID) or MID. The MID is stored in a key-value pair that follows this syntax, s_ecid=MCMID
Expiration 2 years
Usage This cookie is set by the customer’s domain after the AMCV cookie is set by the client. The purpose of this cookie is to allow persistent ID tracking in the 1st party state and is used as a reference ID if the AMCV cookie has expired. Check AMCV cookie here for more details.
Location CNAME customers only. Not applicable for 3rd-party scenarios. Cookie is stored on your domain, the same domain used by CNAME and your Analytics image request.
Size 45 bytes

Cookie Name: s_cc

Attribute Description
Information Stored This cookie is set and read by the JavaScript code to determine if cookies are enabled (simply set to “True”)
Expiration This cookie is a session cookie and expires when the browser is closed
Usage Only one cookie for all accounts
Location This cookie is stored at the domain of the page
Size 4 bytes

Cookie Name: s_sq

Attribute Description
Information Stored This cookie is set and read by the JavaScript code when the ClickMap functionality or the Activity Map functionality are enabled; it contains information about the previous link that was clicked on by the user
Expiration This cookie is a session cookie and expires when the browser is closed
Usage Only one cookie for all accounts
Location This cookie is stored at the domain of the page
Size Varies depending on page URL size, but typically 100-200 bytes

Cookie Name: s_vi

Attribute Description
Information Stored Unique visitor ID time/date stamp
Expiration 2 years
Usage This cookie is used to identify a unique visitor
Location This cookie is stored at the domain of the image request - typically a customer-specific subdomain under 2o7.net or omtrdc.net if you are using third-party cookies, or if your domain is using first-party cookies.
Size 44 bytes
NOTE

Each Analytics visitor ID is associated with a visitor profile on Adobe servers. Visitor profiles are deleted after 1 year of inactivity regardless of any visitor ID cookie expiration.

Cookie Name: s_fid

Attribute Description
Information Stored Fallback unique visitor ID time/date stamp
Expiration 2 years
Usage This cookie is used to identify a unique visitor if the standard s_vi cookie is unavailable due to third-party cookie restrictions. Not used for implementations that use first-party cookies.
Location This cookie is stored on your domain as a first-party cookie.
Size 33 bytes

The following table describes the flags for Analytics cookies:

Cookie (set by) httpOnly Secure SameSite
s_vi (http Response) No Yes when SameSite is “None” and connection uses HTTPS “Lax” by default when using CNAME. “None” when using 2o7.net or omtrdc.net.
s_ecid (http Response) No No “Lax”
s_fid (Javascript) No No Unset
s_cc (Javascript) No No Unset
s_sq (Javascript) No No Unset
NOTE

If using a single CNAME to track across multiple domains or properties, SameSite should be set to “None” for s_vi. For help changing Analytics cookie settings, contact Customer Care.

Cookies Set By Plug-ins

Additional cookies can be set depending on the use of Analytics plug-ins. These cookies are snippets of code available to the client for use in a variety of circumstances. These circumstances include: retrieving values from the URL; concatenating values to pass to Analytics; capturing form abandonment, and so on. For specifics on cookies that are set by each plug-in, contact ClientCare. An example would be the s_vh cookie used with the Set Once Per and Set and Get Last Value plug-ins.

Conversion variables (eVarX) passed in on a image request without JavaScript, such as code placed within an email, are attributed properly only if the email client and web browser share the same cookie space.

On this page