I think through trial and error I discovered that `b` represents the utag_data object so in some cases I reference it directly:
b.page_name = "test";
This feels dangerous, especially if Tealium changes the variable at some point. And also, with the "scope vars" field, how do you actually use it?
I believe the syntax checker no longer looks for variables out of scope so this feature will most likely be removed from the UI eventually.
Regarding the "b" variable. The b variable is the tag's local copy of the utag.data object. This variable is safe to use and not go away or change at some point.
Thanks @Ty, other than debugging the Tealium source code and setting breakpoints are there quicker/easier ways to determine the variable mappings - so that you could easily find what local copies map to what?
Does that make sense?
This will output the "b" object to your console. That may be a little quicker to debug than setting breakpoints.
To enable debugging, set this cookie:
If you mean mappings you can go to the Tag tab, then go the tag you're interested in and select Edit in the Mapping Data Sources box. Here you will see the tealium variables to that specific tag variables mapping.