Tealium Learning Center

Thank you for your comprehensive suggestion. I also take that as an answer that Tealium currently doesn't provide a feature out of the box to support this :) We will be using Onetrust as our CMP provider. I know from a previous talk with our CSM that Tealium is partnering with a different CMP provider. So we will see if the upcoming Consent Integrations feature will help us to simplify our solution. For now we will build something like suggested. Thanks again for your respones. Best regards, Andreas ... View more

I'm just going to hit the Collect Http Api: https://docs.tealium.com/platforms/http-api/endpoint-spec/   Essentially, I need to track user consent behavior without collecting any PI data.  ... View more

In terms of rollback in a profile that has library inheritance, I guess my issue is that it does not technically exist. You can fix-forward by reverting to older snapshots of various libraries / the profile itself but the concept of a true rollback is not one that's been implemented, but presumably could be..? Each publish produces a distro bundle, to enact a genuine rollback you would simply need to push an older distro to the CDN, perhaps sensibly constrained such that only a previous prod build could be pushed to prod. Then for the more granular stuff, when to inherit etc., for me I think it makes the most sense to have some sort of timeline tool not unlike the current client-side versions feature, which in a profile would give you the ability to look across all the inherited libraries, and using a master slider pick a point in time at which to inherit the latest (at that point) version that's eligible for inheritance. And then beneath that, library-level sliders that would allow the user to set custom inheritance on a specific library if they so wished. The default would always be "current", and maybe the standard behaviour would be that the slider snaps to profile publish events, so the simple-mode experience is that you can simply drag the whole set of inherited libraries to their state at a given publish within your profile. But the complex-mode experience would let you pick any moment in time, and split those timings by library. Use case would be - three days ago I performed a production publish and one of the tags that's been configured in an inherited library is leaking a data item to a vendor that they should not be receiving, and it's severe enough that I want to be able to perform a fix without reverting the entire publish. But time has passed, new features have dropped in other inherited libraries ready for the next scheduled publish, but I need to perform a hotfix now to sort this one issue and I'm not intending to launch any new features. The owners of the affected library have ensured that what's published there today is what was in the last release, plus the fix, nothing else, but I can't go around another five teams' libraries reverting everything they've done this week, perhaps I shouldn't even have the access to do so. So, I go into the Timeline view in simple-mode, drag the master slider back to our last production publish, enable complex-mode, and then find the affected library and drag its slider to "current". Now the content of my publish is the inherited libraries at their position at my last publish except for the one library that requires an update, which is inherited in its current state. The way I'm envisaging it working in the backend would be effectively that each library publish is in effect a commit to the branches (environments) to which it's published. From my profile I don't see details of the development branches that users within the library are using to manage their own code, but I do see a stream of commit/publish events that I can roll back to a specific point in time for the purposes of what I'm inheriting. I'm probably just reinventing Git submodules or something, so this might all be terribly derivative, but you get the idea.. Bonus feature: The ability to specify for a given publish what the minimum version of other libraries/profiles within the account needs to be for that publish to work. Because interdependencies between inherited libraries do exist and they're awkward. If I make a change to my Webchat library to enable a new supplier and my Analytics library contains code that adds event listeners to the new webchat dialog, I need to be able to specify within my Analytics library that a given publish expects that the Webchat library will be at least as recent as insert date here. Or use tags as sort of feature flags so that you have a dependency on a specific tag being present in the other library, I dunno.. but what you want to avoid is a scenario in which an interdependency between two libraries is a) not made visible to users and could be forgotten about and b) cannot cause weird side-effects if one library is rolled back and another that depends on now-reverted code isn't rolled back. And finally, the feature I'm describing above would also work for maintaining stable releases vs nightly release tracks etc., wherein you might have a main profile that takes the most recent version of every library it inherits, and a near-identical main-stable profile that has all its sliders fixed at a given point in time, only moved when a new version is considered stable having been shown to be issue-free in production. "Can't you just do that already, freezing the stable version by not publishing the profile?" you might ask, and not quite, because at the point of publishing that profile, you're getting all the absolute latest versions of the libraries, which might not be the versions that you want to include in your stable release. Furthermore, if you needed to make any reference data changes (e.g. update a marketing tag campaign ID that has expired) without functional code changes, you'd have to re-inherit the whole set of libraries at their current state including all code. ... View more

