Different Adobe Launch Scripts (Org IDs) on domain and subdomain and to report on end-to-end journey

[Nidhi_Shastri]

Dear Experts,

Need your expert opinion on a situation. Consider a Parent Content Website ABC.com where mostly all paid campaigns land onto and further it routes the users to different products purchase path. From the content website ABC.com the visitors can go to the subdomain xxx.ABC.com and purchase the product. But both ABC.com and xxx.ABC.com have different Adobe Launch Scripts as they belong to different departments altogether. The Adobe Analytics implementation on xxx.ABC.com is just a basic OOTB and not yet customised. I am responsible for implementing and reporting Adobe Analytics on xxx.ABC.com. The ask from the business is to connect the journey and know how many visitors were sent to ABC.com via campaigns and how many purchased from xxx.ABC.com. Due to Adobe Analytics handled by two different organisations its a tough situation how to technically report on end-to-end journey. In my opinion the best method would be to use the Adobe Launch script of ABC.com on xxx.ABC.com (after deleting the current one) and co-own the property with the parent organisation. but in this case the control and publish rights of the tags belong to ABC.com so if xxx.ABC.com wants to implement any third party tags or introduce any new implementation we need to depend on ABC.com to verify and publish the tags from Staging env. Our business want to keep the full control of tags. Could you please suggest what could be the best way to report on end-to-end journey from ABC.com to xxx.ABC.com considering both have different Adobe Org IDs and if we want to keep full control for xxx.ABC.com. 

[Jennifer_Dungan]

This is an hard one... 

Technically, I control the code for our main www site, and all the subdomains... I used different Launch script for each code base... so www.domain.com is using Launch property A and sub1.domain.com is using Launch property B and sub2.domain.com is using Launch property C, and so on...

But all of the Launch properties on are on the same Org ID... so that the ECID is consistent, and also, I send all the data into the same suite.

Honestly, I don't think it's remotely possible to do an end-to-end journey if you are on a separate Org ID.... The ECID (user identifier) is set per Org... even if the cookie was set against .domain.com so that it is shared with all the subdomains, the data is stored in completely different accounts and properties.

In theory, you might be able to stitch the journey together in an external Data Lake, but you can't even do a proper journey analysis across multiple suites, let alone across multiple orgs....

I get the need to maintain control of your own code and tags though.. but unfortunately, I think that will prevent any likelihood of stitching together the user journey...

The best you could hope for would probably be to use internal campaign parameters to pass some info about what page / function / etc sent traffic from the main site to the sub-domain, and vice versa... it won't give visibility to the whole journey, but can provide some information about where the user was and what they were doing when they switched.... 

[bjoern__koth]

Hi @Nidhi_Shastri 

as @Jennifer_Dungan says, different OrgIDs lead to different ECIDs, which make an e2e reporting challenging.

You could check if the appendVisitorID functionality of the Visitor ID service could work. But this would also require adaptations on your other organization's launch property. The idea is to modify link URLs between domains that cannot read each other's cookies like a link from A.com to B.com, yet still belong to the same OrgID.

Your case is slightly different though, but maybe worth a try.

Else you could look at the referrer information to detect traffic from your other subdomains, but this would surely not give you the whole picture, since you  will essentially end up with different ECIDs and inflate the Unique Visitors numbers.

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

If you won't get access rights to the other Launch property, maybe they could clone it within the same Org and give you access to that? There you could work on and ask them to incorporate your changes in their main property. Worked for me at other clients.

They can just copy your rules/data elements over after reviewing them.