2 Adobe Analytics instances running on the same page | Community
Skip to main content
Level 2
November 9, 2020
Solved

2 Adobe Analytics instances running on the same page

  • November 9, 2020
  • 3 replies
  • 2886 views

Can we have 2, AA instances running on the same page.

 

One AA is being hosted by Tealium and another one from Launch.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Brian_Johnson_

@abhinav_m - What are you trying to accomplish? Are you trying to send the same data to different report suites? Different data to different report suites? Are the AA instances owned by the same org, or does one belong to you and the other belongs to another org/vendor? If you can provide more context, we might be able to provide suggestions or alternatives.

3 replies

yuhuisg
Community Advisor
Community Advisor
November 10, 2020

You can, but it's not advisable. The most immediate impact is that because you're sending 2x hits, you could exceed your licence's volume very quickly, which can increase the cost of your AA bill.

Besides that, sending such hits can lead to inaccuracies in reporting or spending more time to interpret the reports.

So, just don't.

Adobe Employee
November 10, 2020

You can, though it's not supported or recommended. It's bound to cause issues.

Abhinav_mAuthor
Level 2
November 10, 2020
Can you provide some expected issues that we might run into.
Brian_Johnson_
Brian_Johnson_Accepted solution
Level 8
November 10, 2020

@abhinav_m - What are you trying to accomplish? Are you trying to send the same data to different report suites? Different data to different report suites? Are the AA instances owned by the same org, or does one belong to you and the other belongs to another org/vendor? If you can provide more context, we might be able to provide suggestions or alternatives.

Brian_Johnson_
Level 8
November 11, 2020
@abhinav_m - I think I understand what you're trying to do... The technical challenges here may include visitor identification (ECID will be different for different orgs), namespace conflicts (if both are using the 's' object, watch out), or page performance issues if you're loading the same code (appMeasurement) more than once. I'm sure I'm leaving out many other possible issues/challenges, but these would be some of the major things to watch out for.