Analytics Debugger
Your Single Source of Truth (SSOT) for debugging analytics implementations
Prints useful information to the JavaScript console by enabling the debug version of the Google Analytics Javascript.
Review user movement across collected snapshots.
View collected rating snapshots from the latest 7-day window to assess rating stability.
Compare 1-day, 7-day, and 30-day net growth and growth rate.
Review publication date, version, supported languages, and crawl timestamps.
Review the store description, core capabilities, and common use cases.
This extension loads the debug version of the Google Analytics Javascript for all sites you browse using Google Chrome. It prints useful information to the Javascript console. These messages include error messages and warnings which can tell you when your analytics tracking code is set up incorrectly. In addition, it provides a detailed breakdown of each tracking beacon sent to Google Analytics.
To use this extension, You need to follow three steps:
1. Turn it on by clicking its icon to the right of the address bar.
2. Open the Chrome Javascript console to see the messages.
On Windows and Linux, press Control-Shift-J.
On Mac, press Command-Option-J.
Inspect the latest comments and rating distribution.
Store average score: 4.2. The bars below are calculated from synced review text only, so they may be empty for extensions that have public ratings but no synced comments yet.
Review related products from the Chrome Web Store detail page.
Your Single Source of Truth (SSOT) for debugging analytics implementations
The Tag Assistant extension works with Tag Assistant to help troubleshoot installation of gtag.js and Google Tag Manager.
The simplest way to debug and verify dataLayer implementations without using the browser console
Browser DevTools extension for debugging Google Analytics 4 (GA4) events.
The easiest way to debug and check the dataLayer implementations without having to use the browser console!
The Tag Assistant Companion extension works with Tag Assistant to help troubleshoot installation of gtag.js and Google Tag Manager.
Not working even if it's ON. Please check the issue with latest Chrome version.
This used to be the best debugging tool out there for GA and GA4. It helped determine which measurement ID each event was sending to to help identify possible incorrect locations for events being sent when multiple measurement IDs are loaded on the page from GTM. Now it no longer works and just crashes the page and renders nothing in the console when it does load. I wish this tool would make a comeback because the other GA debuggers out there do not compare
Could be better in many ways.
I don't know how many screenshots of the console output I've sent to web developers to show them that the consent manager settings are incorrect. Thanks for this helpful browser extension
Hi all, this extension does not support GA4 and hasn't bee updated for several years. I've developed a replacement tool, supporting also GTM and other ad networks and analytics tools as well. https://chromewebstore.google.com/detail/analyticsgtmpixel-debugge/canpneabbfipaelecfibpmmjbdkiaolf
Trying to filter developer traffic in GA4. Have the data filter setup in GA4 correctly but not sure how to enable debug mode. Supposedly this should do it, but don't think it's working. Didn't have high expectations since this was updated back in 2019.
Seems to work, even though Google hasn't touched it in 3.5 years. And, I was not able to find any documentation on how to properly use this or interpret the results. Google is one of the wealthiest companies on the planet, yet they can't find their way to hire a small team to maintain and document this tool? Typical Google Greed.
It used to work perfectly with the previous version but now, with GA4 doesn't work anymore.
As of today this is the extension Google recommends we use to Debug GA4 events. Works great!
Sadly I can't use this because we apparently have 5,000 "Debug devices" with similar names. Until they fix this... it is useless and we can't validate any tracking. How did they miss this?