Tealium Learning Center

In our implementation, we use a tag-scoped extension on a single tag to have it run consistently across multiple domains, performing a lookup from domain to site ID. So at most, you'd only need the two tags, one global, and one country/site specific, but it may even be possible to run both trackers off the same Tealium tag (assuming they're both running analytics.js), though that's not something I've had to implement myself.. ... View more

I can't rule out having caused our corruption in the first place - one of our team had gone through creating and mapping like 100 data items as Page JS Variables instead of UDO Variables, so I ran an update to utui.data.define to change the types of everything (as opposed to deleting, recreating, and then remapping), and it was after that that I first saw the issue... In terms of what that code does, for the curious, I believe it iterates over tag ID 1's mapping, excluding keys that fail a hasOwnProperty check, excluding relationships that don't have a dsID (data source ID?), and then for each entry checks the UDO definition for the variable mentioned in the mapping. If the data source ID in the mapping object matches the corresponding UDO variable ID, then it skips the rest of the loop. If not then it updates the data source ID in the mapping to the ID for that variable in the UDO. So my assumption is that the mapping object within the tag correctly identifies the variable name (so when published, it comes out correctly) but gets its source ID corrupted, and the UI is powered by a lookup on that ID rather than the name, which is why the UI doesn't match either the intended mapping, nor the published output. In my experience, mismatched IDs have tended to be the result of issues with library inheritance, but at this point it's all just idle speculation.. :o) ... View more

Hi @jbenavidez2, You're referencing the b object, but at the point where the event takes place that object isn't in scope. You should only reference b when using an All Tags or Tag Scoped extension that works on the current event payload. In the case of a click handler, you're dealing with the DOM Ready creation of an event listener, so in your example you will need to manually fire a Tealium event. So instead of references to b, you should initialise your own object, and at the end of the code, emit that to Tealium, so along the lines of: var payload = { event_source: "jQuery Extension" }; payload["value"] = $("#amount").val(); payload["event_source_id"] = $(this).attr("id"); utag.link(payload); ... View more

Hi @jbenavidez2, You're referencing the b object, but at the point where the event takes place that object isn't in scope. You should only reference b when using an All Tags or Tag Scoped extension that works on the current event payload. In the case of a click handler, you're dealing with the DOM Ready creation of an event listener, so in your example you will need to manually fire a Tealium event. So instead of references to b, you should initialise your own object, and at the end of the code, emit that to Tealium, so along the lines of: var payload = { event_source: "jQuery Extension" }; payload["value"] = $("#amount").val(); payload["event_source_id"] = $(this).attr("id"); utag.link(payload); ... View more

Yeah, we had something like this happen to us too.. @adrian_browning fixed it for us, with the following script run in the console: var map = utui.data.manage[1].map; for (var mapId in utui.data.manage[1].map) { var mapObj = utui.data.manage[1].map[mapId]; if (!utui.data.manage[1].map.hasOwnProperty(mapId)) {continue;} if (!mapObj.dsID) {continue;} var result = _.where(utui.data.define,{name : mapObj.key, type : mapObj.type}); if (result.length === 0) {continue;} [result] = result; if (mapObj.dsID === result._id) {continue;} mapObj.dsID = result._id; console.log(mapId, mapObj.dsID,mapObj.key, result._id,result.name); } ... View more

Hi @AdityaTiwari, utag.loader.GV is a function that returns the properties of an object that pass the hasOwnProperty check u.map is an object that contains the mapping of UDO variables to vendor parameters (as configured in the Tags tab of TIQ), so for example: u.map = { page_title: "WT.ti", page_category: "WT.cg_n,DCSext.page_category" } So that first line of code iterates over that mapping object, where each loop has "d" taking the value of each UDO element that's to be mapped to a vendor parameter. In the second line then, b[d] is the current value of that UDO element in the current data payload that's been passed into the tag. The if statement checks that the variable for mapping is defined and not blank within the current payload. An undefined or blank UDO element won't be mapped into the tag. The third line then looks up the target vendor parameter, and splits it on a comma in order to produce an array, since a single UDO variable can be mapped to multiple vendor parameters. The fourth line then iterates over that array, so e[f] represents each individual vendor parameter. The fifth line then might otherwise read as: tag.data[target_variable] = payload[udo_variable] Based on that mapping defined in the interface and stored in u.map. So in the mapping example above, we might end up with the following assignments being made: u.data["WT.ti"] = payload["page_title"]; u.data["WT.cg_n"] = payload["page_category"]; u.data["DCSext.page_category"] = payload["page_category"]; Hope that helps, let me know if you need any further clarification. ... View more

