Tealium Web Companion (loaded via the Chrome Extension version 1.11.1) seems to have built-in restrctions on the tags that it can analyze. Can anyone confirm these constraints?
I saw a note in one of the help docs that the Extensions analyzed are only those on all docs. This doesn't seem to be the case on the tag listing, as I have some that are all, and some that are using load rules with custom UDO logic.
Second question, are there two versions out there, one that shows three columns on the tags tab? The UID would be hightly useful in triage, but is not there in my version. It shows in the screen shots on this help doc: https://community.tealiumiq.com/t5/iQ-Tag-Management/Tealium-Tools-Web-Companion/ta-p/18523. But this help doc looks like my view with only two columns, the name and status: https://community.tealiumiq.com/t5/iQ-Tag-Management/Web-Companion/ta-p/11947.
If you debugging with utag.loader.cfg, you have to check multiple values. The 'send' and the 'load' value. It is possible that the 'send' value is 1, but if the 'load' value is 0, the tag isn't loaded and not shown in Web Companion. Only if 'load' and 'send' are 1 it is shown in Web Companion. You can either check with utag.rpt. This shows you which tags acutally loaded > for example s_2: 0, in this case 0 means true and s_2 is the tag with the uid 2.
Hopefully that helps
In response to your first question, there are scenarios where the Web Companion will not show what you think.
The issue mainly revolves around how you are versioning. The Web Companion uses the
utag.cfg.utid which is made from
ACCOUNT/PROFILE/VERSION_TIMESTAMP this means that it will pull from the latest revision from that version. So if you have published changes onto the same version, (creating a new revision) this will effect what you see in the Web Companion.
Your second question, with regards to the 2 versions. I wrote the Tealium Tools version to extend the functionality and try to improve the output to more closely match what was really happening.
May it be that some of the tags are scoped under an All Tags load rule? In that case the tags are bundled by default on the utag.js file. I see your note on that, but still it's the only scenario I can think of.
Also, what do you see if you filter by utag. in the network tab of your browser? Do you see all the 20 tags loaded in different utag.N.js files (where N is the UIDs), and all the techonologies are loaded on the page (maybe you can check this out by using Ghostery)?
Please let me know how that works!
06-29-2018 05:48 AM - last edited on 07-02-2018 11:56 AM by kathleen_jo
Ghostery shows a larger set of tags active than the Web Companion @psanchez.
There are only 3 utag.N.js. The rest are evaluated on the client, i.e. are in utag.js.
To the first response, if I analyze the config loader for send=1 and load=1, I only see three. If I look at send=1 and load=4, I see over 20.
07-03-2018 01:00 AM - last edited on 07-03-2018 08:27 AM by kathleen_jo
Then the only options I can think of is either the tags are scoped to all the pages, or they have the Bundle in utag.js option enabled (Tag > Advanced Settings > Bundle Flag > Yes).
Whenever a tag is included on the utag.js, @marksawers, Tealium Web Companion does not show it (which is something a bit annoying sometimes).