Adobe DTM: using a new property vs a new container

Avatar

Avatar
Validate 1
Level 1
michael_feiner
Level 1

Like

1 like

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
michael_feiner
Level 1

Like

1 like

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
michael_feiner
Level 1

19-12-2017

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 50
Employee
Kaushalendra
Employee

Likes

65 likes

Total Posts

142 posts

Correct reply

69 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Boost 50
Employee
Kaushalendra
Employee

Likes

65 likes

Total Posts

142 posts

Correct reply

69 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 10
View profile
Kaushalendra
Employee

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

Answers (3)

Answers (3)

Avatar

Avatar
Level 1
michaelf7823341
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile

Avatar
Level 1
michaelf7823341
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile
michaelf7823341
Level 1

18-01-2018

Thanks Jantzen.

Avatar

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,338 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,338 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

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

Avatar

Avatar
Validate 1
Level 1
michael_feiner
Level 1

Like

1 like

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
michael_feiner
Level 1

Like

1 like

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
michael_feiner
Level 1

09-01-2018

Thank you Kaushlendra