Tealium Learning Center

Hi @ssundar yes, there is a way to adjust utag.js default behaviour. The feature you most likely are looking for is called utag_cfg_ovrd - put settings in a preloader extension and utag.js changes loading behaviour accordingly. I found one of @adrianbrown replies describing some of the settings here ... View more

Hi Shree, Assuming that you have set up "link" event tracking correctly on the button(s) using a trigger from e.g. a jQuery extension that calls the utag.link tracking function, it could be related to the tag containers' templates lack of event type support. Some containers are "born" to only support "view" events out of the box. For example many conversion tag containers are by default born with "view" event only. If you want a tag to fire under other conditions, you would have to modify the template to your custom needs. You can adapt your tag template to support more events in your local profile. First, create a new "Save As" entry in your versions history (so you can roll back if needed). Then locate the following line of code in the tag template (find edit button to the template editor under tag config > advanced settings) and then try update the line containing u.ev from: u.ev = {"view" : 1}; To: u.ev = {"view" : 1, "link" : 1}; Remember to save "Version Template" (recommended, so you can roll back to a previous version) + publish. If this does not solve your problem, you are welcome to DM me and I'll be happy to take a look at your exact setup. Let us know how it goes. Kind regards, Kevin ... View more

Hi Christian, you are very welcome. Glad I could help. Have a great day. Kind regards, Kevin ... View more

And to add, yes - you can put in script tags <script></script> and put inline code in there, to manipulate the Tools DOM. Just keep in mind the DOM is re-written for every send call. ... View more

Hi Christian, The Tool window is completely rebuilt from bottom-up for every call you do from the JS main file to tealiumTools.send ({.. : .. }) which is why you will need to detach and re-attach e.g. jQuery callback listeners again if you put inline code within the Tools windows' HTML. I would not recommend trying extending handlebars, rather, you are probably much better off utilizing the provided Bootstrap (3) framework and use jQuery for the eye candy stuff to get the job done with the least amount of effort required. Your time is better spent elsewhere than fighting with the internal loading mechanisms of the Tool infrastructure itself (been there, done that). Kind regards, Kevin ... View more

Hi Christian,  Just updating the reply. All communication from the page to the Tool window happens via an Iframe postMessage, so all data has to be passed via the message object from the Tools corresponding js file. Simply read what you need from window in there, and pass it to the Tool via the provided send method.   Kind regards, Kevin ... View more

Hi @aswathi, It looks to me that the b object is out of "runtime" scope - i.e. b does not exist when the click handler fires. Try to change the reference to utag.data.prop53 instead - assuming that the variable prop53 is present there. If this does not get you on the right track, post a link to the page where you are trying to get it to work and I'll take a look for you. Kind regards, Kevin ... View more

Hi @darsha You'll need to load, i.e. go into, the lib-global library profile, make your changes there and then publish those changes to e.g. PROD (to the linked environment in your parent profile). Then navigate back to your parent profile. In there you should now see an orange "save/publish" button indicating that a change has been made (an asterisk * will indicate changes). Now you would then publish the configuration changes to e.g. DEV/QA and test the parent profile configuration against your website. When finished and happy with the changes, then publish your parent profile to DEV/QA/PROD and you are done. Kind regards, Kevin ... View more

Hi Ben, yes this looks indeed like a timing challenge. Depending on how you scoped the extension, a tag container's default "fire" mechanism is at dom ready, which means that performance.timing.loadEventEnd is already set when your code snippet runs. First, try scope the extension to the Adobe tag and change the tag container's wait flag to "no" and see if that makes a difference. If this does not work, then try "bundle" the tag (so it will be embedded in utag.js and hence fire at the earliest convenience) and if that does not work either, then maybe you can get away with removing the condition check altogether and let the busy loop kick in immediately: if (performance.timing.loadEventEnd == 0) { .. } If you are still having problems, I'd be happy to take a stab at the challenge, if you PM me with your account/profile and website URL to where the setup is currently in place and I'll take a look. ... View more

This sounds like you either have a draft that needs approval to go to prod, or as Per mentioned, check the top right corner of the extension in question. ... View more

Hi Dave,   If you are using the Tealium Target extension to define your mbox, if there is a timeout (default 7 seconds), the publish engine logic injected into the utag.sync.js file should set the container ID to visible again if the requested mbox (content) is not returned in time (default 7 seconds). Note, there is no content blocking involved.   There might be other challenges in your exact scenario. I'll help you with sorting your current issues. Kind regards, Kevin ... View more

