ECID ITP and Cross Domain Tracking Concerns | Community
Skip to main content
A
addams
Level 2
March 4, 2020
Solved

ECID ITP and Cross Domain Tracking Concerns

  • March 4, 2020
  • 2 replies
  • 8821 views

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.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by PratheepArunRaj

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.

2 replies

PratheepArunRaj
Community Advisor and Adobe Champion
PratheepArunRajCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
March 11, 2020

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.

Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
    PratheepArunRaj
    Community Advisor and Adobe Champion
    PratheepArunRajCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    March 13, 2020
    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
    Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
    P
    Adobe Employee
    PranithakatAdobe Employee
    Adobe Employee
    September 21, 2021

    Hi Arun,

    May I know if its safe & acceptable to pass visitor Id in Url ? or any alternatives if we don't want to see the value in URL ?

    A
    Adamh44
    Level 2
    March 19, 2021

    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.  

    Terms & ConditionsAccessibility statement

    Loading footer...