Double Adobe Launch URL to the Unique Report Suite.

[prathap08]

Team,

Can we load two adobe launch URL(each from different account web property) to the unique report suite? Any impact loading double launch URL?

Example: adobe experience licensed account1 - webproperty > samedomain.com > unique-launch-url-1 > report suite 1
                adobe experience licensed account2 - webproperty > samedomain.com > unique-launch-url-2 > report suite 2

[Jennifer_Dungan]

Are you asking about adding 2 Launch files onto your website? 

As in:

<script src="https://assets.adobedtm.com/112221412/567b5756757b/launch-sefertertert.min.js" async></script>  <!-- Report Suite 1 -->
<script src="https://assets.adobedtm.com/455675675/567567575b56b7/launch-567b57567.min.js" async></script>  <!-- Report Suite 2 -->

If so, yes, this is a big problem as these two files will load instances of the same resources that will conflict with one another.

If you need to track to 2 separate tracking, there are other ways to do this....

I am not sure what you mean by "adobe experience licensed account1" and "adobe experience licensed account2".. are you saying you need to track to two separate companies or organizations?

This is going to be a big problem, if you are talking about two separate organizations, with your ECID values which are tried to a specific Org.

If you are talking about two different companies within the same org, it should be less of an issue.

Now depending on the above, are the tagging profiles the same? i.e. eVar1 is the same in both suites, eVar2 is the same, event26 is the same, etc? If so you can just sent the calls to multiple suites in the same call... however, if they are different tagging profiles, you can create multiple tracking objects in the same Launch property to keep the tracking from corrupting one another:

https://experienceleague.adobe.com/docs/analytics/implementation/vars/functions/s-gi.html?lang=en

So one suite would use the standard "s" object, and the other could use something like the "z" object.

Allowing you to set the eVars separately:

s.pageName = "suite 1 page name";

z.pageName = "suite 2 page name";

Each suite would also have its own send beacon:

s.t();

z.t();

[prathap08]

Thank you for the response. It is for two separate ORG accounts. 

Example:-

ORG 1 > Webproperty > Launch URL > Using under the www.example.com > sending the data to ORG1 > Report Suite 1

<script src="https://assets.adobedtm.com/112221412/567b5756757b/launch-sefertertert.min.js" async></script>  <!-- Report Suite 1 -->

PLAN IS TO:- 

ORG 2 > Webproperty > Launch URL > Using under the same www.example.com > sending the data to ORG2 > Report Suite 2

<script src="https://assets.adobedtm.com/455675675/567567575b56b7/launch-567b57567.min.js" async></script>  <!-- Report Suite 2 -->

Expectation is to receive the data to both report suite `1 (ORG1 account) and report suite (ORG2 account). 

(this is kind of short term test to create various dashboard along with ORG1 and ORG2 related domains under one ORG account i.e., ORG2)

[Jennifer_Dungan · Accepted solution]

Adobe highly recommends NOT having two copies of Adobe Launch on your site, but having 2 orgs, you may not have an option... however, you will definitely need to use the above:

https://experienceleague.adobe.com/docs/analytics/implementation/vars/functions/s-gi.html?lang=en

to change how one of the suites collects (s object to z object) to try and avoid conflicts... but on top of that, I am worried that your ECID data will get corrupted... since the system is not designed to generate two identifiers for different organizations.

Do you have a CSM (customer success manager)? I would reach out to them and have them get you some help from Adobe on how to successfully track this without messing up both accounts.....

This will likely also require a lot of custom code implementation, just so you are aware.... 

This is beyond most of us, since most of us do not have to track to multiple organizations... multiple suites, yes... to multiple companies, on occasion... but multiple orgs is extremely tricky since each org has their own ECID values that will cause some issues....