Tealium Learning Center

I agree that this is functionality that Tealium should provide, but in case anyone wants to try this brutal hack, I've run it through Babel myself and pasted the result here. ... View more

Thank you Unknownj, we wholeheatedly agreed with your sage guidance around querystring references. On July 31st, 2019 an independent  security  researcher on the internet discovered and reported a Tealium S3 bucket that contained CDN logs for a number of Tealium accounts.    In addition to a  security -related post, the researcher reached out to us in good faith and made contact with Tealium Information  Security  Team directly in order to report his findings. The S3 bucket was part of our response to internal requests to process our CDN logs relating to objects we delivered as part of the TMS service.    The logs contain object requests from our CDNs for the TMS files we delivered for you. We are disappointed that this lapse in our manual processes led to the public disclosure of our log files and have taken specific measures to ensure this will not happen again. This was a breakdown in our manual business processes and we can assure you that none of our automated  security  systems were breached and the  security  controls of our platform are not affected. The logs disclose very limited information relating to the objects requested from our CDNs and did not disclose any UDH visitor or event data.    Immediately, access to the affected bucket was removed by Tealium’s Network Operations and  InfoSec  Teams.    This incident was caused by a process breakdown involving human-error that failed to implement our required access controls.     Tealium has performed an extensive audit and has verified all S3 buckets are appropriately permissioned;    and we are focusing on automation and layered controls in order to make sure this doesn’t happen again. We value the trust you put in us and our Services and are working tirelessly to ensure we live up to yours and our own highest expectations. Matthew Pitta, Sr. Director - Information Security and Technology ... View more

It seems like Tealium is no longer on this list: https://github.com/disconnectme/disconnect-tracking-protection/commit/9158ab0bded2a6471112bae229937208fb5ca65e (see also: https://github.com/disconnectme/disconnect-tracking-protection/issues/31#issuecomment-471711233) ... View more

Hi @UnknownJ , Thank you very much! Kind regards,  ... View more

Thanks for the insight @UnknownJ  - bizarre to use colours that way.  ... View more

Just to close the loop on this thread. The best way to implement event tracking without coding your site with calls to utag.view() and utag.link() is to implement a combination of HTML5 data attributes in your page code and the jQuery Extension in iQ. More info here: Event Tracking - Understanding Your Options ... View more

Hello, The previous reply is correct. What happens is that your page reaches DOM Ready, and the document.write() is invoked, overwriting the entire page with its (invisible) content.  You could do something like this. var attr = { type: "text/javascript", src: "https://cdn.somewhere.com/my/tag.js" }; function scriptWrite(attr){ var head = document.getElementsByTagName("head")[0], script = document.createElement("script"); Object.assign(script,attr); head.appendChild(script); } Of course, since this code will execute asynchronously, you may run into timing issues during execution from an event handler.   ... View more

@Hi @SKammerlocher    This error can also be caused if you are using the web companion to switch enviroments but are also bundling tags. If this is the case then I would suggest instead of using the web companion to change envriorments to use the Enviroment Switcher Tealium Tool.   https://community.tealiumiq.com/t5/iQ-Tag-Management/Tealium-Tools-Environment-Switcher/ta-p/16027 ... View more

Hi @davidmolina, I think there are two steps here: Adopt a design pattern that suits your rollout approach, and Migrate to that pattern With that in mind, rather than using a boolean true or false against a single variable, I would instead partition my users with a (randomly assigned) number from 0-99 and use that to drop them into the appropriate treatment. You can get a random number from 0-99 with the following JS expression: Math.floor(100*Math.random()) So let's say you've got a variable test1, which takes value from 0 to 99 - to run a 5% sample, simply use a condition: test1 < 5 Now all you need to do is migrate your existing customers bsased on their wave1 value. You could do that with the following logic: if(wave1 === true){ // wave1 is set and the customer is in the first 5% sample test1 = Math.floor(5*Math.random()); } else if(wave1 === false){ // wave1 is set and the customer is in the 95% remainder test1 = 5 + Math.floor(95*Math.random()); } else { // wave1 isn't set and the customer should be placed at random test1 = Math.floor(100*Math.random()); } This should then give all your existing wave1 members a number from 0-4, all the wave1 non-members a value from 5-99, and all new customers a value from 0-99, evenly distributed. Then you simply need to update your test condition to ensure that the right number of customers are included. Give me a shout if any of that is unclear. Cheers, James ... View more

thanks @UnknownJ Totally agree about the consistent UDO but I am working on an already existing project and hence have to perform hacks in order for things to work :cathappy: Also, the scope of the values on different pages is different and hence captured in different UDOs depending on page type ... View more

I think I need to read through this a few more times, @UnknownJ.  I am particularly intrigued by your example of the prospect of bracketing the privacy manager extension with this custom extension.  Thanks for posting, really enjoy your recipes! ... View more

Hi @novikp, There are definitely ways, it depends on your use-case. For example, if your deployment uses utag.sync.js, you could make sure that the script reference includes a Math.random cachebuster (e.g. utag.sync.js?cb=0.54245424), and then have utag.sync.js write its current ##UTVERSION## value into a global variable, that's then used as a cachebuster on your request for utag.js. What that means is that every customer will be forced to download a fresh utag.sync.js with every pageview (so you lose cache efficiency there), but will always get the new utag.js if the published version has changed. This is not dissimilar to the way in which the individual tag files are cachebusted only on change, but it does impact performance due to the need to re-download utag.sync.js on every page. Alternatively, if it's just for testing purposes, you can use thing like Chrome dev tools to disable caching of resources, or add an optional cookie-based cachebuster to the utag.js request that allows you to set a cookie to force a cachebusted request. All things are usually possible, just depends on exactly what you need, and what cost (i.e. complexity, performance, changes to the way the resources are loaded) you can live with. ... View more

If the extension in question is simply one which takes a meta tag such as: <meta name="WT.sp" content="Dotcom;PersonalHome"/> And passes the value of the content attribute into the parameter specified in the name attribute, then this can be handled by the base tag natively, but Tealium is already doing a lot of the heavy lifting anyway, so you wouldn't necessarily need anything complex.. You could do it with a tag-scoped extension, running within the Webtrends tag, with the following code: for(var k in b){ if(k.indexOf("meta.WT.") == 0 || k.indexOf("meta.DCS.") == 0 || k.indexOf("meta.DCSext.") == 0){ u.map[k] = k.substr(5); } } What this does is iterates over all the UDO variables in the event payload (which includes the "meta.*" variables that Tealium automatically picks up from meta tags), identifies any with the WT, DCS or DCSext prefixes that denote a Webtrends meta tag, and then adds an entry into the tag variable mapping that pushes those into the specified variable name. So in the example above, it would create a mapping from the UDO variable "meta.WT.sp" to the target variable within the tag "WT.sp", which I believe replicates the built-in WT base tag behaviour with the minimum of fuss. ... View more

Wow, @dan_george  - that did it - I suppose I made that a lot more difficult than necessary, but it was a good learning experience for me.   Thanks so much for the pointers and guidance through the setup and context info for each aspect of the Custom Container. ... View more