Tealium Learning Center

This is the situation: country A wants a site that is managed by a worldwide corporation. The only way they can have it is by accepting the default setup as all the other country sites. That means that tracking/datalayer is implemented as it is, and is handled by Tag Manager B.   Now we want to implement Tealium in Tag Manager B. So first B will load, and then it will load Tealium as an extension. This is the only exception they're wanting to make on the default setup. All datalayer fields will be 'translated' to Tealium syntax. And all events are send through B to Tealium with a utag.link call. The rest of all the scripts/pixels/etc will be implemented in Tealium.   What is your opinion about this? Can/will it break? Will we get timing issues with certain scripts? Other thoughts? ... View more

One of my clients wants to fire a few pixels after 15 and after 30 seconds. Tealium has no standard Load Rule feature to fire tags after X amount of seconds. So the first solution was a custom javascript extension scoped on "Dom Ready":    setTimeout(function() { var example = new Image(); example.src="http://url-of-pixel"; }, 15000)   I stripped the code as far as I could. In my clients case they have 5 pixels that are fired filled with datalayer elements (utag_data["example"]) and are fired on different pages. And the code was also different in that it counted the amount of seconds a visitor was on a site, and it would count on when navigating to other pages. The main disadvantage: only people with coding skills could add new pixels. And if they wanted to add new pixels with different cookieconsents (based on if visitors allowed only functional or all cookies), they also needed a coder. Now I made 3 new extensions to create the firing behavior I want. First the timer extension: /* Main script to start a timer that tracks session time per second and stores it in a cookie */ function TLD() { var parts = document.domain.split("."); return parts[parts.length - 2] + "." + parts[parts.length - 1]; } function readCookie(name) { var nameEQ = name + "="; var ca = document.cookie.split(';'); for(var i=0;i < ca.length;i++) { var c = ca[i]; while (c.charAt(0)==' ') c = c.substring(1,c.length); if (c.indexOf(nameEQ) == 0) return c.substring(nameEQ.length,c.length); } return null; } function createSessionCookie(name,value) { document.cookie = name + "=" + value + ";domain=" + TLD() + ";path=/"; } function updateCookieCount() { var actualcount = readCookie("delayed_pixels_timer"); if (actualcount != null) { actualcount = parseInt(actualcount) + 1 } else { actualcount = 0;} createSessionCookie("delayed_pixels_timer", actualcount); if (actualcount < 32) { setTimeout(function() { updateCookieCount() }, 1000); } } setTimeout(function() { updateCookieCount() }, 1000);  This script triggers a timer that updates a sessioncookie every second. So when a visitor goes to the next page the timer will continu where it stopped. This extension is scoped on "Dom Ready". Change the "32" in the script if you need it longer then 32 seconds. The second extension looks like this:   /* Scope to the tag(s) that you want to delay Adjust the timeout in the script below It will only fire once per session */ if ( !b.tag_delay && a == "view" ){ function readCookie(name) { var nameEQ = name + "="; var ca = document.cookie.split(';'); for(var i=0;i < ca.length;i++) { var c = ca[i]; while (c.charAt(0)==' ') c = c.substring(1,c.length); if (c.indexOf(nameEQ) == 0) return c.substring(nameEQ.length,c.length); } return null; } var spendtime = readCookie("delayed_pixels_timer"); if (spendtime != null) { spendtime = parseInt(spendtime); } else { spendtime = 0; } if (spendtime < 15) { var timeout = 15 - spendtime; var dataLayer = utag.handler.C(b); setTimeout( function(){ dataLayer.tag_delay = true; utag.view(dataLayer, null, [id]); }, timeout * 1000); } return false; } In the "Scope" field you put all the tags that need to be delayed. If you need an extra timer for let's say 30 seconds you just copy this extension, scope it to the appropriate pixels and change the "15" on both locations to whatever you need. My client is now able to create new pixels that have normal loadrules (for several types of cookie consents or different url's, etc) without the need to code. After the creation of the pixels they open the 15-second extension and put the new tag in the scope of that extension.  Any thoughts? ... View more

I'm in the middle of cleaning up my clients Tealium account. I've followed these steps: Check which loadrules don't have any active tags connected, set them to inactive Check which loadrules are still fired based on existing URL's and events and set the other loadrules to inactive Check all tags that are old, or have loadrules that are inactive, make them inactive What remains are a lot of extensions (including custom javascripts that fill datalayer fields) and datalayer fields. How to clean them up? If a datalayer field isn't mapped to a tag, loadrule or extension it's safe to remove it? Perhaps I do a search through the extensions for "utag_data" or "b[" or "b." to make sure the fields aren't used, and then delete the datalayer field? What's left are the extensions. How to check if they are still used? I think I have to manually check each one of them to see if it's still in use? ... View more

Based on a visitors cookie-consent level we launch Google Analytics with or without the displayfeatures. If you turn it on Tealium will load:     ga("require", "displayfeatures")     But if you turn it off Tealium will load nothing and Google Analytics listens to the property settings. There you can turn it on/off also.   I change to Google Analytics Tealium template from:     if (u.data.displayfeatures === "true" || u.data.displayfeatures === true) { u.all("require", "displayfeatures");     to:     if (u.data.displayfeatures === "true" || u.data.displayfeatures === true) { u.all("require", "displayfeatures"); } else { u.all("set", "displayFeaturesTask", null); }     To ensure the displayfeatures are always turned on or off in the script so the property setting are overriden. So far so good. But if you fire an event after 15 seconds with the utag.link function:     utag.link({ gua_ec: "category", gua_ea: "action", gua_el: "label", gua_ni: true })     Tealium creates a new GA tracker (which is ignored, cause the tracker already exists) and sets the following line:     ga("require", "displayfeatures")     Even when the displayfeatures are turned off?   How is this possible? Looks like a bug?   My solution for now is to change:     if (u.data.displayfeatures === "true" || u.data.displayfeatures === true) { u.all("require", "displayfeatures"); } else { u.all("set", "displayFeaturesTask", null); }     to:   u.all("set", "displayFeaturesTask", null);   to make sure the're always turned off unregarding the option you selected in the Tealium GA settings. ... View more