Debug Google Analytics with Google Analytics Debugger
When using Google analytics, it's easy to find out if you have the tracking code installed, but that doesn't mean that it is working. Even if Google reports the tracking code has been detected and installed, you may have syntax errors that can cause problems.
To properly check your Google Analytic tracking code, you should first ensure it is installed, and then ensure there are no errors within the tracking code iteslf. In this tutorial, we will walk you through these steps.
Ensure your tracking code is installed
Checking your tracking code for errors
The Google Chrome browser has an addon that is available that will check and debug the Google Analytics code for any errors. The following tutorial will explain how to use the Google Analytics Debugger.
- Visit the Google Chrome store for Google Analytics Debugger
- Click the Available on Chrome button on the top right.
- Next, Click the GA Debugging icon at the top right to turn the Google Analytics Debugger On.
GA Debugger off GA Debugger On
- Visit the your site to view the Google Analytics process. When the debugger runs, any error will show in red. In this case the following error is thrown:
The _setAccount API expects an account string for argument 0. The argument given (36141341-1) does not match the expected format of UA-XXXXXX-X.
This error is caused by the Google Analytics code not being set to the correct account format.
Analytics Error No Analytics Error
If you see the above error or one similar, visit this page for a comprehensive list of possible problems and how to correct them.
Support Center LoginOur Login page has moved, Click the button below to be taken to the login page.
Social Media Login
2014-03-13 4:58 am
I am in charge of different websites and for some of them, the debugger doesnt work at all, since there is no information ... the screen is just blank
However, I am receiving data, so the code is installed and "working"
Why do you think it can be happening?
2014-03-13 8:11 am
It could possibly be due to an old version of the tracking code being present in your sites. Other code on the site could also be preventing the information from being displayed.