- Identity Service Help
- Overview
- Implementation
- Implementation methods
- Implementation guides
- Implement with Experience Platform tags
- Implement for Analytics
- Implement for Target
- Implement for Analytics and Audience Manager
- Implement for Analytics, Audience Manager, and Target
- Using the ID Service with A4T and a Server-side Implementation of Target
- Direct Integration with the ID Service
- Direct Integration Use Cases
- Test and verify the ID Service
- Opt-in Service
- ID Service API
- ID Service API Overview
- Configuration
- Configurations overview
- audienceManagerServer and audienceManagerServerSecure
- cookieDomain
- cookieLifetime
- disableIdSyncs
- disableThirdPartyCalls
- disableThirdPartyCookies
- idSyncAttachIframeOnWindowLoad
- idSyncContainerID
- idSyncSSLUseAkamai
- loadTimeout
- overwriteCrossDomainMCIDAndAID
- resetBeforeVersion
- sdidParamExpiry
- Secure and SameSite configurations
- secureCookie
- useCORSOnly
- whitelistParentDomain and whitelistIframeDomains
- Methods
- Methods
- appendSupplementalDataIDTo
- appendVisitorIDsTo (Cross-Domain Tracking)
- callTimeOut Methods
- ID Synchronization by URL or Data Source
- getInstance
- getAnalyticsVisitorID
- getCustomerIDs
- setCustomerIDs
- getMarketingCloudVisitorID
- getLocationHint
- getVisitorValues
- isClientSideMarketingCloudVisitorID
- resetState
- Reference
- Reference Overview
- Analytics Reference
- Analytics Reference Overview
- CNAME Implementation Overview
- Setting Analytics and Experience Cloud IDs
- Order of Operations for Analytics IDs
- ID Service Migration Decision Points
- ID Service Migration Scenarios
- Analytics and Identity Requests
- Server-side Implementation Mixed with JavaScript
- The ID Service Grace Period
- Google Chrome SameSite labelling changes
- Content Security Policies and the ID Service
- COPPA Support in the ID Service
- CORS Support in the ID Service
- Customer IDs and Authentication States
- ECID library methods in a Safari ITP world
- Identifying Unique Visitors
- Get Region and User IDs From the AMCV Cookie or the ID Service
- Requirements for the ID Service
- Video Heartbeat and the ID Service
- Data Workbench and the ID Service
- SHA256 Hashing Support for setCustomerIDs
- FAQs
- Release notes for ID Service
Analytics and Experience Cloud ID Requests
An overview of how the Experience Cloud Identity Service works with the legacy Analytics ID.
Summary
Historically, the Experience Cloud Identity Service has been integrated tightly into Adobe Analytics. It remains an integral part of Analytics but now performs important functions for other solutions and features in the Experience Cloud. Because of this historical legacy, checking for or writing an Analytics ID works a little differently than with the generic process described in How the Experience Cloud Identity Service Requests and Sets IDs…. For additional information on the order of operations for checking IDs, see Setting Analytics and Experience Cloud IDs.
The AMCV Cookie is Not Set in the Browser
If the Experience Cloud (AMCV) cookie is not present, then an ID service call to Adobe generates a response that varies depending on the presence or absence of a legacy Analytics ID. The legacy Analytics ID is stored in the s_vi cookie. The table below describes how IDs are written to the AMCV cookie based on the state of the s_vi cookie.
| s_vi Cookie Status | Description |
|---|---|
| s_vi Cookie is Not Set |
The ID service assigns visitors a Experience Cloud ID (MID). The MID identifies your visitors to Analytics and other Experience Cloud solutions. |
| s_vi Cookie is Set |
When a site visitor with an s_vi cookie first encounters the Experience Cloud Identity Service, this service:
Note: With a grace period, the data center response always includes a legacy ID that is stored in the s_vi cookie. During the grace period, the legacy ID is written to the AMCV cookie as the AID value. |
Users identified by the s_fid cookie will not have their legacy FID value migrated to the AMCV cookie. With an s_fid cookie, users will be migrated as if no s_vi cookie was present (see above) and appear as new visitors to your site. See Analytics Cookies for more information.
The AMCV Cookie is Set in the Browser
If the AMCV cookie is present, Analytics will use the MID as the Analytics identifier if there is no legacy Analytics ID value in the cookie.
