ECID ITP and Cross Domain Tracking Concerns

[#1]

We have been evaluating using ECID with an AppMeasurement tracking project that is in progress.  We want to make that our new tracking created from this project is as future proof as possible.  We have multiple domains involved with our websites (mainwebsite.com with a separate bookingdomain.com for purchases) so it is critically important that cross domain tracking work accurately and that visitors are properly linked together across domains.  At a high level we have come to the below findings but want to make sure from an Adobe ECID expert (who is familiar with ITP and recent updates) that we are making the optimal choices.

• Current direction based on our research
• Move forward with ECID and use the appendVisitorIDsTo function to allow our cross domain tracking to work.
• CNAME – it seems that it would be optimal to use a data collection CNAME for our website domains.
• Concerns/Questions
  • demdex.com and demdex cookie – this is a third party cookie and is blocked by Safari and Firefox (ITP) which could break our cross domain tracking?
  • Article where demdex.com is mentioned as having cookies explicitly blocked by Firefox:  https://medium.com/adobetech/a-review-of-browser-privacy-initiatives-and-proposals-4ae86edc23c
  • 
• Will link decoration using the appendVisitorIDsTo function be blocked by browsers in the future and will this function work properly today in Safari/Firefox?
• Will using CNAMEs help our cross domain tracking be accurate in browsers that block third party cookies like Safari and Firefox?  We have seen inconsistent articles that suggest this may or may not help.
  • Articles:
    • https://experienceleaguecommunities.adobe.com/t5/Adobe-Experience-Cloud-Audiences/ECID-ITP-Cookie-De...
    • https://docs.adobe.com/content/help/en/id-service/using/reference/ecid-library-methods.html
    • https://docs.adobe.com/content/help/en/id-service/using/reference/analytics-reference/cname.html
    • https://docs.adobe.com/content/help/en/id-service/using/reference/analytics-reference/analytics-ids....

[addams · Accepted solution]

Dear Addams,

Append appendVisitorIDsTo Function is the only method I would say that can persist the visit from one domain to another domain when the browser blocks the third party cookie. Check out my take on Google Recent announcement to 'phase out' third party cookies on Google Chrome and its impact on Adobe Analytics Cross-Domain Tracking: Reference Link. This might give you a clear idea!

So, use the method and go ahead with your implementation.

Thank You, Arun.

[addams · Accepted solution]

Hi Pratheep,

Thank you for the insight and your article was very helpful. 

- In addition to using the appendVisitorIDsTo function, do you think we should also setup a CNAME (https://docs.adobe.com/content/help/en/id-service/using/reference/analytics-reference/cname.html) for our websites to help with cross domain tracking and ECID?  Or does the CNAME not help with ECID/cross domain tracking?  It would be a lot of additional effort for us to setup CNAMEs for the large number of websites that we own so we only want to do this if there is benefit.

- Do you have any idea if the appendVisitorIDsTo function, the URL parameters/querystring variables (www.destination.com?adobe_mc=MCMID=1234|MCAID=5678), or the cookies created (MID) will be blocked by browsers (Safari, Firefox, and Chrome) in the future since this is considered link decorating/decoration?

Thank you.

[PratheepArunRaj · Accepted solution]

Dear Addams, 1. CNAME is not required since ECID set Visitor ID Cookies in same domain i.e. First Party Cookies. 2. Browser will never block a first party cookie until there is an alternative. And adding Query String to our URL should never be a problem since it is a part of URL Structure. But make sure you domains are open to Query String, some domains/platform restrict Query String for Security Purposes (Like Post Login). Thank You, Arun

[addams · Accepted solution]

Hi Pratheep, thank you for the additional details and your responses are very helpful.  Much appreciated.

[addams · Accepted solution]

Hi Arun, I recently posted this similar post. Could you possibly help me out with your thoughts on this issue? https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/cross-domain-iframe-ecid-...

[#7]

I think this might be an issue with cross domain tracking via CNAME below. It's from the 3rd link you posted. I had the same question myself. 

If you are also using this same data collection server on other sites (for example, myothersiteA.com, and myothersiteB.com), and a visitor later visits these sites, the cookie that was set during the visit to mymainsite.com is sent in the HTTPS request to the data collection server (remember that browsers send all cookies for a domain with all HTTPS requests to that domain, even if the domain doesn’t match the domain of the current website). This is what is known as using a cookie in a third-party context, or just a third-party cookie, even though you are using a CNAME. Adobe recommends a CNAME for each unique domain.

Note: Safari blocks all cookies in the third-party context regardless of how they are set.

I think your best bet is to use Visitor.appendVisitorIDsTo - that's what I have inferred from the many different references, and what Adobe shared with me.