Adobe Experience Platform Web SDK cookies
The Adobe Experience Platform Web SDK uses cookies to store values specific to your implementation.
AMCV_###@AdobeOrgMCMID|<ECID>); larger when written by VisitorAPI.jsidMigrationEnabled is enabled, which is the default. It helps when transitioning to the Web SDK while some parts of the site still use VisitorAPI.js. The Web SDK reads this cookie to reuse an existing ECID. After the Edge Network returns an ECID, the Web SDK writes it to this cookie if the cookie is missing or contains a different ECID.com.adobe.alloy.getTldconfigure command runs and before consent is evaluated, so cookie scanners can report it as set before consent. The cookie contains only its own name and does not store behavioral or profile data.demdexdemdex.net domain. Present when thirdPartyCookiesEnabled is enabled (the default) and the browser allows third-party cookies by default, such as Chrome or Edge. In that case, the Web SDK sends identity requests to adobedc.demdex.net, which sets this cookie. Audience Manager uses this cookie to assign a unique ID and support ID sync, segmentation, modeling, and reporting. See demdex in Audience Manager cookies.kndctr_<orgId>_identitykndctr_<orgId>_clusterkndctr_<orgId>_consentkndctr_<orgId>_consent_checkkndctr_<orgId>_personalizationkndctr_<orgId>_advertisingin. The Web SDK writes this cookie when the page URL contains Adobe Advertising click parameters (s_kwcid or ef_id), or when Adobe Advertising DSP advertisers are configured. It stores URL-encoded JSON that can include search click data (_les_lsc), a hashed IP address, a LiveRamp RampID envelope (when a RampID JavaScript path is configured), and conversion timestamps used to throttle duplicate conversions. In browsers that allow third-party cookies by default, it also stores the Adobe Advertising surfer ID and display click data (ev_lcc). This cookie is set on the current hostname only. The component also loads resources from pixel.everesttech.net, www.everestjs.net (when an ID5 partner ID is configured), and your RampID ats.js path. These resources can set their own cookies, which are not listed on this page.kndctr_<orgId>_bc_session_idstickyConversationSession is enabled, so that chat sessions persist across page loads.mboxtargetMigrationEnabled is enabled. It allows the Target mbox cookie to be set by the Web SDK.mboxEdgeClustertargetMigrationEnabled is enabled. It allows the Web SDK to communicate the correct edge cluster to at.js so that Target profiles can stay in sync as users navigate across a site. When the kndctr_<orgId>_cluster cookie is not present, the Web SDK also reads this cookie to route requests to the matching Edge Network region.s_ecids_ecid=MCMID|<ECID>. Acts as a first-party backup of the ECID, primarily for CNAME (first-party) scenarios. When idMigrationEnabled is enabled, the Web SDK reads this cookie to reuse an existing ECID.The Edge Network sets all of its cookies with the secure and sameSite="none" attributes. If you currently have both secure and non-secure sections on your website, user identification can be inaccurate. When a user navigates from a secure section of the site to a non-secure section, the Edge Network generates a new ECID with the request.
Cookies that the Web SDK creates on its own, rather than at the direction of the Edge Network, use different attributes. The AMCV_###@AdobeOrg cookie and Audience Manager cookie destinations include the secure and sameSite="none" attributes only on HTTPS pages. The com.adobe.alloy.getTld and kndctr_<orgId>_advertising cookies use the browser’s default attributes.