Once you've started a debugging session in Google Tag Assistant, you'll be presented with a variety of information about your website's tags and events. This guide walks you through the different sections and features of the Tag Assistant interface, explaining how to interpret the data and use it to troubleshoot and optimize your tag implementation.
About the Tag Assistant UI
When Tag Assistant fist opens, you see the default Summary view with an overview of events and tag information for the requested page. If multiple Google tags or Tag Manager containers are detected, select one to see all hits for that specific Google tag or container.
Note: Browser events may be applied to all containers, but the hits are filtered by the container that is selected.
The left side of the screen displays a list of events. The Output section will display a card for each hit detected for the selected ID.
Events are grouped by the page where they took place. Click on a page title in the left navigation bar to view a page-level summary. A new page group is added to the top of the list as the user navigates to another page in the site that has the Google tag on the page.
Events appear in the order they were fired and are numbered accordingly. Events marked with a are built-in triggers that were emitted automatically when the Google tag loaded. Click on an event in the left column to view more detail.
The API Call shows the JavaScript that was used to configure data for the event selected, which will be either a gtag()
call or a datalayer.push()
call.
Output will show where hits were sent, updates to the data layer, and any errors.
Hits detail
Hits Sent will show where a particular hit was sent, and what kind of hit it was:
When you click on this hit, a detail window will appear. This view shows detail about the parameters that were sent with each hit.
Data Layer
The Data Layer tab shows values found in the dataLayer
object. When Summary is selected, it will display the current state of the data layer, as well as the data that was pushed to the data layer for each event.