Adobe DTM: using a new property vs a new container | Community
Skip to main content
michael_feiner
michael_feiner
December 19, 2017
Solved

Adobe DTM: using a new property vs a new container

  • December 19, 2017
  • 4 replies
  • 2735 views

Hello,

We are currently using one DTM Property for multiple websites. This has worked fine to date. However, we now have a new website that will be managed by a different group of stakeholders. This group of stakeholders should have admin rights for changing tags on their website. But should not be able to do so for the other websites.

The obvious solution is to create an additional property for the new website. However, I wanted to check whether there is any use case for keeping to one property for all websites and creating an additional container for the new website. What would be the pros and cons for such an approach? Would it be even possible to have admin rights at the container level?

Thank you,

Michael

    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 Kaushalendra

    Hi Michael,

    In my opinion when there are different teams working on different websites and there is no or very less visibility of changes across teams, the recommended approach would be to with the different Web properties.

    If needed, Admins can copy rules across Web Properties to avoid any redundant work and later teams can individually make changes to their copies.

    4 replies

    Kaushalendra
    Adobe Employee
    KaushalendraAdobe EmployeeAccepted solution
    Adobe Employee
    December 20, 2017

    Hi Michael,

    In my opinion when there are different teams working on different websites and there is no or very less visibility of changes across teams, the recommended approach would be to with the different Web properties.

    If needed, Admins can copy rules across Web Properties to avoid any redundant work and later teams can individually make changes to their copies.

      michael_feiner
      michael_feinerAuthor
      January 9, 2018

      Thank you Kaushlendra

      jantzen_b
      Adobe Employee
      jantzen_bAdobe Employee
      Adobe Employee
      January 9, 2018

      In addition to what Kaushalendra​ said, I'd defiantly try and keep your variable schema the same across web properties and sites even if they aren't in the same web property or report suite. Having the same variable schema will set you up for success when you try and use our integration and core services across properties and sites.

      M
      michaelf7823341
      January 18, 2018

      Thanks Jantzen.

      Terms & ConditionsAccessibility statement

      Loading footer...