Expand my Community achievements bar.

Webinar: Adobe Customer Journey Analytics Product Innovations: A Quarterly Overview. Come learn for the Adobe Analytics Product team who will be covering AJO reporting, Graph-based Stitching, guided analysis for CJA, and more!
SOLVED

What will be the risk or impact on change of the website domain?

Avatar

Level 5

Hi All,

We have a website that is hosted on domian abc.com and have implementation of Adobe Analytics using Adobe Launch. We would like to change the domain from abc.com to xyz.com. Could someone help me to understand the following;

 

  • What all changes we need to consider in Adobe Analytics to update the domain name?
  • What will be the impact and risk on existing report suite and analytics data?

Thank you in advance!

 

Regards

Rashid

 

1 Accepted Solution

Avatar

Correct answer by
Level 4

Hi @RashidJorvee ,

 

This is a loaded question but there are some things to consider:

  • Any logic in your tag manager which is dependent on URL/Domain
  • Any processing rules dependent on URL/Domain
  • Any segments using URLs or Domains
  • Cookies which are set against the domain name
  • ....you get the idea. If you're using a domain (full or partial) or URL in your logic across your implementation, you'll need to revisit these
  • First party collection name for analytics sever (ie: metrics.abc.com -> metrics.xyz.com
  • Settings in your library configurations which point to analytics or use analytics domains/URLs
  • Any certificates for the impacted/new domains

 

I would say that a complete and thorough audit is required of your implementations to assess the potential impact. It's a bit of an intensive process but critical for risk mitigation. Your report suite doesn't go anywhere provided you keep it intact, but you would need to update your analytics implementation to be certain that you're addressing all data points impacted.

 

You may want to run a parallel container/RSID to test pre- and post-migration (compare a set of the same pages on different domains assuming all other factors are unchanged). 

View solution in original post

1 Reply

Avatar

Correct answer by
Level 4

Hi @RashidJorvee ,

 

This is a loaded question but there are some things to consider:

  • Any logic in your tag manager which is dependent on URL/Domain
  • Any processing rules dependent on URL/Domain
  • Any segments using URLs or Domains
  • Cookies which are set against the domain name
  • ....you get the idea. If you're using a domain (full or partial) or URL in your logic across your implementation, you'll need to revisit these
  • First party collection name for analytics sever (ie: metrics.abc.com -> metrics.xyz.com
  • Settings in your library configurations which point to analytics or use analytics domains/URLs
  • Any certificates for the impacted/new domains

 

I would say that a complete and thorough audit is required of your implementations to assess the potential impact. It's a bit of an intensive process but critical for risk mitigation. Your report suite doesn't go anywhere provided you keep it intact, but you would need to update your analytics implementation to be certain that you're addressing all data points impacted.

 

You may want to run a parallel container/RSID to test pre- and post-migration (compare a set of the same pages on different domains assuming all other factors are unchanged).