Tealium Learning Center

@Ashish_Chainani  Thanks so much, excellent, thanks for share your wisdom. Thanks!!! ... View more

Hello All, I have a similar issue. For the product details page, once the page loads, the product data isn't available in the data layer and hence the developers have added a "utag.link" on page with updated data layer that has product related variables along with "tealium_event" with value "product details". How do we trigger additional GA call once the utag.link triggers on the page? ... View more

1) The gtag-based Google Tags all make calls to the googletagmanager domain. It is sort of an extra-GTM container just for these gtag-based google tags (Ads, Analytics, Floodlights). So don't worry about that. So you don't need to activate Google Tag Manager. 2) That's much more complicated to answer as it depends on the conditions (how to test whether it is working in a Safari with ITP enabled is something even the Google staff was incompetent at explaining. But in general, you should still see requests with the required floodlight parameters going out in your http debugging tool like before with the traditional floodlight tag. ... View more

An excellent, simple, solution! It works fine. Thanks! ... View more

@florian_perl   If you want to make it truly global you can use the window object. then you can just use the function name to call it.   Adrian ... View more

Thank you @STerjeson that makes perfect sense. ... View more

@jmbolfing, my client has a requirement for having a GTM container in place (not my idea) along with GA. The script I put in place is mainly to help monitor for ad click fraud more than anything, but it also helps point out how often GTM and GA fail to load, or dont load in time, along with people who have the tracker blocked. Yes, there is the potential for Tealium to be blocked as well. If you wanted to monitor for that, you would have to have the script directly on the page probably.  ... View more

I agree with everything that @STerjeson has said here. The best option would be to create a new variable and set it using a set data values extension (or multiple extensions), and have conditions to check which value you need to populate the variable with each time. If you do decide to override the "qp.oid" variable, be sure to use the "b" object, rather than utag.data. All tags and extensions should use "b", as utag.data will only be read when the utag script initializes; "b" will always contain the most up to date values inside an extension. There are some exceptions, such as "DOM ready" extensions, or "Pre-Loader", but all other extensions have access to "b". There is one other option that may work: you can map different values to the same mapping (e.g. "qp.oid" could be mapped to "prop1", and "click_oid" could also be mapped to "prop1" - just an example). In theory, the one that is lower in the mapping list would win, so if it was a page load, and the click variable didn't exist, the "qp.oid" variable would win, but if the event is a click, and the secondary variable is populated, this one would win. There is one caveat to this: technically, the mappings are stored in a plain JavaScript object, and when we loop through the object to assign the mappings, there is no guarantee of the order in which they will be evaluated. However, most browsers will now evaluate/loop through JavaScript objects in the order in which the properties were defined (there may be some exceptions), so in the vast majority of cases across the major browsers, you should find that mapping multiple values to the same mapping will work as expected, and the lowest one in the list in the UI would win. This means you could have as many different items mapped to the same item as you wish, and the one that appears lowest in the list will win. You may wish to test this. However, for the sake of the extra "clutter" in the UI from having lots of mappings to the same property, I would still choose the extension option that @STerjeson suggested. ... View more