Tealium Learning Center

Hello,   I have an important case where we need to upload a tag template/JavaScript code regularly. The process of creating of the code does use a continuous integration system, but currently there is no automatic transition of transferring the artifact (JavaScript code) to Tealium iQ.   The only way I know is to manually edit a tag template or JavaScript extension and transfer the code via Cut and Paste.    Looking at the Data Layer Enrichment API in https://community.tealiumiq.com/t5/Tealium-API/Data-Layer-Enrichment/ta-p/14619, I have the hope that there is a way to not only upload JSON but also JavaScript directly.   Do you have a solution for me that uploads JavaScript code into an tag template/JavaScript extension via an API? While taking MFA into consideration?   Thanks in advance, Michael   ... View more

Hello,   has anyone had experience with the onHandler in conjunction with require.js?    We are trying to use the jQuery onHandler extension in TiQ, but it is silently failing. When trying a command on the console, it fails (as is expected) with "Uncaught TypeError: $ is not a function" when not using require().   Probably, some kind of call such as this would be needed outside of the code generated by the onHandler Extension:   require(['jquery'], function($) { ... })   As of now, the only solution seems to be to write a Javascript extension to trigger tracking. Is there a way to get the standard onHandler Extension to work with require.js so that people without JavaScript permissions will again be able to implement Event Tracking?   Thanks in advance, Michael ... View more

Hello, I have a question concerning the placement of utag.js in a static HTML document without UDO. The aim is to add Tealium to parts of a web site where the modification of source code is expensive due to process reasons. Adding utag.js as a one off process is feasible, building a best practice conforming UDO is economically forbidding. Tealium will mainly be used to extract information from the corresponding web pages and feed that into a Collect Tag. The information on the page will be present in javascript variables and the DOM. Timing is not essential, but being sure that the javascript variables on the page are accessible to Tealium is. My question is: where should we best place the utag.js call in this case, right below the opening body tag (usually best practice) or at the bottom of the page, below all the (static) data and javascript variables? What would be the advantages, disadvantages of the two solutions? I am leaning towards placing the utag.js at the bottom, so that we know that all data is present on the page when TiQ runs and we can immediately use an extension to set the data values in the data layer. As opposed to, say, placing utag.js at the top and firing the Tags on DOM Ready and scoping the data setting Extensions to the relevant tags, hoping that they will have the correct timing. Is there a recommendation on utag.js placement under these circumstances? Thanks in advance, Michael ... View more