2 DTM containers | Community
Skip to main content
Jakub_Drhlik
Jakub_Drhlik
Level 2
Feb 6, 2018 5:17 AM UTC
Solved

2 DTM containers

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.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    jdonleyAccepted solution
    Level 8
    Feb 6, 2018 2:32 PM UTC

    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..

    View reply

    4 replies

    mathieus1867212
    New Participant
    Jun 29, 2018 3:09 PM UTC

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

    Translate
      Jakub_Drhlik
      Jakub_DrhlikAuthor
      Level 2
      Feb 7, 2018 12:00 AM UTC

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

      Appreciate it.

      Translate
      jantzen_b
      jantzen_b
      Employee
      Feb 6, 2018 11:52 PM UTC

      +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.

      Translate
        jdonleyAccepted solution
        Level 8
        Feb 6, 2018 2:32 PM UTC

        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..

        Translate
          Terms & ConditionsAccessibility statement

          Loading footer...