2 DTM containers

[Jakub_Drhlik]

Hi Team,

we have a scenario where we need to run 2 different DTM containers on pages for some time for validation purposes, old (H.2...) vs. new implementation (App measurement - context data approach ). The library naming convention is different (s. vs. s_new etc.), as well as the report suites.

Do you guys see any issues doing that? Potentially any miscounting, data sent to wrong report suites and so on?

Thanks guys.

[josh_donley · Accepted solution]

You cannot run two separate DTM containers on the same page. DTM uses _satellite object namespace for its core library and there is no way to change that.  So, the 2nd DTM container will overwrite the 1st container. And.. you may see a mixed bag of weirdness depending on how much of the 1st container is loaded before the 2nd container..

[jantzen_b]

+1 for Josh's answer! Please do not try and deploy more than one instance of DTM or Launch on the same webpage. Doing so almost always results in hours of troubleshooting with a solution of removing one of the instances.

[Jakub_Drhlik]

Thank you for the confirmation. Thought so, just wanted to bounce it by the forum.

Appreciate it.

[mathieus1867212]

Even if the two containers contain completely seperate tools.  i.e.  one contains Target tool, the other contains Analytics tool?