Tealium Learning Center

@anourani111  In production, Im not sure there is anything you can reasonably do to bypass this. This is part of the "design" with the client-side batching which is generally "best" for the user. If they navigate away the events should still fire.   For development / testing, you may be able to use the dev chrome extension which used to bypass the wait. https://chrome.google.com/webstore/detail/google-analytics-debugger/jnkmfdileelhofjcijamephohjechhna  ... View more

Very helpful and what I exactly wanted. Thank you LordLingham ... View more

Sorry to hear you are having issues here. It sounds like the event listener is being added multiple times, which would probably be the result of this extension firing on each view/link event being sent. Can you confirm this is running at the "DOM Ready" Scope, or has "run once" selected if it is "Before / After Load Rules"? If its BLR / ALR without the "run once" option, each view would be adding the listener again - which would mean firing another event. Page load - 1 listener Click - 1 event fired + 1 listener added 2nd click - 2 events fires, +2 listeners added Etc. etc. ... View more

Hello @LuLong Sorry to hear you are still having some trouble here. I've checked the template for GA4, and it looks like the event "view_item_list" should generate and send an item for each element in your arrays (12) Without seeing your specific setup I can't say anything for certain, but a few things you should check 1) You are firing at "view_item_list" event with your mapping, and not a "view_item" - "view_item" is specifically told to only send the first item in your array. Based of your description, it sounds like this is the most likely issue here 2) Ensure mappings are correct for the items. You want to be mapping to both "product_id" and "product_name" within the mapping toolbox. You mention the ecommerce extension - If you are using this, the template would use the values created as "_cprod" and "_cprodname" - worth making sure these are populated correctly 3) Failing this, you can try a bit of debugging - Loading the "utag.x.js" file in your browser developer tools - where X is the UID of the tag (e.g. utag.123.js) will allow you to place breakpoints on the code - You can find a function called "getItems" which is the part generating the list of items to be sent, with some breakpoints here you might be able to get an idea of whats going on. If the steps here don't work, or you are still not sure what to be doing, drop me a message here, or reach out to your support team where a CSE will be happy to look in to your specific setup. ... View more

Ignore my previous post, didn't read properly. ... View more

Hi, thank you for your reply. Indeed we are migrating from v1 to v2 as stated on the message. As such, we are confident the Tealium mobile config is correct since we've been working with it for a while now. The issue is specifically related to the new initialization config. We've managed to get it working by using all the Dispatchers and Collectors. They question came up because if we don't use all of them, then no data is being sent. We are still curious on the relationship between the several Dispatchers and Collectors and Tealium being able to send any data. In other words, the question, or request, is to elaborate in your docs what is each Dispatcher/Collector doing and to make it clear when is each of them required. We also weren't able to see any logging, we are wondering if the logLevel config is represented in the local level, via logs in react native debugger for example, or is it something we would only see on the server side? The documentation does not explicitly mention this. Regards,   ... View more

The best way to prevent a tag from firing would be to adjust the loadrules to only be met for specific events. Typically you would only have a "view" event fire once per page, there are some exceptions - but it may be worth confirming if you want to be using "utag.view" instead of "utag.link" If the event data being sent for both of your view events is identical - and there isn't and easy way to be able to identify whether this is the second event on the page or not - You could look to add some functionality in one of a few places   Tag Template - Some of our tags already have this functionality built in - lots of them will make use of a "u.initialised" flag which you can use. This would involve modifying the template though, which many people prefer to avoid.   Extension / Loadrule update Add this code to a javascript extension which is scoped to the tag. utag.data.has_xxx_fired = true; Then add this code to a JavaScript Extension scoped to "Before Load Rules" b.has_xxx_fired = utag.data.has_xxx_fired || false; Then add this condition to a loadrule has_xxx_fired is not equal to true You can change out the variable name "has_xxx_fired" with anything you like! When the tag fires for the first time, we set has_xxx_fired in utag.data, which we then read on subsequent events, and we dont let the tag fire a second time. Those options are a bit more work - And it would be easier if you already have something in your event to play from though.  ... View more

Hi @LordLingham I'm also interested into knowing more! Thanks! ... View more

Hello @asdhjjjjjjjjj  Sorry to hear you are having some issues still. If the mobile publish settings are correct, there could be something else blocking things from firing, This may be due to things like the network connection, the old mobile.html file being cached, or something like "consent manager" is set up within the app.   Have a quick check of those things and if you still do not find the fix, reach out to the support team who will be happy to look in to this further / at your specific setup.   Thanks James ... View more

Thank you for your fast reply. I didnt know that there are extension scopes that still run with the "noview" config,  but that sounds like a good solution :) Greetings ... View more

You could add a condition to the preloader javascript extension that doesn't trigger on non SPA pages. But even if the page is a non SPA, by using the "window.utag_cfg_ovrd = {noview : true};" configuration, that disables all auto pageviews, meaning you could also manually trigger a utag.view() call on a non SPA part of the site. ... View more

Hello, I am having the same issue here the Facebook Pixel is triggering a random "SubscribedButtonClick" event when I make click on the CHECKOUT button. My guess is that this is in somehow preventing the iniciateCheckout event to initiate correctly on the CHECKOUT button click. It would be nice if we can turn off these auto events. Thanks ... View more

Thank you! It makes sense. ... View more

Ah ok thank you @LordLingham . I was not aware of the tool "Environent Switcher". That helped indeed. ... View more

Hi LordLingham, Thanks for your help! I'll update the extension in Tealium and let you know if it works. Update: It worked, thanks! Max ... View more

Thank you very much for your response @jumbreit. Kind regards, Marta ... View more

Hello @LordLingham ,   Thank you for your reply. It is GA which is triggering the additional sessions. I think, i will open a ticket by support. Thank you. Best Regards, Alexandra   ... View more

Not completely happy with this. 1. Can I be sure that this function name is never changed in the Tealium utag.js, which would break my extensions depending on this? 2. This has a side effect on all other extensions. 3. It would be better if Tealium could just be configured to do this by default. ... View more

Thx @LordLingham    Been contact Support, and they have upgrade our consent manager to v2.0 and this have resolve the issues. ... View more

Hello @tealium23 ! Judging by your description, there is a syntax error in the custom template which is causing an issue with your other tags from running. Have a look at the template and correct any syntax errors you can find - if you are unable to find anything, you can reach out to support (or drop me a message) who will be happy to help out! ... View more

Hi Darsha, This is a good question on how libraries work. From your description, it is likely the lookup extension is inheariting from the parent profile called: lib-global (under your account) therefore this is greyed out and it would need to be edited from the opended lib-global profile instead. To edit the lookup extension in TIQ, you will need to: - Open the lib-global parent profile as show in the green below from the top left menu (it should be found under your account as well): - Edit this lookup extension in the: lib-global parent profile - Publish your change to DEV/QA/PROD to the lib-global parent profile. - Re-open the child profile inheariting this lookup extension from lib-global. Should you see an orange star (marked as changed but unsaved) next to all elements inheariting from lib-global there (tags, extensions...) To update the changes just made from the lib-global library to the actual the child profile, please publish the child profile into the environment to test it, example: DEV/QA. It should resolve your question. Hope this helps ... View more

@akshaykashyap2    I don't have the tag in front of me so I can't say for certain, but I'm 99% sure that this is correct.   Map an array to the mappings defined in the tag UI and it should create the enhanced event for each id code in the array.   Map a string, and it get one event for each character in the string (obviously not what you want)   Update the extension to set the value to be an array, and everything should be golden! ... View more