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

Hello @anourani111 This used to be a timeout put in place within the GA4 library on Google's side - I believe its their way and waiting to see if there are multiple events that they can batch and send together. This is supported by their documentation here  I believe there used to be a way to have this send immediately involving some debug flag, but you probably dont want to enable this in production. ... View more

Hello @anourani111  You can find our documentation for the generic tag here   The only thing we care about the tag you have is the src attribute, and the fact it is as image (vs an iframe or a script) When setting up the tag, make sure the "type" is set to "image", this is the default, but best to double check. Moving on to the source / URL https://insight.adsrvr.org/track/pxl/?adv=trl7bi1&ct=0:l5a0wfx&fmt=3 This can be split in to a few parts  - The base URL - https://insight.adsrvr.org/track/pxl/ - The Query Parameters - ?adv=trl7bi1&ct=0:l5a0wfx&fmt=3 The Base URL can either be set by using the UI config and entering the static value ( probably what you want here), or you can use a mapping to set this, by using "base_url" as the mapping destination Querystring parameters are slightly different here, breaking down the ones you have, looks a bit like this. adv=trl7bi1 ct=0:l5a0wfx fmt=3 Our tag logic will add the ? and & characters in to the url by default, so you dont need to worry here. You just need to set up some mappings within the tag to specify these values. If these values will never change, you can simply add a custom mapping, where the destination matches the left hand side of your parameters above. I've added a screenshot of what the fmt=3 mapping would look like for reference. If the values are subject to change based on your datalayer, you can use variables from your datalayer instead of a custom value - the process remains the same   This should work for you, but feel free to reach out here / raise a ticket with support if you have any further questions or issues.     ... 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

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 @Joell  Were you using v1 previously - Was everything working fine there if so? If you were not, and this is the first time you are using this profile with mobile, it would be worth checking your mobile publish settings. https://community.tealiumiq.com/t5/iQ-Tag-Management/Creating-a-Mobile-Profile/ta-p/16328#publish_settings   Judging by the dispatchers specified, you are looking to send this data directly to EventStream - So you should make sure that "Tealium Collect" is enabled within the mobile publish settings. You could also look at getting a copy of the example app from out GitHub, and simply updating the app to use your own account/profile - The example app should have everything working, so you'll be able to use this to help narrow down the cause of the issue https://github.com/Tealium/tealium-react-native/tree/master/example If the mobile publish setting is already enabled, or you are still having trouble, it may be worth raising a ticket with the support team, where you can specify your account and profile - and someone will be able to look at this in more depth ... 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

Hello Björn This should work for the situation you have described. The line "// ADOBE TARGET SCRIPT" is referring the the placeholder ##UTSYNC## in your utag.sync template. This placeholder is replaced with the anti-flicker logic from the content modification extension, so if this is wrapped within that if statement, it wont run when the condition isn't met. If you are having some issues, I can always have a look at this with you if you raise a ticket :) ... View more

Hi Chris! You can certainly add the snippet of code at the preloader level, and you can certainly run this based off the DOM. variables, but do not. that utag hasn't really ran by this point, you would need to check for the domain / pathname yourself - you cant use utag.data ... View more

Hello @grafn  This issue should no longer happen when using the "Environment Switcher" The method of switching environment here is different to the older method of the "web companion" switching environments. We recommend using the "Environment switcher" tool which can be found in the same chrome extension as the web companion.   Hopefully this should hide this error from you when you switch environments now - if it doesn't, there is likely another issue that needs looking at. ... View more

@MartaSM1  Happy to hear that things are making sense!   Consent manager may be a little harder to have multiple instances for. "Out of the box" the consent manager will work on multiple domains, as it operates using a simple cookie. If you need to change the configuration. / the template, this would get a little more complex. I've covered the best way of working with something like this in another post - it will be easier if i link this here, but let me know if you have more questions. https://community.tealiumiq.com/t5/Tealium-iQ-Tag-Management/Styling-Explicit-Consent-Prompt-Manager-for-3-sites/m-p/31001/highlight/true#M9285     Regarding your other tags, the easiest way would probably be to use a "lookup table" extension, which can use an identifying property (probably domain) to see which site it should be using, and therefore which setting to be using. https://community.tealiumiq.com/t5/iQ-Tag-Management/Lookup-Table-Extension/ta-p/13708 For example, to change the "Tracking ID" in Google Analytics (gtag) Add the following mapping And then something like this in a lookup table to help decide whick tracking ID should be used. Note this is scoped to the tag which is using the mapping.   I hope this helps, as always, let me know if you have any further questions! kind regards ... View more

