Testing Data Tracking

[srikanth_ps]

Hi there, I am facing a weird issue..we have an JS extension populating dynamic meta tags with condition (a=view)...which is then picked up by a JavaScript tag for tracking....This is currently deployed in dev only...When we load the production site and then use the tag companion to change the environment to "dev", the tag works fine....but when I open our QA site which loads dev tags by default...the tags do not fire on page load but fires ok for post page load events...what could be causing this issue?

[steve_lake]

The usual way that we start troubleshooting problems like this is to look in the javascript console to see if there are any obvious error messages. Assuming there is nothing obviously wrong, the next thing we check is that the load rules are correct and that the tag is supposed to be firing. This is often the cause for this kind of live/qa site difference - a load rule being set to a specific live-site URL, for example. Next it's a matter of looking in either the network tab of developer tools, or the sources tab (if you are using Chrome) to see if that particular tag is being loaded. If you would like us to take a look, please feel free to send an email through to support-emea@tealium.com with the details. Many thanks

[srikanth_ps]

Thanks for this..one last question...how to refer to an JS extension variable in custom container code...is it "b." etc?

[roshan_gonsalko]

Hi Srikanth, Yes, you'll be able to refer to it via the 'b' object. If you've mapped it then you can refer to the mapped name by u.data.[name]. e.g. if you may 'example_data_source' to 'test' then you could refer to it as 'b.example_data_source' or 'u.data.test' Mapping to in custom containers is very powerful. You might want to read this post to learn a bit more about the power of custom containers: https://community.tealiumiq.com/posts/698275-how-to-tealium-custom-container-tag-with-mappings