Or, if you want an absolutely nuclear way of doing this stuff.... var perfTotals = {}; function pwrap(owner,fname,rname){ var original = owner[fname]; owner[fname] = function(){ var perfStart = performance.now(); var r = original.apply(this,arguments); var perfEnd = performance.now(); perfTotals[rname] = (perfTotals[rname] || 0) + perfEnd - perfStart; // if(perfEnd - perfStart > 10) console.log(rname,perfEnd-perfStart); return r; } }; var exclusions = [window,utag.o]; function rwrap(obj,prefix,depth){ if(depth > 4) return; if(exclusions.indexOf(obj) >= 0) return; for(var k in obj){ if(typeof obj[k] === "function"){ pwrap(obj,k,prefix + "." + k); } else if(Array.isArray(obj)){ obj.forEach(function(item){ rwrap(item,prefix + "." + k,(depth || 0) + 1); }); } else if(typeof obj[k] === "object"){ rwrap(obj[k],prefix + "." + k,(depth || 0) + 1); } } } rwrap(utag,"utag"); utag.view({}); var maxlength = 0; for(var k in perfTotals){ if(k.length > maxlength) maxlength = k.length; } console.log( Object.keys(perfTotals) .sort(function(a,b){ return perfTotals[b] - perfTotals[a]; }) .reduce(function(c,v){ c += v; c += (function(stringToPad){ var output = ""; for(var i = stringToPad.length; i < maxlength + 2; i++) output += " "; return output; })(v); c += Math.floor(perfTotals[v]); c += "\n"; return c; },"") ); This will recursively wrap all the functions found within the utag object or its descendants up to a depth of four, and then fire an event, and tell you how long everything took (with repeat invocations adding to the total): utag.view 937 utag.track 937 utag.handler.trigger 937 utag.handler.RE 203 utag.sender.928.send 146 utag.tagsettings.adobe.visitorAPI.getInstance 131 utag.sender.1428.send 115 utag.sender.1428.o 106 utag.handler.C 106 utag.sender.1216.send 93 utag.sender.1216.o 92 utag.sender.928.o.t 68 utag.handler.LR 66 utag.sender.1024.send 50 utag.sender.1024.o 49 utag.loader.loadrules 46 utag.sender.928.o.Ea 41 utag.sender.928.o.d.querySelectorAll 40 utag.sender.1459.send 39 utag.ut.typeOf 33 utag.loader.GV 31 utag.loader.RD 30 utag.sender.911.send 29 utag.sender.928.o.isReadyToTrack 27 utag.sender.928.o.pb 26 utag.handler.extend.59 26 With the evident caveat that if function a invokes function b, the total execution time for b will be included in a, hence why utag.view, utag.track and utag.handler.trigger have roughly the same duration here - view invokes track, track invokes trigger, but the end to end execution time remains 937ms.   ... View more

The only way you'd be able to do that is by adding event handlers to the Tealium script reference itself, and then using those to detect whether the script was correctly loaded and if not send that information somewhere (keeping in mind that anybody blocking Tealium is likely to be using a fairly strict ad blocker which would prevent most normal data collection endpoints associated with web analytics). There's nothing Tealium can do to detect that blocking because they never receive the network request in the first place. ... View more

@awarwick Although Tealium is on the list, Tealium iQ is not affected. The single Tealium domain listed (.tealiumiq.com) is only used for data collection for the server-side platform components (AudienceStream, EventStream). The client-side platform is not affected by this. The reason for the distinction is that no data is collected by Tealium iQ, and it is often used to serve important content such as consent management platforms (including the Tealium consent manager), which can be essential to the operation of a website. Individual vendor tags served through Tealium iQ, may of course still be blocked by disconnect.me, but the core Tealium iQ scripts are not blocked, as they don't collect any data. ... View more

Hi @pedrochristobal, If the data is stored in a first party context relative to the page the user is on, you should be able to pick up that cookie value within the UDO, it'll be called: cp.aam_something So it'll be accessible in extensions as b["cp.aam_something"], and if you add the item to the UDO in TIQ, you'll be able to map it to other tags. If the data is truly a third-party cookie, you won't be able to access it client-side because web security depends upon not being able to access cookies cross-site. Hope that helps. Cheers, James ... View more

I don't necessarily recommend this, but..... Identify the tag that you want to be portable, and edit its template via the top-right menu. Practically the last line of the tag code should in theory be: }('##UTID##', '##UTLOADERID##')); Replace this with: }(window.portableTagId, (function(u){ for(var k in u.o) return k; })(utag))); Next, in the profile to which that tag usually belongs, add the following pre-loader scoped JS extension: window.portableTagId = 1072; // replace this number with the ID of the tag in this profile In the profile you want the tag to newly appear in, create a new tag, and select "Tealium Custom Container" as the type Under advanced settings, for Custom Script Source, select the full URL of the tag file in its normal location, e.g. https://tags.tiqcdn.com/utag/account/original_profile/prod/utag.1072.js // look up the ID from the profile that owns the tag Make a note of the ID of the new container, and add a pre-loader scoped JS extension as follows: window.portableTagId = 16; // replace this number with the ID of the container tag in this profile And that should. in theory, do it. You can repeat steps 4-6 to put the tag into other profiles if you so wish. What we're doing is effectively instructing the tag to load itself into whichever profile it finds on the page (rather than the hard-coded injection of ##UTLOADERID##), using a dynamic tag ID so that it registers itself against the ID that corresponds to the right config (e.g. load rules) in the profile in which it finds itself. Then in each target profile, you're configuring that dynamic tag ID, and creating a container as a placeholder for the tag against which to create load rules etc. You won't be able to vary tag-scoped extensions between profiles, nor mappings, at least not without some custom code, but it should be sufficient to make a tag portable between compatible accounts (e.g. same UDO etc.) ... View more

Hi @surabhi_sharma2, If I'm reading this correctly, is the problem that s.clearVars() isn't being run between events, causing values to be persisted through successive events? If so, there should be an option within the tag configuration to clear variables between calls, but if you already have an existing implementation that otherwise works, then be careful enabling it - it could be that other behaviours within your Adobe tag are dependent on not running s.clearVars(), and enabling it might break things that otherwise work, so lots of regression testing required.. ... View more

@UnknownJ Just an FYI, most of our tags include logic to stop the tag firing tracking if the main vendor ID is not provided. In the case of GA, if there is no Tracking ID assigned in the tag, it will do nothing at all. Technically, there is no need for a Load Rule to check if GA ID exists, so you can scope the extension to the GA tag directly. ... View more

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

Hi @loldenburg,  Do you mind giving it a shot now? I just confirmed the URL redirect with our community platform provider, and tested it with success. Feel free to send me a private message if you see anything else amiss.    Kristen  ... 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

Thank you, Ben! ... 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

Thank you. The problem was that the elements i wanted to track was not loaded when i tried to define my vars. I did'nt know I could scope to dom ready so i made my own dom checker and now it works, but ill try to set the scope instead. I do need to up my debuging game :)     ... 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 :) Also, the scope of the values on different pages is different and hence captured in different UDOs depending on page type ... View more