@AGoryunova Apologies for the delayed response.   Is Ga triggering the additional sessions, or is this sessions within IQ? If you are happy to message me a URL where i can see this happening, i'd behappy to do a little bit of debugging for you. Alternatively, if you raise a ticket with support, one of my colleagues or I will be more than happy to have a look!   Thanks James ... View more

@AGoryunova - Sorry it seems i misunderstood your comment.   Can you clarify what you mean by "ghost sessions" ? What ISN'T happening that you would expect to see? ... View more

Hello @AGoryunova  You are sending a "link" event which would typically not trigger "pageviews" - it would usually be used to monitor clicks, and the user interacting with the page in some way. If you would like "view" events, you should use "utag.view()" instead ... View more

Hello @AGoryunova    You can try making use of the "setInterval" function https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setInterval   This allows you to define a function / bit of code which should run every "x" seconds.   Something like this would work for you.   var GA_interval = window.setInterval(GA_event, 30000); function GA_event(){ var tags = [ 1 , 2, 3] var data = { "event_action" : "my event action", "event_label" : "my event label", "event_category" : "my event category" } utag.view(data, null, tags); } update the "data" object with the event you want to send to GA. update the "tags" array, with the UID(s) of the tag(s) you want to send the event directly too. ... View more

Hello @MartaSM1    If the webpages are similar enough, lots of people will reuse the profile on multiple domains, assuming the datalayers are fairly similar, and the tagging requirements are the same.   If needed, you could look to make the use of a library, which will allow you to inherit tags / extensions from a library, in to multiple profiles, allowing you to only set up the "similar" things once, but allowing a bit more flexibilty with including "profile specific" items, without having to worry about with creating complex loadrules. You can read more about libraries here. https://community.tealiumiq.com/t5/iQ-Tag-Management/Managing-Profile-Libraries/ta-p/13622 ... View more

Hi @Sam    Thanks for your feedback! I've recently been informed on a function which was included in a recent update to the consent manager which actually does this functionality for you (honoring consent on events like these). Are you running V2 of consent manager? If so - delete the "cmGeneral" template and then publish - to get the template to update to the latest version. If you are not - reach out to me in a private message, or raise a ticket with support and we can get your profile updated! ... View more

Hi @Sam ,   Adding a function in an extension like this might do the job for you,   utag.linkConsent = function(data, cb, tags){ if (utag.gdpr){ var consentState = utag.gdpr.getConsentState(); var csTYpe = utag.gdpr.typeOf(consentState); var sendTags = []; for (var i = 0; i<tags.length;i++){ var id = tags[i]; if (typeof utag.loader.cfg[id] !== "undefined" && ((csTYpe === "array" && consentState[tag.tcat - 1].ct == "1") || (csTYpe === "number" && consentState == 1)) || (utag.gdpr.omittedTags && !utag.gdpr.omittedTags[id])){ sendTags.push(id); } } } var sendTags = sendTags || tags; if (sendTags.length > 0){ utag.link( data, cb, sendTags); } } You would call this in a similar way to how you currently call the tags directly. utag.linkConsent({"hello" : "world"}, null, [9]) The issue with the consent is that whent consent is checked, it modifies the loadrules of the tags and sets them to "false" for any tags the consent is not met for - however calling tags directly like this ignores the consent. The function provided above replicates the consent check, but instead of adjusting the loadrule, it removes any unwanted tags from the array of UID's to be loaded. If consent manager is not active - it will load all of the tags.   The example given above was quickly put together - it's obviously only set up for a "link" event, but you could either replicate this for "view" or modify it for a generic "track" function - just a proof of concept for you to adjust as needed. It worked on my test profile quickly, but you may run in to a few issues if you test it a bit more vigorously. ... View more