When to use and when NOT to use DTM
05 Dec 2015 » Launch
I must admit that, initially, I was a bit perplexed and did not know exactly what to reply. This was the first time I received this question and I had never thought about it. However, I quickly came with a proper answer and this is what I suggested. It must be noted that this is my personal perspective, not Adobe’s.
In order to reply to this question, you must first think about governance. Who manages DTM? Who owns DTM in the company? What is the purpose of using DTM? I think that DTM is a marketing tool, managed by the marketing department, used to deploy marketing tags in a website. So, if the new piece of code that needs to be added to DTM is requested by the marketing department, then it will probably make sense to use DTM; on the other hand, if it is the IT department requesting the addition, I would recommend against using DTM for it.
So, to summarise, from my point of view, here you have some cases that are suitable for DTM and cases that are not:
- In DTM:
- Not recommended in DTM:
- Website functionalities (chats, UI effects)
- Code that needs to be executed in a very specific location of the page (i.e. not at the top or the bottom)
- CMS libraries
Can you think of any other case that would fit in one or the other case? If so, please, leave a comment!