Tealium Learning Center

 Hi @aperez, As I understand it, this tag is meant to be used for stitching visitor cookies when you are implementing Adobe Analytics by using the Tealium collect tag and Event Stream. I don't have much experience with it, but I can imagine it's meant to match the cookies from Tealium with the ones from the Marketing Cloud. Probably the connector in Event Stream just reads the aa element in utag_main: There's no need for this tag when doing a classic client-side integration. Cheers, Pablo ... View more

Hi @Palullu, ut.event key in your data layer is to be deprecated in newer versions of utag.js template. Whether you are doing the mapping on an extension or in the tag's template itself, you can use the next: if(a == 'view') { // Mapping happens here } I just deployed a Snap pixel, and the easiest is making a direct mapping to event within the tag mapping options: Where you set b.snap_event on an extension using the lines I suggested. Hope it helps! ... View more

Hi @jseuren, From my experience, utag.sync.js works exactly the same than other tags. Once it's saved on a profile level and published to the environments, there's no way to get it back. Just as the other templates work. If it's saved on a version level, the old versions can be retrieved by browsing to other versions on your Tealium iQ profile. If you understand as 'versioning' the dates on top of the JavaScript file, then utag.sync is never versioned since it's an empty file by default, and it's up to the user to make different versions. Hope it clarifies things! Pablo ... View more

Hi @jseuren, Once a tag template is saved on a profile scope and published on all the profile branches, there's no way to roll it back other than having made a manual copy on a text file yourself. Usually it's just better to save changes on a version level.   If you have published it on Dev, but QA and Prod remain the same, then you'll be able to manually take the tag template by browsing to the other environments. Cheers, Pablo ... View more

Hi @pascalreder, Most likely you have a tracking call you are not able to locate. The tracking calls seem to be different between, so there might be two extensions populating them. I discard the external links as an option since both pev2 parameters are lnk_o. I'd do the next: Re-write utag.link on the Javascript console. Something like: utag.link = function(arg){ console.trace(arg) } There you'll see how many times utag.link is called, and from where: Just click on the second line of the trace, and you'll be able to locate it in your utag.js file, and it should be easy to map that with an extension/tag. Usually this is due to an event listener placed two times on the same page (something that executes when the page is loaded, and other time). For preventing this from happening you can use the Run once after all tags scope, or set a parameter (utag.runonce). The second might be somewhere on Tealium documentation. The last option I can think of is that you saw only one utag.link call happening. Then your issue is with Adobe Analytics, probably somewhere on the template/configuration parameters. That really depends on the implementation you have. Hope it helps! Pablo ... View more

Hi @abkarim, What you are doing there is firing a Google Analytics (GA) tag only when a visitor clicks on that class. By default a Google Analytics tag will throw a page view. What I think you want to do is tracking those clicks as an event in GA. In order to do that you need to do a couple of things: If you want to send an event to GA, you'd need GA to be on the page before the visitor clicks on that element. For doing this, adjust your load rules, so the tag is present in all the pages (or on the pages you want it to be). GA events are defined by a category, action, label and value. Talking by memory only the first two are compulsory. Therefore, you'd need to map something to those attribute. My advice is you to create a couple of data elements called event_category and event_action (on the data layer tab, or by pressing the '+' symbol next to tealium_event on your screenshot). Then you set a value (event_category to the wider description of the event contact, event_label to something more specific footer). Avoid using tealium_event for this, as it's meant to be a default data layer key that helps distinguishing between views and links. Hope it helps! Pablo ... View more

Hi! Tealium released already a solution for the Global Tag Snippet, so the ones you mentioned are to be deprecated, I can imagine. There's an individual tag available for Google Analytics, AdWords and DoubleClick. You can find those in the tag marketplace. Hope it helps! ... View more

Then the only options I can think of is either the tags are scoped to all the pages, or they have the Bundle in utag.js option enabled (Tag > Advanced Settings > Bundle Flag > Yes). Whenever a tag is included on the utag.js, @marksawers, Tealium Web Companion does not show it (which is something a bit annoying sometimes). ... View more

Hi @marksawers, May it be that some of the tags are scoped under an All Tags load rule? In that case the tags are bundled by default on the utag.js file. I see your note on that, but still it's the only scenario I can think of. Also, what do you see if you filter by utag. in the network tab of your browser? Do you see all the 20 tags loaded in different utag.N.js files (where N is the UIDs), and all the techonologies are loaded on the page (maybe you can check this out by using Ghostery)?  Please let me know how that works!  Pablo ... View more

Hi @JonSpartan1, There's also the posibility of doing it based purely on the URL: If you track several domains within the same Tealium profile, please consider @BenStephenson response, or basing the rule on the page name if it's common between the sites. ... View more

Hi, I'd approach this in a slightly different way, if I didn't misunderstood your challenge: Lookup table for country specific properties. Something like @UnknownJ showed up: For adding the global property, you can just create an extension under this one where you append the global property to it: b.ga_account += ',UA-121212-1'; //Global property Then you just map ga_account to the tag.  My suggestion is keeping the same configuration between countries and global, so it's easier to mantain. If the case is you have free accounts in the countries and the global account has a premium license, maybe you can prioritize the first 20 dimensions. Maybe another options is doing a rollup or having a global account with views per market. Cheers, Pablo ... View more

Hey @LongPun, You can use a Set Data Values (or a JavaScript) extension where you substract order_tax from order_total whenever both are defined, and scope it to All Tags.  Something like this should work: if(b.order_total && b.order_tax) { b.order_subtotal = parseFloat(b.order_total) - parseFloat(b.order_tax); b.order_subtotal = b.order_subtotal.toFixed(2).toString(); } Just double check the format is correct (dot or comma). ... View more

Hi there @weshancock1981, > utag.js:45 trigger:called before tags loaded This log message means you are triggering the utag.view call before the tags are ready to listen those calls. There's a flag into utag object that allows you to know when the tags are ready to fire page view tracking. That flag is under utag.handler.iflag and turns from 0 to 1. I couldn't find any documentation on it, unfortunately. What you can try is encapsulating your utag.view() calls inside a setInterval, which checks for utag, utag.handler and utag.handler.iflag to be defined, and the last one to be one. Something like the next: var firePageView = setInterval(function() { if (window.utag && utag.handler && utag.handler.iflag == 1) { utag.view({ data: 'my data' }) clearInterval(firePageView); } }, 200); Haven't checked your site, anyway hope this helps! Cheers, Pablo ... View more