Tealium Learning Center

Hi @ahrasch - we're finishing up our 'Consent Integrations', which we're expecting to EA in Q4 - what CMP are you using? Feel free to DM me! ... View more

Hi @matthew_grinspa, if I've understood correctly, the behavior you're looking for is, in fact, our default behavior.  To my knowledge, that jQuery fadeOut code you pasted isn't part of our out-of-the-box solution, so if you can find where that code was added as a customization (likely one of the CM templates or a JS extension), it should be pretty straightfoward to simply remove it. Does that help? Best Caleb   ... View more

Hi @gsreevastava , true, deleting the attribute from the TiQ/UDH UI doesn't actually remove it from the event payload. Are you trying to remove the cookie (1) from the UDH completely, or (2) just from the Azure Event Hub payload specifically while leaving it available for other purposes in the UDH? SInce you deleted the attribute in the UDH as an attempt to fix, I'm guessing (1).  In that case, assuming you're using TiQ, I'd probably make the exclusion in TiQ, with an extension scoped to the Collect tag to either remove the cookie information from the b object with JS or set it to either an empty string or something like "(removed)" using the Set Data Values extension to make it clear that you've removed it. For (2), you could change your Azure Event Hub Connector to use the "Send Customized Data to Event Hub (Advanced)" action and then select the attributes you want to send to Azure one-by-one. But that would mean you'd need to update that configuration as variable that you want in Azure are added - I'm not sure if that makes sense in your case. Hope that helps? Best, Caleb   ... View more

Hi @simlev , in case you're still wondering about this, here's the FB documentation about their Advanced Matching functionality, if you check the 'Description' column in the 'Customer Information Data Parameters' section, you can see that nearly every field is supposed to be sent lowercased (sometimes with spaces and puncutation removed as well).  That's because JOHN, John, jOhN, and john (etc.) will all produce different hashes because of the differences in capitalization - it makes much more sense for FB just to store the hash of 'john' instead of every possible variant's hash. Does that help? Best Caleb ... View more

Hi, in TiQ, I'll use dot notation when I can (so I'd write your example  b.var_name ).  But many automatically generated names in TiQ include a dot, which forces you to use bracket notation:  b["cp.cookie_name"] . That's more a technical consideration than a "best practice" I guess.  But I do agree that dot notation is easier to read, and doesn't risk dumb errors like omitting your quotes and accidentally referencing a variable instead of using a string literal. Hope that's useful? Best Caleb ... View more

As @BenStephenson said, the general use case is TiQ receiving tracking events from the page (and/or automatically triggering pageview events on load).  Those incoming "events" are then compared to Load Rules for Tags, which are fired if appropriate.   The functionality implied by your snippet would be covered in the corresponding Tag Template and/or tag-scoped Extensions (to manipulate the data more manually, if needed).  Tags 'subscribe' to events based on their Load Rules inside TiQ. I've never tried, but I don't see why I wouldn't be possible to set something custom up in TiQ to trigger window-level events for other code to listen for, if there were a compelling use case to keep tag-like code outside of TiQ. But that's not available out-of-the-box, and I'd expect using a Tag to be the better option in nearly every case (for all the reasons it's useful to have all Tags in a single TMS, etc.). Hope that helps? ... View more

Sorry for the confusion, you're right that my initial suggestion doesn't work.   The problem is that the callback to the Generic Tag doesn't include the response as an argument. I've just set up a successful test: Use a Custom Container tag to make your API request using xhr (allows you to use the response in your utag.link call).  We could use a JS extension instead, but IMO it's much cleaner to use Tags for all outgoing requests for the sake of possible Consent Management, etc. Just put this code (modify the requested resource and the utag.link as needed) between the 'Start Tag Sending Code' and 'End Tag Sending Code' comments: /* Start Tag Sending Code */ // could add mapping to make this more generalized, hardcoding for now as POC var xhr = new XMLHttpRequest(); var apiResource = 'https://putsreq.com/JTBXYfs30pQvioNwgV2Y' xhr.open('GET', apiResource); xhr.onload = function() {   if (xhr.status === 200) {     var data = {};     data.event_name = "data_callback";     data.foo = xhr.responseText;     utag.link(data);   }   else {     utag.DB('XHR API Request failed. Returned status of ' + xhr.status);   } }; xhr.send(); /* End Tag Sending Code */ No other changes are needed to that template. Assign a Load Rule to that Custom Container so it only fires when the session cookie isn't yet defined Set up a Persist Data Value Extension to persist 'foo' from your 'data_callback' event Sorry for all the back-and-forth on this one, let me know if that works for you. Best Caleb ... View more

Here's how I would configure the Persist Data Values extension here: I created 3 variables: event_name (UDO) foo (UDO) utag_main_foo (First Party Cookie) So if the 'event_name' is 'data_callback' on an incoming event (either utag.view or utag.link as I've configured it here, you could limit it further to only respond to links), the value of 'foo' will be persisted for the Session duration in a subcookie called 'foo' within the 'utag_main' cookie.  That 'utag_main_foo' cookie could be used in the Load Rule for your Generic Tag, to only get that value if you haven't already gotten it within the same session.   ... View more

Here's some documentation on utag.link() - it's basically just a way to send a non-pageview event through TiQ's logic. It's just an event, and as such doesn't set a cookie.  But it allows you to set up the Persist Data Values extension to set a cookie on qualifying events using the 'Conditions' at the bottom of that extension.  Does that make sense? ... View more

