How can you prevent a particular utag.link from firing an Adobe Analytics call?

[jon_narong]

I have a certain utag.link() call (identified by one of two unique UDO variables) that I'd like to exclude from firing a server call in the Adobe Analytics tag. How can I do this?

[adrian_browning]

Your best option would be in a JS extension scoped to the Adobe Analytics tag, check for the UDO variables, and if the check fails, return false. A simple example would be: if ("link" === a && !b['someVar']) { //Check if link AND if the variable is loose false; I.E. undefined or empty string, etc return false; }

[craig_rouse]

You could also use a load rule if you're using utag.js version 4.36 and above. Here's how: Import the bundle of data sources called "Tealium built-in data", described on this page: https://community.tealiumiq.com/t5/Tealium-iQ/Data-Layer-Wizard/ta-p/13556 Now you can use the variable called "(UTAG) event" in a load rule and combine it with a test for your UDO variable. e.g. (UTAG) event equals link AND is not defined (or not populated etc.).

[lukas_oldenburg]

Hi Master Craig, we use utag version "ut4.36.201507131252" I tried just that: 1. I created a Data Source "webtrendsflag" 2. Created a Set Data Values Extension that sets the "webtrendsflag" to "false" (as a text string) if "event category" = "content" 3. Changed the load rule for the Webtrends to fire whenever "webtrendsflag" does not equal "false". => Webtrends still fires on every utag.link call, even when event category = "content". Master Adrian's solution worked by the way, but I prefer the load rule approach as it is something which the JS-not-allowed users could do themselves as well. And it is personally concerning because I was sure this was going to work and told my client to go for this (Craig's) solution for some of his other tags - I will lose all credibility... (ok, maybe not... :). Lukas

[adrian_browning]

Hi Lukas, As of yet extensions will not run before load rules. But that update is coming. So setting a value in an extension and then testing the load rule will not work. If you have imported the "Tealium Built-in Data" bundle, as Craig described, you will then be able to create a loadrule, that is similar too: "event category" is not "content" AND "(UTAG) event (ut.event)" is not "link". Then add this to the list of load rules for the tag as an AND. That should have the affect that you are looking for. If you would like to have a chat about getting this set-up I'm more than happy to jump on a call. Adrian

[lukas_oldenburg]

Thanks! So do I understand you correctly that what Craig described is not available yet? We have this extension from Roshan that checks load rules again AFTER extensions have run, but obviously this won't solve the problem because the load rules are ALSO checked BEFORE Extensions (if I understand the extension correctly), and before the Extensions the load rule fits, just not after that. I'd love to chat with you on that. I asked Niall O'Shea to give you my Skype contacts.