I would like to redefine the way the DataLayer is handled in TIQ.
The DataLayer in a organisation should preferably follow some rules that make it consists across all/most sites and apps. And the mapping between the datalayer and tag should also be the same. So for a account there should be a option to define one (or more) global DataLayer + Tag + Mapping that can be inherited by all libraies and profile where this is needed. (based on Pull or Push definitions)
There should still be the option to add DataLayer parameters in lib and profile level including the mapping. As local variables. This would requrie that the tag mapping is not locked on profile level as it is today when a tag is inherited from a library, or in this case the Global DataLayer.
So we should work with a global account defined Datalayer that covers maybe 80% of the setup and then there is option to make local supliment. This would dramatically reduce or time used in mapping and parameter alignment. And ensure consistency. As example we have 8 libraries that all use 90% the same DataLayer, and then all need a new tag, that need 100% the same mapping in all profile. If this came from one centralized place we would save a lot of time.
It can be seen as a extra layer of libraries but it should not have the functions as a library. There should not be a need for publish etc. Because the DataLayer is always pushed to profiles if thats the setting.
(Note: I just realized that @bjoern_koth have posted a similar idea a few hours ago - but it's a little unclear for me if it is the same concept - so i will let it be for now, and let the community manager decide)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.