Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Adobe DTM: using a new property vs a new container

michael_feiner
Level 1
Level 1

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

1 Accepted Solution
Kaushalendra
Correct answer by
Employee
Employee

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.

View solution in original post

4 Replies
Kaushalendra
Correct answer by
Employee
Employee

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.

View solution in original post

jantzen_belliston-Adobe
Community Manager
Community Manager

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.