Hear directly from Adobe Analytics experts who engage on a day-to-day basis in solving the most critical and complex Adobe Analytics queries. This technical session will help you understand Adobe Experience Cloud visitor identification, common pitfalls, and related industry complexities.
How Adobe Analytics identifies visitors
Intricacies of the Experience Cloud ID service
Commonly misunderstood concepts: visitor migration, grace period, and CNAME
The impact of intelligent tracking protection on visitor identification
Following the session, there was a fair amount of confusion about the role of CNAME's in visitor identification. We spoke about CNAME's in two different contexts, which I'll attempt to clarify here.
1. Cross-Domain Tracking:
For browsers that block 3rd-party cookies, including Pre-ITP 2.1 Safari, CNAME's could facilitate using the same AMCV cookie values between domains, provided that visitors first navigated to the CNAME domain, then to other domains. This option, no longer works in Safari with ITP 2.1.
The primary option for cross-domain tracking would require passing the visitor ID via the query string when navigating from one domain to another using the appendVisitorIDsTo method of the ID service object.
ITP 2.1 will remove client-side (document.cookie) first-party cookies after 7 days. The ECID service AMCV cookie is among those cookies impacted by these changes. Using a CNAME, in combination with the pending update to the ID service library, provides an effective way in mitigating the impact of this 7-day cap.
In summary, CNAME's were historically valuable in some cross-domain scenarios but will no longer address this use case for Safari users. However, CNAME's are recommended for the separate purpose of addressing ITP 2.1 first-party cookie caps (7-day). Additional details will become available as the updated ID service library is made available.
AnkitaSharmaerindavis Per our conversation after the session, setting a CNAME does not solve the cross domain issue with ITP 2.1. You mentioned that the only way to be able to do cross domain tracking properly with ITP2.1 at this time is to embed a code to the url that is going to the other domain. Can you please provide a link to the resource on where I can find out the details on implementing that?