Hi @okbrown , if you want to persist the data from pageview to pageview, adding it to the UDO won't be enough.  utag_data and utag.data are just window-scoped JS objects, so they only last the life of the page. b is even more short-lived. You need to set a cookie (or use local/sessionStorage). The easiest way to do that in TiQ will be to set a cookie using the Persist Data Value Extension. So you might: Use a Generic Tag to make your HTTP request Use a tag-scoped JS Extension to set a callback for your Generic Tag, something like u.callback = function (response) { if (typeof response !== "string") response = "bar";   utag.link({     "event_name" : "data_callback",     "foo" : response   }); } That callback will fire a utag.link event with the data from the response (obviously just illustration code).  Set up a Persist Data Value Extension to persist the value of foo to a cookie like utag_main_foo (you'll need to add both those through the Data Layer tab).  You can set that up with a condition so that it's only set on 'data_callback' events.  I'd suggest using a utag_main subcookie to make sure that the session recognition is consistent (some browsers handle that strangely, better to let TiQ's session logic handle it). Depending on your use case, you may also want to set a Load Rule on your Generic Tag so that it only fires when that cookie ( cp.utag_main_foo ) isn't already set to make sure it only fires once per session. That's off the top of my head and I haven't tested it through specifically, but those are the building blocks I'd suggest using. Hope that helps? Best Caleb         ... View more

Hi @shailesh_gaikwa  glad to hear it's working! Since you're using AND, the rule will only evaluate to TRUE if all of the component conditions evaluate to TRUE.  Here are three cases to illustrate what's happening when TiQ evaluates the Load Rule: CASE: EventType value is "EventType4" Condition Result EventType is populated TRUE EventType does not contain EventValue1 TRUE EventType does not contain EventValue2 TRUE EventType does not contain EventValue3 TRUE > Evaluates to TRUE, tag will fire.  CASE: EventType value is "EventType2" Condition Result EventType is populated TRUE EventType does not contain EventValue1 TRUE EventType does not contain EventValue2 FALSE EventType does not contain EventValue3 TRUE > Evaluates to FALSE, tag will not fire.  CASE: EventType value is "" Condition Result EventType is populated FALSE EventType does not contain EventValue1 TRUE EventType does not contain EventValue2 TRUE EventType does not contain EventValue3 TRUE > Evaluates to FALSE, tag will not fire.  Does that help? Best Caleb ... View more

@Frish - to add to @ruipedromachado's post, there's another important consideration when looking to move tags from the client-side to the server-side - cookies.   Often, simple web-based trackers like the ones in Rui's post rely on 3rd party cookies to transmit meaningful data to the vendor in question, and/or set user-level identification cookies in the request response (with a Set-Cookie header).  Without that user-level information, those outgoing requests wouldn't be useful (because the vendor wouldn't know which user has viewed that page, or which click to associate with the conversion, etc).   That's why Tealium offers a number of Cookie Sync tags and related functionalities.  Those vendor-specific tags retrieve/create such cookies and allow the values to be persisted on Tealium's side so they can be sent to the vendor manually from our servers.  This example for Criteo and this one for TheTradeDesk have a bit more detail about the approach in AudienceStream (where you can persist that data on the Visitor Profile), and we've documented it more generally for EventStream as well (where we use our own third-party cookie to persist that data, since EventStream is event- (not profile-) driven. Long story short, it's not quite as simple as just moving the tag, you also need to find out what additional information is generally delivered via 3rd party cookie to that vendor in their web-based solutuion, and find out if the vendors offers a way to retrieve it so that it can be persisted in Tealium and sent to the vendor accordingly. Hope that helps? Best, Caleb ... View more

Related Product Idea: https://community.tealiumiq.com/t5/Product-Ideas/Maintain-extension-order-of-operations-in-child-profiles/idi-p/25902 ... View more

Hi @GavinAttard, the order in the child profile is the one that's followed.  If they're inherited in the wrong order, they will fire in that (wrong) order. I generally name my grouped extensions with a prefix that helps with grouping and order: That same convention might make this issue less painful for you and your team.  I'd encourage you to add a Product Idea for a TiQ enhancement that ensures extension order is preserved on inheritance from a library, you'd have my vote. Best Caleb ... View more

Hi @sujay_das, I usually use DOM Ready, because it's important that the HTML element you're adding the listener to is already present (and DOM Ready ensures that, assuming a standard HTML page). The other 'Run Once' options that @BenStephenson mentioned will probably work just as well, since it's very unlikely that setting would result in trying to add the listener before the element is present.  I'd expect either approach to work fine in most cases. ... View more

Hi @ErikDekker, excellent - glad it's working! In case it's interesting for you: It makes sense that it wouldn't show in the source code, since we're injecting it via JS after the source has loaded.  But you should be able to see it in the 'Elements' tab of Developer Tools, since that view contains the info from the source as well as any dynamic changes that happen after page load.  Any DOM changes in TiQ can be checked like that. Best Caleb ... View more

Hi @ErikDekker, if you put the snippet above into a JS extension with Pre Loader scope, a meta tag should be added the head, and that meta tag should also be picked up and added to the utag.data object on the page (works in my tests). What are you seeing instead?   ... View more

 Hi @siddharth_singh, TiQ supports Time-Based Load Rules to help with this as well: https://community.tealiumiq.com/t5/iQ-Tag-Management/Load-Rules/ta-p/5098#toc-hId-821619860 Hope that helps! Best Caleb ... View more