Tealium Learning Center

I created a generic plugin to handle just this. It should be useful when used in conjunction with utag.link calls and google's custom events, but you may need to modify slightly based on your needs. You can either put it directly on your page, or in a domReady scoped javascript extension. Here's a link: http://www.inteliquant.com/scroll-tracking-plugin/   If you are looking for more of how much a user viewed on the page, you can use the percent page viewed plugin. That is searchable in the community, or found here: http://www.inteliquant.com/percent-page-viewed-extension/ ... View more

@samrat_dsouza, It may be possible to do, but it sounds like there will be a significant amount of workarounds since it appears you'll be adding various loading rules into the mix. I would suggest to submit this as a support ticket if possible to see if there is an alternative solution that may meet your needs better. One possible solution may be by combining tags and handling logic directly in a custom container, rather than multiple tags and extensions. ... View more

It's usually better to default everything to a string value (e.g. "1") since most of our templates expect strings. Javascript is also loose enough where you can increment and convert back to a string in one swoop:   b['metrics1'] = (++b['metrics1']) + ""; //increment by 1 ... View more

Yup! You can do this pretty easily using a set data values extension. You would just set user_id to the existing _ptmz variable. Your condition might also say "_ptmz is defined" for the extension rule. ... View more

Hello @ani2012. To make sure I'm understanding correctly:   1) You have user_id mapped into GUA's UID variable 2) You want to also have the value from the cookie "_ptmz" mapped into the UID variable.   If that's correct, then you shouldn't need to alter the user_id at all. The beauty about mappings is that you can map multiple variables to a tag and it will accept the last one populated with a value. So, assuming user_id is a udo variable and _ptmz is a cooke variable (and both created in the data layer tab) then you could do a mapping like so in the GUA tag:     Then, if one or the other variable is populated, then the uid will get populated. If both variables are populated, then the _ptmz would take priority since it is lower on the list. ... View more

You are correct on the mappings, only one value is accepted. However, Adobe calls only accept one value per eVar/prop on a given network call, so you'll need to do one of two things to get around it:   1) Fire a separate utag.link/view event with the second item of data. So you might have the first call look something like so: utag.link({ cart_typemini="mini" }) Then a second one that you call like so: utag.link({ cart_typestd="std" })   2) Change the variable to be from eVar75 to a list variable. Then, instead of sending 1 value, you can send a list. Example:   list1 -> mini,std   However, since it appears you are reporting 2 different metrics here, it may be prudent to re-evaluate your actual business requirementsto see if it's possible to put these values into separate eVars. ... View more

Hi @srinii86!   I've done a lot of implementations with both Tealium and Adobe DTM with Adobe Analytics. There's several pros and cons to each, so I'll try to point out each as best as I can while being unbiased.   Tealium Pros Much more intuitive interface. Clear separation between tags, extensions/customizations, and data elements. Integrated data layer. Clear use of event tracking methods and data tied to each individual event. Fully asynchronous by default. Hundreds of pre-built tags available. Excellent support team and resources. Much more user friendly for tag implementation. More robust versioning and permissions.   Cons Versioning a little less intuitive. Costs extra money. Event tracking through the tool relies on jQuery or javascript knowledge.   DTM Pros Integrated with Adobe Analytics more closely. This makes variable mappings a little more logical to work with, in Adobe terms, from start to finish. Free if you already have Adobe Analytics. Slightly easier versioning system up front. Event tracking is built in and much easier to use than jQuery.   Cons Very limited integrated tags. It is literally only integrated with Google Anaytics and other Adobe products. Implementing tags means implementing javascript. Requires synchronous implementation in both the head and footer of each page. No clear separation between data elements, tags, and "extensions". No native data layer integration. Manual javascript tag tracking events (e.g. link tracking) allowed, but data isn't tied directly to the event. Limited support and sometimes hard-to-find resources.     Back to your original question about implementing Adobe Analytics -- every client I've seen chooses Tealium hands down unless money is a large factor. The reasons usually come to management of the tag (which Tealium excels in) and intuitiveness of accessing the data. Tealium's philosophy is built around a strong vendor-neutral data layer, so you are looking at real, readable variables (e.g. customer_id) instead of something impossible to decipher on its own (e.g. eVar45). Tealium allows these to be very user-friendly and easy to map, whereas you have to keep going back and forth for DTM unless you remember to specifically name each individual data element. Both tools will get the job done in a similar manner for basic setup as well, but Tealium's extensions are much more intuitive than implementing customizations within DTM (sometimes very confusing or difficult).   The largest question I always keep in mind is "what is my end goal for the tool?" If my sole purpose for a tag manager is to implement Adobe Analytics, then DTM is going to be better suited because it is free and already very integrated. However, if I'm going to implement any other tags aside from Adobe Analytics and possibly have multiple users using the system of different skill levels, then Tealium is hands down the preferred tool. ... View more

For future users looking at this question, here is an option that will work on a tag-by-tag basis. 1) The following code needs to be placed in a javascript extension 2) any tag(s) that you would like to trigger at onload instead of dom ready should be scoped to this extension function addLoadEvent(func) { var oldonload = window.onload; if (typeof window.onload != 'function') { window.onload = func; } else { window.onload = function() { if (oldonload) { oldonload(); } func(); }; } } utag.onload_flag = utag.onload_flag||{}; if(!utag.onload_flag[id]) { if(document.readyState!="complete") { addLoadEvent(function() { utag.view(utag_data,null,[id]); }); return false; } utag.onload_flag[id] = 1; }     ... View more

Yup! Since this is very custom tracking, you would have something similar to above to house your different event needs, then loop through what is being set on your page and match things up. The last step will be to fire the actual events as needed either with u.addEvent for SiteCatalyst, mappings for Google Analytics, and usually mappings for other tags as needed. ... View more

This is why I like the object approach in a javascript when there is a massive amount of events. It's easier to setup and it will run much faster since it's a hash lookup instead of a full loop. When you do 100+ extensions, every single one is going to run regardless. It will be more readable, but from a performance standpoint, doing an object (hash) lookup will be fastest. ... View more

I would also recommend this for ease of use unless you have a large amount of events (like 20+) that need to be checked. ... View more

Hi Jarno,   If you are checking one event, then you can use the indexOf syntax. Something like so:   if(b['pageEvents'].indexOf('XXX') > -1) { u.addEvent('YYY'); }   If you want to check multiple events at a time, you'll probably want to do a loop and go through all the different events. Maybe something like so:   var pageEvents = "eventA,eventB".split(","); for(key in pageEvents){ if(pageEvents[key] == "eventA") u.addEvent("XXX"); else if (pageEvents[key] == "eventB") u.addEvent("YYY"); }   I personally like to use the object syntax though it is more complicated:   var events = { eventA: "XXX", eventB: "YYY" }; var pageEvents = "eventA,eventB".split(","); for(key in pageEvents){ if(events[key]) u.addEvent(events[key]); } ... View more