Tealium Learning Center

Thank you for your comprehensive suggestion. I also take that as an answer that Tealium currently doesn't provide a feature out of the box to support this :) We will be using Onetrust as our CMP provider. I know from a previous talk with our CSM that Tealium is partnering with a different CMP provider. So we will see if the upcoming Consent Integrations feature will help us to simplify our solution. For now we will build something like suggested. Thanks again for your respones. Best regards, Andreas ... 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

I am also facing a similar kind of issue when I place this code in the Tealium with scope DOM ready function is called multiple times. window.tealium_sourcepoint = function(e) { if (e.origin.toLowerCase() === 'https://notice.sp-prod.net') { e.stopPropagation(); e.bubbles = false; console.log(e.data)}} window.addEventListener('message', tealium_sourcepoint, false); ... 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

It makes total sense :)   Thanks a lot @calebjaquith  ... View more

@calebjaquith  thanks for clearing up. That behavior seems a bit counter-intuitive, but I am glad it works that way. Thank you both very much. ... 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 @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

Thanks for the link @calebjaquith. @siddharth_singh link what Caleb has provided is a easy option.  Just wanted to add a note here, its always good to have the tag deactivated or deleted once its span is done. Its bwill be safe as well as its good for performance as well. ... View more