Tealium Learning Center

Hi @darsha.  We've acheived this by using an extension to set a UDO variable (e.g. "page"), and then mapped that UDO variable to pageName in the tag.  I think you will have better luck using extensions to manipulate the variable, rather than trying to do that in the mapping section of the tag. ... View more

Hi @Jayakrishnaa - You might try setting utag_cfg_ovrd.noview to "true".  This will prevent the default page load call from happening.  Keep in mind, you will need to manually initiate utag.view( ) calls when utag_cfg_ovrd.noview is set to "true" window.utag_cfg_ovrd = window.utag_cfg_ovrd || {}; //Make sure we don't kill a previous decleration of the object window.utag_cfg_ovrd.noview = true;    ... View more

Just to close the loop on this, we ended up going with a custom JS extension and mapping it to the "SiteCatalyst AppMeasurement for JavaScript" tag, but we also manually set the s.prop and updated s.linkTrackVars within the extension. I guess the tag based variable mapping happens before extensions scoped to the "SiteCatalyst AppMeasurement for JavaScript" tag execute, so the mapping was happening before the variable was valued. I hate having to manually set an s.prop within an extension, but it works. Thanks for your help. ... View more

Thanks! ... View more

One additional question...  Is it possible to get a list of host names requesting the various profiles tags, @TealiumJustin?   Thanks! ... View more

Thanks Justin, this is exactly what I was looking for. ... View more

Nevermind.  I switched all utag.data.varName and utag_data.varName references in the js code to b.varName, and now it's working.  Thanks! ... View more

Hi @adrian_browning.  As a follow-up...  I am having great difficulty getting javascript variables to map to eVars and props in appMeasurment.  The current solution (running utag.js v4.44.xxx) has utag.view() calls initiated (as outlined in your email above), each time a "virtual page view" happens.  I've got all of the elements being passed in the utag.view() associated with corresponding UDO variables defined in the data layer.  Most of these are mapped directly to an eVar or prop in the appMeasurement tag and that works great.  However, I also need to manipulate some of the data coming in, and then place it in it's own UDO variable to then map to an eVar or prop in the appMeasurement tag.  I am currently doing this with a Javascript code extension.  No matter what I try, I can't get the value from the JS extension to map correctly in the appMeasurement tag.  It's always showing up as blank or "unknown_unknown".  I've tried changing the scope of the extension, I've tried using utag_data.varName, utag.data.varName, b.varName, etc in my js code.  I've also scoped the extension every way I can think of, but nothing seems to allow me to map anything accurately to the appMeasurement tag except for those values passed in on the utag.view() call when the page loads.  I've put this in debug mode, and everything appears to work correctly when the extension executes.  Am I approaching this wrong? I also tried using a "set data value" extension, but this only worked for me when I used text.  When I reference other UDO variables via JS code, they always seem to map to ""  or "unknown_unknow".  We have this working on non-SPA sites with no problem.  Any advice? ... View more

Thanks for the info @craig_rouse.  We created a copy of the old profile, and it appears that automatically upgraded the utag.js version to 4.44.xxxxx.  I am now able to access all of those variables.   ... View more

Thanks for the response @adrian_browning.  Sorry for the confusion, the code I pasted in was just pseudo-code.  The data being passed in the calls is structured in the way you have described.  Also, we are utilizing the "noview" config option you mentioned to supress the default calls.   I'm still only able to access just the data being passed in the utag.view( ) call when referencing variables in the Tealium data layer tab. Will I be able to get to all of the cookie, dom, etc. variables if I have the developer set utag_data on the page?  If not, does the developer need to always pass all of this as parameter data in the utag.view() and uta.link() calls?   One last note, the profile being used for this site is extremely old (ut4.002.201709252212),  We are planning to update this to a more current version in hopes that it will make for a smoother implementation.  I'm also wondering if this is causing the behavior I've outlined above?   Thanks again for your help. ... View more

Thanks for the feedback.  After looking at the issue more closely, the extension code was working properly.  My issue was actually related to changes that were introduced in Optimizely X that alters tracking behavior, which I had mistaken for an extension problem.  For waht it's worth, Optimizely X now does an independent Adobe tracking call rather than merging it's variables into the exisitng pageview call (like Optimizely Classic does). ... View more