Tealium Learning Center

Hi @Anonymous I did something similar a while ago. I added click handler extensions for the "continue" button in each section which updated the data layer with the step name (in page_name) and other interesting information from each step, and then called utag.view() with the updated data layer. I think I also then click handlers on the closed section headings because you could click back into a previous section to change it. utag.view will load all the tags as if it is a new page view, using the passed data layer, so if you set up the object correctly then GA will pick up the product information and fire correctly (along with any other appropriate tags) ... View more

Hi @yan_almeida Additionally to what @UnknownJ says: utag_data is (usually) declared on the page, and (usually) contains stuff set by the developers from the server utag.data is the processed data layer.  This contains everything from utag_data... plus any DOM stuff (properties prefixed with "dom." such as utag.data["dom.url"]) plus any cookie values (properties prefixed with "cp.") plus any page JS variables you may have declared plus any querystring parameters (properties prefixed with "qp.") Also utag.data will have had any extension manipulation code applied ... View more

Hi @zed_haque If I have a lot of handlers to add then I group them in to functional groups and use a javascript extension rather than the templated handler extensions. Example: I have a site where the SPA fires window events on interesting changes, so we've configured Tealium with about 10 extensions that contain related handlers, which then deal with the events. For example: Ext: Navigation Handlers $(window).on("logo_click", (event,data) => { ... utag.link(data); } ); $(window).on("nav_button_click", (event,data) => { ... utag.link(data); } ); Ext: Search Handlers $(window).on("perform_search", (event,data) => { ... utag.link(data); } ); $(window).on("search_result_click", (event,data) => { ... utag.link(data); } );   Ext: Registration Journey Handlers $(window).on("registration_start", (event,data) => { ... utag.link(data); } ); $(window).on("registration_step_change", (event,data) => { ... utag.link(data); } ); $(window).on("registration_complete", (event,data) => { ... utag.link(data); } );   And so on...   This means we've got about thirty handlers into about ten extensions. Is that similar to what you are trying to do? ... View more

Hi @timmychap I've used this template before, and after a lot of faffing about and going through the entire JS template, i eventually worked out that only certain parts of the sdes object are populated, and it all depends on (from memory) the "type" that you set against the tag. The type can be a comma separated list of strings, so I ended up putting lots of them in each tag to make sure that all the bits that I needed were populated. You don't need to use the ecommerce extension data objects, but if you don't you will need to set up the mappings yourself (which isn't a big job). I'll see if I can find the set up I did (can't actually remember which client it was for) and get some examples for you. ... View more

Hi @brandon_flynn This easiest way to do this is probably: - add an event handler extension.  - Set the selector to .mybtn and the trigger to click.  - Assign a JS Code to the data object you have that is mapped to evar2, and use jQuery to read the text out of the button.  Something like $(this).text() should read the inner text from the element that was clicked (if you don't have jquery on the site you can do it using "normal" javascript) It will look a bit like this:   Hope that helps ... View more

I think this was a glitch.  Tried again this morning and it all works fine. ... View more

Hi @pascalreder In Adobe you don't need to send data to virtual report suites.  You send it to the Global report suite and the virtual is configured using a segment. So as long as the data you send in has the right variables set to make it fall into the segment/VRS, then the hit will be counted in both. If you want to pass data to two "normal" report suites, you can write a Set Data extension (or a Lookup Table) to create a comma separated list of RS values, and map that to the s_account object. Hope that helps Ben ... View more

Hi @Anonymous You could add an extension scoped to the GA tag that blanks out the ecommerce variables if the page is not the order conf page. I've done that a couple of times for different purposes (on the Adobe tag rather than GA though). Generally something like: if(b.pageName !== 'order-confirmation') { b.orderId = ""; b.revenue = ""; } Obviously replace the data layer objects with your data layer object names.  This then stops the ecommerce extension populating the __cc... objects, and stops the automatic mapping of the purchase events.  You can scope this to any tag that does automatic ecommerce tracking. ... View more