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....
- Articles:
