How to implement cross domain tracking ?

[aagk123]

How to implement cross domain tracking ? We are using adobe launch and its legacy tracking. I followed the below document but didn't work. Pasted the code in adobe analytics extension and changed the domain with respective ord ID and 

https://experienceleague.adobe.com/en/docs/id-service/using/id-service-api/methods/appendvisitorid

[Amruthesh_AG]

@aagk123You mean visitor is getting changed when you navigate to other domain?

If yes how you are fetching visitor id?

[aagk123]

We are using launch and installed same launch code to both sites.so when we move from Site A to Site B the Id changes

[bjoern__koth]

Hi @aagk123 

can you specify what did not work for you and how you implemented it?

I never really encountered any issues with this functionality.

[aagk123]

trackingServer: 
trackingServerSecure: 
marketingCloudServer: 
marketingCloudServerSecure: " 

Now how and where to find these values?

[bjoern__koth]

You can actually use the same value for all of them. It is the domain you see your tracking events being sent through when you look at the network tab and filter for "/b/ss".

[aagk123]

Actually looks like vendor is prevent url rewrite because of which I am unable to append visitor ID but luckily I can see s_ecid in the 3rd party site cookie section and I guess I can fetch and rewrite the MCID in adobe launch?

[bjoern__koth]

The key is that the necessary parameters are appended to the href of your link. One way or another, you will need to be able to get these parameter appended to the links. If you are having completely different domains, you will not be able to read these cookies. Do you see a demdex cookie on your website? That could help recreate the ECID but is the rather deprecated approach and may be a problem once third party cookies disappear 

[Jennifer_Dungan]

Typically the tracking server values (you used to have one secure and one non-secure, but now we just use the secure one for all), is typically either set up using the Adobe Server (which means all third-party cookies), or it is a CNAMED server specific to your domain... so if you have a website like www.domain.com then your tracking server might be stats.domain.com or tracking.domain.com, or some subdomain of your choice (so that the cookies can be written to .domain.com)

Now, when it comes to vendor sites... is the vendor using a subdomain of your domain (i.e. third-party.domain.com), or are they using their own domain (i.e.e domain.third-party.com or something.third-party.com)?  If they are using your own domain, they should already share the existing cookies set on your main site.. if it's their own domain it's a toss up what ECID they will get.. unless your vendor is willing to set up a CNAME record for a dedicated tracking server... in this case, you  likely it won't line up...

However, if you can't append query parameters to the vendor's URL, I am not sure how you would be able to use Launch to force the ECID (how will you get the user's ECID from your main domain onto your vendor site?)

Unless your vendor is willing to set up a CNAME record for a dedicated tracking server... in this case, you should get the same ECID in most cases, without passing anything in the URL... if the tracking server is set up for your Adobe Org, the dedicated tracking server should be able to identify the same user and set the ECID properly (without needing the append visitor ids).

For instance, I have 30+ websites, I have a tracking server for each one. I have very little site to site traffic (so I never bothered with setting up the Append Visitor Ids)... but if I open Incognito and open siteA.com in one tab (using stats.siteA.com as the tracking server), then open siteB.com in another tab (using stats.siteB.com as it's tracking server), I get the same ECID on both sites.... since the Demdex server is able to identify me as the same user, and set the proper first party cookies on both sites... 

[Jennifer_Dungan]

I've seen other people with this issue... I am not sure if the current version of the code is failing to automatically grab the Visitor Id from the query parameters...  I believe that some people solved this by creating a rule to grab the values from the parameters and force the ECID cookies, etc before the tracking is run....

While I don't think you should have to do this... you are not the first to complain about this exact issue... you might want to open a ticket with Client Care.

[Jagpreet_Singh_]

Hi @aagk123  Did you find the suggestions helpful? Let us know if you need any further information! If the solution works for you, please mark the answer as correct to help others. And if you’ve found your own solution, we’d love for you to share it with the community. Thank you!