Same site domain and subdomain using different tracking server

[michaela7702973]

We have a website currently https://www.oldwebsite.com, using tracking server smetrics.oldwebsite.com. This site's URL/domain will change to https://www.newwebsite.com. I've initiated the steps to implement a new first-party SSL certificate for first-party cookies for the new domain. When this process is over and the domain change is in effect, I will edit the settings in Launch and set the tracking server on www.newwebsite.com to smetrics.newwebsite.com (the new tracking server). This is all fine.

However, we also have a related subdomain, subdomain.oldwebsite.com. This subdomain will not change yet to the new domain, it will be continue to be subdomain.oldwebsite.com for the time being even after the domain change on the www. This subdomain is set up as a different property in Launch. It's set up to use the tracking server smetrics.oldwebsite.com.

Data for both the www and the subdomain go into a single report suite. Therefore, my concern is - I will have https://www.newwebsite.com using tracking server  smetrics.newwebsite.com and a related subdomain subdomain.oldwebsite.com that's not changing for now and will still use tracking server smetrics.oldwebsite.com and they both use the same report suite. Is this fine? Will data from both tracking servers be added to the report suite?

[Andrey_Osadchuk · Accepted solution]

The data will come to the report suites regardless of what tracking servers the beacons are sent to as long as the CNAME is configured correctly.

However, what you should be ready for is that the visitor will unlikely be identified as returned visitor when they come to the new domain (a new ID will be assigned).

Best wishes,
Andrey Osadchuk | Inspect Launch Implementation, Automate Classifications & Data Sources, Essential Bookmarks