ObservePoint Tag Debugger Explained

Overview

This article explains the information displayed from the tag debugger. For information on troubleshooting, downloading, and using the Tag Debugger see: ObservePoint Tag Debugger (Chrome Extension).

Download the OP Tag Debugger in the Chrome store.

Tag Name

All the marketing tags that fire on a page show up under the column Tag Name. Underneath Tag Name is the Path, which is the URL link where the tag was called from. Clicking on the Tag Name brings up the full URL path. In the debugger window, the URL is displayed as Actual and Decoded Request. Selecting the variables tab will display a list of all variables for that particular tag.

View the URL request from where the tag is called, by clicking the path.

Account, Category, and Status Code

The Account column displays the ID number associated with the tag. One tag can have multiple accounts. The category column classifies the type of tag it is i.e. Analytics, Advertising, etc. Status codes indicates the result of the page load. A list of their meanings can be found here.

Request Size and Response Size

A request is relayed from a network to a server and the server responds. Request size shows the outgoing http size in Bytes while the response size is the server side's response to the original http request.

The size of request and responses displayed in bytes.

Total Time and Latency

The time period from when a request is sent until the server responds is called Latency. The Total Time is the time after the server responds and the tag loads.

For example, in the figure below you see it took around 2017 ms from the time a request for a tag was sent for a response to be received (the Latency period). An additional 17 ms from when a response was received was needed for the tag to load on the page (total time).

These metrics can alert you of long page load times.

Look under the Page Load Time report in the application for more information.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.