Adobe Experience Platform Web SDK cookies

Last update: 2024-10-16
  • Topics:
  • Cookies
    View more on this topic
  • Created for:
  • Experienced
    Admin

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

Name Max age Size Description
kndctr_<ORG_ID>_identity 34128000 (395 days) 100-120 bytes (variable) Stores the ECID, as well as other information related to the ECID.
kndctr_<ORG_ID>_consent 15552000 (180 days) 10-11 bytes Stores the user’s consent preference for the website.
kndctr_<ORG_ID>_cluster 1800 (30 minutes) 3-5 bytes Stores 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.
mbox 63072000 (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.
mboxEdgeCluster 1800 (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_###@AdobeOrg 34128000 (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.

On this page