Collecting data with two different launch files from two different ORG accounts for same website

[RP08]

Hi Team,

We have a plan to send the www.example.com web traffic data to different ORG accounts instance parallelly.

Currently, we have implemented analytics for the www.example.com web traffic data in the "ORG Account 1" instance - Web Property/Report Suites with single launch file.

Future plan is to have different launch files from different ORG accounts in the www.example.com web pages.

ORG 1 > Webproperty > LaunchFile <script src="https://assets.adobedtm.com/*****/******/launch-ORGaccount1.min.js" async></script> <!-- Report Suite 1 --> in the www.example.com header.

ORG 2 > Webproperty > LaunchFile <script src="https://assets.adobedtm.com/*****/******/launch-ORGaccount2.min.js" async></script> <!-- Report Suite 2 --> in the www.example.com header.

Will there be any issue sending the same site(www.example.com) web traffic data with two different launch files to the respective organization account report suites?

[yuhuisg · Accepted solution]

Generally, you cannot have 2 different Tags properties in the same website. The reason is that a Tags property's underlying JavaScript object is called "_satellite". You can't change that name, it's fixed by Tags.

As a result, when you have more than one property in the same website and they all create the same named "_satellite" object, one property is always going to "win", but you can't be sure which one because it depends on which property the user's browser had downloaded and executed successfully.

You will need to find a way to consolidate your multiple tracking requirements within the same Tags property.

[Rudi-Shumpert]

As @yuhuisg stated. you can not have two different Tags properties on the same site.  It will cause numerous issues and is not officially supported.

• Multi-suite Tagging -- https://experienceleague.adobe.com/docs/analytics/implementation/prepare/multi-suite-tagging.html?la...