I forgot to tell you that the passed object will become reality for that particular call. That is why you only see your changes to 'b'. So instead of doing all of the above (you can of course do that if you need to be able to do more "house cleaning" on utag.data when "claudio" event is happening) but you could just update the utag.data object with the new pre-condition for your lookup table extension and then call utag.track with utag.data as argument. I think that would do it, without the need for your custom container tag merging data from 'b' onto utag.data. For example: utag.data.my_data_source = "something else"; utag.track("claudio", utag.data); Both flavors should work, though I would not recommend doing too much of this stuff so please be careful. In an ideal world when pre-conditions to the page change, pass in a new fresh object every time and do not reuse previous data from the sticky utag.data object on the page. In a very heavy ajax environment, it makes it very hard to maintain. The data object (UDO) data sources, at least the vital ones like page_name, page_type, product_ids etc, should be provided and maintained by the developers of the website, not built and maintained inside Tealium. ... View more

Hi Claudio, Depends on the extension scope I guess. JavaScript code copy pasted inside extensions and scoped to all tags / specific tags are by default wrapped in an anonymous function scope, i.e. not possible to trigger them without calling utag.view / link. However, if you define your in page data layer modification functions in a pre-loader / dom ready scope, and make them referenceable (named functions) then you can trigger them at will. I assume you are planning on overloading an in page function? If you really want to take the creative hat on, you could try run all tags scoped extensions (your lookup table extension) without firing tags, by passing in a dummy value to utag.track directly: utag.track("claudio", { "data_source_name_trigger" : "new value to consider" }); By calling utag.track with a custom value as first argument, no Tealium IQ tag templates will know about "claudio" event, unless you have explicitly modified a profile template to react to the "claudio" event type. Not knowing your exact challenge you are dealing with here, but perhaps your day-to-day SE can help you with iterating over it with you. Please note that extensions are designed to run in conjunction with what is supposed to be considered a page view and / or click data ultimately triggering tag technologies to fire. ... View more

Hi Kevin, Try this. In a JavaScript extension, you need to refer to "b" to get access to the consolidated data layer. Remember you will also need to map the data source "data_sources_joined" to the final evar destination in the tag's mapping table. /** * join 3 arrays with data into 1 data source example */ if (b.Quantities && b.Quantities.length) { for (var i = 0; i < b.Quantities.length; i++) { var joined = []; joined.push(b.Quantities[i]); // if Sizes at array index i exist if (b.Sizes && b.Sizes[i]) { joined.push(b.Sizes[i]); } // if Upload_Status at array index i exist if (b.Upload_Status && b.Upload_Status[i]) { joined.push(b.Upload_Status[i]); } // join the data at array index i with a colon separator b.data_sources_joined[i] = joined.join(":"); } // finalize the data with pipe separator b.data_sources_joined = data_sources_joined.join("|"); } ... View more

if you look at variable e, it contains everything concatenated in one string, separated by colon matching the array index and pipes. This code here is obviously just an example. What UDO variable array names do you have these values in? ... View more

Hello Kevin, Try this in google chrome console: var a = ["a1","a2","a3"]; var b = ["b1","b2","b3"]; var c = ["c1","c2","c3"]; var d = []; for (var i = 0; i < a.length; i++) { d[i] = ([a[i], b[i], c[i]]).join(":"); } var e = d.join("|"); ... View more

Hello Iwan, If you log into Tealium IQ, goto the data layer tab, and click the little down arrow next to "add data source" button + click "add common data sources". On the left hand side menu, you can choose to auto-populate data sources with naming conventions recommended by Tealium. Kind regards, Kevin ... View more

Hi Jarno, If you scope a JavaScript extension to a tag and the return value is a boolean false, it should prevent the tag from firing. For example: if (window.location.pathname === "/home"){ return false; } ... View more

IS POPULATED is also a good one. It checks for the data source is defined AND it has a value. ... View more

Agree with Ty. If you want this library loaded on every page, pre-loader is the way to go. ... View more

Hi Andreas, I would probably start with using the Tealium Generic Tag container and/or download the source code and host it inside the template depending on whether it is required to be hosted at their servers. If you go to the tag eco-system and search for "tealium" you will find it. Kind regards, Kevin ... View more

If you for example create an "all tags" scoped javascript extension inside your sub-loaded profile and put in the code: b.hello = "world"; + publish to e.g. dev or qa. When the utag.js file has the updated timestamp, locate the extension inside utag.js and put a breakpoint on that line inside the extension i.e. function(a,b) closure. - if you can't see the b.abPage data source when the breakpoint is active, then we might need to take a deeper look into it. You can email us at support-emea@tealium.com with page details / what to click on to see the abPage data source in question and we'll be happy to look into it for you. ... View more