It's likely, @Jayakrishnaa, that a user's browser is automatically translating some text on the screen into Russian, and that translated text is then being scraped by either Tealium or Adobe and is being picked up as it appears on the page. We often see Page Titles that have been translated into Polish etc. coming through on ours, one way of fixing it would be to store the original value of the link in a data attribute of that element and then retrieve that when the link is interacted with rather than its observed .text() value. ... View more

Hi @LongPun  The b variable within an All Tags extension running either Before Load Rules or After Load Rules will contain the event payload that was passed into the utag.link call, the solution above will definitely work. I think it's worth debugging your code using the information here to check what's happening. ... View more

The main problem you're going to get here is that if you only attempt to load the tag on the click, @brett-bold, the browser isn't going to have enough time to fetch the utag.x.js file and then drop the pixel on the page before it aborts all outstanding network requests and navigates on to the next page. You could speed that bit up by creating a UDO element that effectively detects whether a qualifying link is available on the page, potentially writing that to utag_data at DOM Ready. So long as the tag itself is scoped only to a link event, the pageview will load the tag but won't fire the tag. Then use a tag-scoped JS extension that identifies ineligible click events, and suppresses the tag firing for those. Something like: if(b.event_name != "outbound_click") return false; That will then abort the tag send if the link event wasn't an outbound click event. Alternatively, bundle the tag so that you don't need to load it remotely on the page. Either way works, and should cut down the network traffic and give you a better chance of punching through. The ideal approach would be to either: Open off-site links in a new window, giving the old window all the time it needs to complete its various tag sends, or Use an event listener on the link clicks to prevent the default navigation behaviour for a brief period while tag firing takes place, and then navigate the customer onward after say 800ms (which should be enough for an SSL handshake etc.) - it's bad customer experience, and requires messing with the site a little, but it'll work In general, firing off network requests when the browser is trying to navigate off the current page is always risky - if the HTTPS handshake to LinkedIn hasn't completed before the browser gets a response from the page it's navigating to, it'll abort the request and the payload will never reach the LinkedIn data collection server, which will impact your conversion metrics on certain (faster) browsers. ... View more

Added additional security on API calls that edit tag templates. Out of interest, what change is that, @TealiumJustin? Just thinking, I've got some code kicking about somewhere that uses the tag template API, would be handy to find out in advance of trying to use it if it's not going to work any more :o) ... View more

So, @mukherr, this will give you a quick view of which profiles inherit from which libraries, just paste it into the dev tools console in Chrome or similar while logged into TIQ: var p = utui.profile.import._profiles; var op = ""; for(var k in p){ op += p[k].name; for(var i = 0; i < p[k].imports.length; i++){ op += "\n " + p[k].imports[i].name; } op += "\n\n"; } console.log(op); Alternatively, this will give you a CSV that contains all relationships to stick into a graph database: var p = utui.profile.import._optionalLibraries; var op = "Profile,Library"; for(var k in p){ for(var i = 0; i < p[k].imports.length; i++){ op += "\n" + p[k].imports[i].name + "," + p[k].name; } } console.log(op); Explore the _profiles, _optionalLibraries and _requiredLibraries properties of the utui.profile.import object in the TIQ UI for more detail.. ... View more

