Sub domain tracking on Adobe

[nk271]

I have a question related to domain and sub domain tracking in Adobe Analytics. I have a main domain names www.xyz.com and a sub-domain www.abc.xyz.com and I am trying to look at options for Adobe analytics (AA) implementation on the sub domain site. The main site already has AA implementation in place but the sub domain does no. There are two options in this situation, either to build new report suite for the sub domain or to build it within the existing domain. The end goal is that I should be able to build a customer journey across the sites. We are leaning towards creating a new report suite as the evars and props available for the main site are limited and we want to leave some buffer for the main site. However, the challenge with creating a new report suite is there will be two different journeys for the same visitor going to these different site. Are there any solutions where we can still track this visitor journey being on different report suites? Has anyone implemented anything similar? Thank you.

[yuhuisg · Accepted solution]

There's a third option, which builds off your second option:

Track both main and subdomains to the same report suite, then use a Virtual Report Suite to be able to report on the subdomain separately.

Reference: https://experienceleague.adobe.com/docs/analytics/components/virtual-report-suites/vrs-workflow/vrs-...

[nk271]

Thank you for your response. However, as I mentioned, I am leaning towards building a new report suite due to the limited evar availability. I may have found a possible solution to track visitors across sites using the CNAME implementation and following the steps mentioned in the article. https://www.digitalbalance.com.au/our-blog/how-to-measure-visitors-across-multiple-domains-in-siteca... Do let me know your thoughts on this solution. Thank you.

[yuhuisg]

Ok, I didn't realise that the main and subdomains had very different measurement objectives. You could also look at a global report suite (via multi-suite tagging): https://experienceleague.adobe.com/docs/analytics/admin/manage-report-suites/rollup-report-suite.htm.... NOT a Rollup because Rollups don't support pathing, which looks like it's something that you need. The CNAME approach helps in using the same visitor ID across report suites, but doesn't solve your requirement of being able to report the entire path.

[nk271]

Yuhuisg, thanks for the global report suite option however, as mentioned, our main site has limited evars available and not sure if adding the othersite report suite to the existing one will help. I am not sure if the global report suites allows more evars. In that case the solution might work but if not, we'll have to go the independent report suite but the challenge in that case would be the pathing between site as you mentioned.

[Jayakrish]

Please try to implementing the cross domain tracking on this scenario.

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

[jantzen_b]

Do any of the answers below answer your initial question? If so, can you select one of them as the correct answer? If none of the answers already provided answer your question, can you provide additional information to better help the community solve your question?