Hi all We are looking at ways to better organise data layer, extensions and tags in modular libraries. In an environment with many different profiles, the whole stack of the datalayer and extensions is rarely used by one profile. Instead, there are some profiles that make use of e-commerce variables (and related extensions), some only need a basic setup and others are content platforms that would require yet another set of datalayer variables and extensions. We could easily split up the data layer and extensions in logical "packages". The problem is mapping variables to tags with a large number of mappings, typically Analytics tags. Ideally, those tags would be managed in one place. But given the diversity of the platforms, the mapping would be very different for the a.m. profile types. Not feasible with the ootb tag mapping. The idea is to do the mapping in a Javascript extension scoped to the respective tag. Ie. overriding the *u.map* part of the tag template with that extension. Is that something you would recommend or is there another way to achieve a flexible mapping? Many thanks for your thoughts
... View more