I forgot to tell you that the passed object will become reality for that particular call. That is why you only see your changes to 'b'. So instead of doing all of the above (you can of course do that if you need to be able to do more "house cleaning" on utag.data when "claudio" event is happening) but you could just update the utag.data object with the new pre-condition for your lookup table extension and then call utag.track with utag.data as argument. I think that would do it, without the need for your custom container tag merging data from 'b' onto utag.data. For example: utag.data.my_data_source = "something else"; utag.track("claudio", utag.data); Both flavors should work, though I would not recommend doing too much of this stuff so please be careful. In an ideal world when pre-conditions to the page change, pass in a new fresh object every time and do not reuse previous data from the sticky utag.data object on the page. In a very heavy ajax environment, it makes it very hard to maintain. The data object (UDO) data sources, at least the vital ones like page_name, page_type, product_ids etc, should be provided and maintained by the developers of the website, not built and maintained inside Tealium.
... View more
Expand/CollapseMenu
