Overview
The AMCV cookie (Adobe Marketing Cloud Visitor) is a first-party cookie set by the Adobe Experience Cloud Identity Service. It contains the Experience Cloud ID (ECID), which acts as the common identifier across all Adobe Experience Cloud solutions (Analytics, Target, Audience Manager, etc.). This check ensures that the cookie is present and properly initialized on every page of your site.
Why it is important
The AMCV cookie is the foundation of identity management in the Adobe ecosystem. If this cookie is missing or fails to set:
Identity Fragmentation: A single user navigating your site will be treated as multiple distinct visitors. This inflates "Unique Visitor" counts and breaks pathing reports.
Loss of Cross-Solution Integration: Without the common ECID, data cannot be shared between Analytics and Target. For example, you won't be able to use an Analytics segment to personalize content in Target.
Attribution Gaps: If the cookie is reset or lost mid-session, the "source" of the visit (e.g., a paid search click) may be lost, leading to "Direct" traffic being over-reported.
Marketing Cloud ID Service Failure: A missing AMCV cookie usually indicates that the ID Service (VisitorAPI.js or the Web SDK) is not loading or executing correctly.
Implementation
The implementation starts with creating an Audit where the user it opted out. Using this Audit, you are ensuring your tracking and identity services are firing as intended for consented users.
Here is a pre-built ObservePoint report showing pages with the AMCV cookie. (Compare this against your total page list to find gaps).
Remediation
If the AMCV cookie is missing from specific pages, investigate the following:
1. Identity Service Library Loading
The Experience Cloud ID Service must load before the Adobe Analytics library.
Action: In Adobe Launch (AEP Tags), ensure the Experience Cloud ID Service extension is installed and configured.
Action: Check that the extension is part of the library build being served to the affected pages.
2. Correct Organization ID
The Identity Service requires your 24-character Adobe Organization ID (ending in @AdobeOrg).
Action: Verify that the Org ID is correctly entered in your TMS configuration. A typo here will prevent the cookie from being generated.
3. Tracking Server and SSL Configuration
Insecure tracking server settings can sometimes interfere with cookie setting, especially on modern browsers with strict privacy controls.
Action: Ensure you are using a consistent tracking server (ideally a CNAME) and that
s.trackingServerSecureis defined.
4. Grace Period and Migration
If you recently migrated to the ID Service, ensure the "Grace Period" is configured correctly in the Adobe Analytics admin console if you still rely on legacy s_vi cookies for some users.
Action: Confirm that no scripts on the page are accidentally clearing cookies or blocking the
dpm.demdex.netcall, which is required to fetch the ECID.
Conclusion
The AMCV cookie is the "digital glue" that holds the Adobe Experience Cloud together. Ensuring its presence on every page is vital for maintaining a single, consistent view of your customers. Without it, your analytics data becomes siloed and your personalization efforts become impossible.
Regular automated monitoring via ObservePoint ensures that your identity foundation remains solid across your entire digital estate.