Adobe Experience Platform Web SDK cookies

Last update: October 16, 2024

CREATED FOR:

  • Experienced
  • Admin

The Adobe Experience Platform Web SDK uses cookies to store values specific to your implementation.

NameMax ageSizeDescription
kndctr_<ORG_ID>_identity34128000 (395 days)100-120 bytes (variable)Stores the ECID, as well as other information related to the ECID.
kndctr_<ORG_ID>_consent15552000 (180 days)10-11 bytesStores the user’s consent preference for the website.
kndctr_<ORG_ID>_cluster1800 (30 minutes)3-5 bytesStores the Edge Network region that serves the current user’s requests. The region is used in the URL path so that the Edge Network can route the request to the correct region. If a user connects with a different IP address or in a different session, the request is again routed to the closest region.
mbox63072000 (2 years)Present when the Target migration setting is set to true. It allows the Target mbox cookie to be set by the Web SDK.
mboxEdgeCluster1800 (30 minutes)Present when the Target migration setting is set to true. 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.
AMCV_###@AdobeOrg34128000 (395 days)Present when idMigrationEnabled is enabled. It helps when transitioning to Web SDK while some parts of the site are still using visitor.js.

The Edge Network sets all 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.

Experience Cloud


Behind the Brew: App Builder

Behind the Brew

Learn everything you need to know about how to use App Builder to integrate Adobe Commerce with any other eCommerce application. We'll cover everything from gaining access to building frameworks for data transfer.

Thursday, Jul 17, 5:00 PM UTC