- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
javascript:(function(){window.open("","UDO Inspector","width=600,height=514,scrollbars=1").document.write("<script language=\"JavaScript\" id=\"udoaudit\" src=\"//tags.tiqcdn.com/utag/adrian-test/tools/dev/utag.4.js?"+Math.random()+"\"><\/script>");}());
What can it do?
At the top of the window, you have the values from:
So when you are on a site having to scroll through the source of a page can be a pain trying to find the raw data layer, so what the UDO Inspector attempts to do is to scrape the source of the page to find the raw utag_data (or whatever the udo_name has been set to)
Once it is found, it will display it "as is", so if the data layer is formatted badly, then that is what will be shown.
So looking at a badly formatted data object isn't easy. So on this tab you will be able to see that data in two formats. Table & JSON format.
The JSON object is correctly syntaxed so you are able to copy the JSON object and paste it into a utag.view or utag.link call.
This is the utag.data once the All Tags Extensions have been run through.
Again this can be view in either a table or JSON format.
Status
Variable Types
Each of the above options is clickable, and you are able to show/hide each type as you wish to see.
View/Link/A custom event
What you see here is any calls that have been sent to utag.view/link({}); or utag.track("custom_event", {});
Sent Data - Event Type
This is the data that will be sent to a tag. This is achieved by a blank tag being created which is called by the send() call, this has the UID of 0.
UID - Event Type
Every tag that has at least one extension will gain a new extension that takes a copy of the b object before continuing with the rest of the the tags send code.
UID - Tag ID
Event Type - View/Link/Custom event
Selecting an item will show you the data that was sent in that call, with both the JSON and Table views.
Selection two items, will allow you to compare two calls to see what was different in the data object. The colours are the same as those from the Diff tab.
When the UDO Inspector starts up, it sets the utag debug cookie:
document.cookie="utagdb=true";
From this point onwards, all calls that the utag.js or a utag.x.js files makes to the debug function, these are listed in this view.
This tab reloads whenever the load rules get re-evaluated, so you can see in real time which load rules are currently active. There are two statuses Fired / Not Fired.
The load rules are listed with all Fired items at the top, and Not Fired items towards the bottom. Within each group they are sorted by their Load Rule ID.
Copyright All Rights Reserved © 2008-2023