The first thing to say is that the target structure isn't an array, at least not a valid JS array, it looks more like a delimited string, so the following is an attempt to arrive at that outcome:   var sku_combined = []; if(b.sku.length == b.sku_price.length){ for(var i = 0; i < b.sku.length; i++){ b.sku_combined.push(JSON.stringify(b.sku[i]) + ";" + JSON.stringify(b.sku_price[i])); } } b.sku_combined = sku_combined.join("|");     Which will set the "sku_combined" UDO variable to the following string: "925913";"64.99"|"893200";"74.99"|"893201";"89.99" If the vendor really needs that wrapped in square brackets, you can do it as part of that last operation, but to me it feels a bit weird to start wrapping it in what looks like a JS structure when it's not valid JS... ... View more

I've not had this problem, @iris-tan, when dropping multiple Doubleclick tags onto a page - each one can have a separate variable mapping in Tealium, and when they fire, they go into separate iframes with distinct IDs. The only issue I've ever had was with re-firing an existing Doubleclick tag before the connection had been established in the iframe, but that doesn't impact you if you have separate tags within TIQ. ... View more

Yeah, you just create a Set Data Values extension and map your UDO variable to the JS Code expression "navigator.userAgent" and it ought to work right out of the box. ... View more

I've not seen a better approach than using a Set Data Values extension to grab the following useful properties from the navigator API: doNotTrack language userAgent maxTouchPoints If you want to be lazy and do it in pure JS, something like this would work: ["doNotTrack","language","userAgent","maxTouchPoints"].map((v) => b["nav." + v.toLowerCase()] = String(window.navigator[v])); (might want to run it through Babel to de-ES6 it) It populates the following UDO elements: nav.donottrack nav.language nav.useragent nav.maxtouchpoints From their respective navigator properties. ... View more

Hi @Sshuichci The first thing is to make your API key dynamic, by creating a UDO variable to hold it, and then mapping that into the tag configuration (ideally using a pre-defined mapping that comes as standard with the tag, but I'm not familiar with Amplitude). Then set that UDO variable based on the environment currently detected. You could use a lookup table or a Set Data Variables extension, but I'll just give the example in pure JS: if(b["ut.env"] === "prod") b.Amplitude_API_key = "your_production_api_key"; if(b["ut.env"] === "qa") b.Amplitude_API_key = "your_testing_api_key"; if(b["ut.env"] === "dev") b.Amplitude_API_key = "your_development_api_key"; And in theory that should sort you out.. Give me a shout if you need any further detail. ... View more

Ah, I think we might have looked at solving the same issue. In our case, we wanted to: Not have any vendor-specific code on pages so that any future change of vendor didn't require an HTML code change, and Not risk causing JS errors if a customer's ad blocker prevents utag.js from loading There are two approaches you can take. The first is to create wrapper functions for utag.view() and utag.link(). If handling utag.js unavailability is your primary goal, then try the following: // Add this code to all your pages window.utag_view = function(){ // do nothing }; window.utag_link = function(){ // do nothing }; // Add this code to a DOM Ready Tealium extension window.utag_view = window.utag.view; window.utag_link = window.utag.link; That'll basically give you a set of utag_view and utag_link functions which will be inert if utag.js hasn't loaded, but once utag.js has loaded, they'll be repointed to be references to the built-in utag.view and utag.link functions. Then any time you want to trigger a link event, use utag_link - if Tealium is there, it'll be routed via the utag function, otherwise it will fail gracefully. If you were to later change your tag management vendor, you could just repurpose those two functions and point them at the alternative vendor. The other approach is to build all of your tracking within Tealium itself, so never fire events from the page, but rather create event listeners. In our case, we used custom attributes against on-page elements, for example: <input id="0.1.1.1.2" name="txtTitle" data-analytics-narrative="Customer Title" data-analytics-tracking="full" data-analytics-persist="customer_title" /> Those attributes describe the field in question in a reporting-friendly way, the expected behaviour for an event (do we capture an interaction, capture the value of the interaction, or capture nothing?) and the UDO variable into which we might persist the value thereafter (if needed). Then we used jQuery to track blur events against input elements, registering the event handlers in a Tealium extension, and used the custom attributes against the element in question to populate the event payload before pushing it into utag.link, all within Tealium extensions. Hope that's of some use.. ... View more

Not currently, @alok, but there's a feature suggestion here: Alerts, email notification and Slack integration I'd suggest you go and add your support to it to get it prioritised on the roadmap. ... View more