I am setting up IBM Coremetrics (or Digital Analytics).
I have lots of attributes for all my "tags" (pageview, productview, etc.)
Thus wanted to separate each kind of tag for readability.
Indeed i have tried and had one massive tag with more than 100 values mapped and some value passed in different attributes across the available actions. This makes it hard to isolate for example all the values passed to the PageViewTag as when a datasource is used for multiple destinations they are grouped together. Moreover when you forget to add a destination something you need to locate where the datasource is located (and there is no search button) which is tedious.
At the moment i have thus setup 8 Tags for IBM, one for each type, but i am affraid that they all start throwing tags of the same kind. As I have imported the demandware extension, i don't want one tag that fires on a specific condition to throw tags allowed on all pages. i.e. the OrderTag throwing as well a ProductView tag.
What is the best practice around this kind of big setup ?
Thanks very much !
Thanks for reaching out. Ultimately your approach depends on what your data collection needs are. The value of Tealium is that it minimizes maintenance of your tags so the idea of having 8 analytics tags for the same vendor may not be the best route. At the same time it may be necessary depending on your data collection needs.
The ideal situation is a single tag and through the use of load rules and additional logic through extensions in TIQ we can tell a single tag where and when to fire. Testing the tag and data collection through the browsers' network traffic and IBM reporting console should call out any collection issues.
I recommend reaching out to your account manager to discuss your strategy and the appropriate plan of action for your requirements.
Thanks and I hope this helps!