Tag Bundling based on Publish Environment?

[james_hartley]

During Digital Velocity there was a short conversation around Tag Bundling. Will there be an option in place in the future to bundle our tags based on environment? I know that I can accomplish this now by keeping different publish settings for each environment but this is tedious to maintain. I would like this to be something that we can keep static for PROD but have the tags not bundled for testing in all other environments.

[dan_george · Accepted solution]

Hi Jim, Just curious what is trying to be accomplished here. If you are trying to debug, you can still find each tag template's code at the bottom of utag.js. Also, each tag call is still a separate log event that can be seen in the network tab. Let me know and I can provide more information.

[james_hartley]

Hey Dan, Thanks for the response. My reason for this questions was 2 fold 1. There was a short conversation at the DV Tech Training on bundling and the environment settings and thought it would be a good idea to re-visit 2. It may be useful to our Content and DEV teams (non-analytics teams) to be able to see the separate JS files in the "Sources" tab for our lower environments but keep it bundled in PROD. Also, many of our enterprise js files are bundled in prod but load separately in DEV, TEST etc. and it would be nice to easily align our analytics implementation with those practices. This is not a must have - just something that may be helpful. Cheers!

[dan_george]

Hi Jim, I have submitted an enhancement request on this and the Engineering team will review. Personally I'm a little weary to provide this option. I prefer to test with the exact configurations that will appear in production. This is two fold. First since Tealium is asynchronous, and second since the order of events in Tealium is important. By bundling you are changing the order of events occurring and depending on the configurations in place this could negatively effect the implementation. For example, in dev they could be appending a variable to the UDO low in the page and since our tags are running at DOM Ready the variable is picked up. However, with bundling enabled we are running the tag much sooner in the page and the variable can be missed and therefore not reported. Either way, Engineering will determine the feasibility and your account manager can keep you up to date on the status.

[james_hartley]

Hey Dan, Thanks for the info. I will wait for an update.