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