Search
Clear search
Close search
Google apps
Main menu

Google Analytics Errors

Add Google Analytics

Consider update to the async version

Detected both ga.js and dc.js scripts which will make tracking ambiguous

Detected both ga.js and urchin.js scripts which can cause reporting errors

Ensure your method name begins with a "_"

Invalid or missing web property ID

Leading or trailing whitespace in ID

Method 'X' has X additional parameter

Missing closing script tag

Missing JS script

Missing X required parameter(s) for method 'X'

Move the tag inside the head.

Move the tag outside of the iframe

Remove the deprecated method, "XXXXXXXXX"

Tag is included in an external script file. Ensure data is being collected as expected

The value for parameter 'X' in method 'X' should not be quoted

Unknown method name: 'XXXXXXXXXXX'

Verify your code since this is a non-standard implementation

Warning: Opted out of Google Analytics

Missing HTTP Response


Add Google Analytics.

We have detected that there is no Google Analytics tracking code found on this page.
Failing to have Google Analytics tracking code on this page will prevent data from this particular page from associating to your Analytics account.
Solution: Ensure that you add the Google Analytics tracking code onto this page before the closing tag.

Consider update to the async version.

We have detected that the Google Analytics tracking code on this page is not the asynchronous version of the tracking code snippet.
While data will report to your Google Analytics account, both the pageview and user data may be unreliable as compared to the asynchronous tracking code which is placed in the
section and runs simultaneously with the rest of your code.
Solution: Update the tracking code to the asynchrnous version of tracking code to ensure the most relaible Google Analytics data.

Detected both ga.js and dc.js scripts which will make tracking ambiguous.

Installing multiple instances of the Google Analytics Tracking code on a single web page, especially different versions of the code, is not a supported implementation. This error denotes that the page currently uses both the ga.js version and dc.js Display version.
While data will report to your Google Analytics account, both the pageview and user data will be unreliable. This will result in pageviews/visits over-reporting and Display-eligible users potentially under-reporting.
Solution: Ensure that there is only one version of the Google Analytics script on the page. You must choose to migrate to the dc.js version or use the pre-existing ga.js version.

Detected both ga.js and urchin.js scripts which can cause reporting errors.

Installing multiple instances of the Google Analytics Tracking code on a single web page, especially different versions of the code, is not a supported implementation. This error denotes that the page currently uses both the ga.js version and older urchin.js version.
While data will report to your Google Analytics account, both the pageview and user data will be unreliable. This will result in pageviews/visits over-reporting.
Solution: Ensure that there is only one version of the Google Analytics script on the page. You must choose to migrate to the ga.js version or use the older urchin.js version.

Ensure your method name begins with a "_"

All methods in Google Analytics begin with the underscore character "_". This is a syntax error which denotes that you referenced a valid GA method, but did not begin the method with "_"
Failing to initiate the method with "_" will prevent the method from executing properly and will thus impair tracking. For instance, if you declare 'trackPageview' instead of '_trackPageview', the pageview method will not execute and no pageview will be recorded.
Solution: Ensure that all Google Analytics methods referenced on the page follow proper syntax and begin with "_"

Invalid or missing web property ID

The Google Analytics web property ID is not properly set within the Google Analytics JavaScript. The web property ID is used to associate the Google Analytics request to a specific Analytics website profile.
Failing to properly set the Google Analytics web property ID will prevent pageviews from associating to your Analytics website profile.
Solution: Ensure that Google Analytics web property ID in the Google Analytics JavaScript on your page matches the Google Analytics web property ID generated in your Analytics website profile.

Leading or trailing whitespace in ID

The Google Analytics account ID is not properly set within the setAccount function in the Google Analytics JavaScript. There is a whitespace (empty space) either before or after the account ID that prevents the correct ID from collecting.The account ID is used to associate the Google Analytics request to a specific Analytics website profile.
Failing to properly set the Google Analytics account ID will prevent pageviews from associating to your Analytics account.
Solution: Ensure that Google Analytics account ID in the Google Analytics JavaScript on your page does not contain any extra or empty spaces. The account ID in the script should match the Google Analytics account ID generated in your Analytics website profile.

Method 'X' has X additional parameter.

Each method in Google Analytics has a set number of allowed parameters. This error denotes that you have exceeded the number allowed parameters for the given method.
Exceeding the number of allowed parameters will either cause Google Analytics to drop any parameter over the limit OR cause Google Analytics to fail to record data associated with the given method.
Solution: Review the documentation and parameter allocation for the respective Google Analytics method here: https://developers.google.com/analytics/devguides/collection/gajs/methods/. Ensure that your implementation follows the documentation appropriately.

Missing closing tag

When the Google Analytics JavaScript executes on your site, a call is made to load a larger file from google-analytics.com/urchin.js. This file is critical to Google Analytics data collection. This error denotes that the call to google-analytics.com/urchin.js was not made and the request is missing from the JavaScript.
Omitting the call to urchin.js will prevent all Google Analytics data collection and will thus prevent any data from reporting in your account.
Solution: Ensure that your Google Analytics script contains the full request to google-analytics.com/urchin.js. The script on your page should match the script that is generated in your account.

Missing JS script

When the Google Analytics JavaScript executes on your site, a call is made to load a larger file from google-analytics.com/ga.js (dc.js or analytics.js may also be used depending on your script version). This file is critical to Google Analytics data collection. This error denotes that the call to google-analytics.com was not made and the request is missing from the JavaScript.
Omitting the call to google-analytics.com will prevent all Google Analytics data collection and will thus prevent any data from reporting in your account.
Solution: Ensure that your Google Analytics script contains the full request to google-analytics.com. The script on your page should match the script that is generated in your account.

Missing X required parameter(s) for method 'X'.

Each method in Google Analytics has a set number of required parameters. This error denotes that you have not entered the number of required parameters for the given method.
Failing to implement the number of required parameters will either cause Google Analytics to incorrectly record data parameter for the given method OR cause Google Analytics to fail to record data associated with the given method.
Solution: Review the documentation and parameter allocation for the respective Google Analytics method here: https://developers.google.com/analytics/devguides/collection/gajs/methods/. Ensure that your implementation follows the documentation appropriately.

Move the tag inside the head.

We have detected that the Google Analytics tracking code is outside of the
section on this page. This decreases the likelihood that the tracking beacon will be sent before the user leaves the page.
One of the main advantages of the asynchronous snippet is that you can position it at the top of the HTML document. This increases the likelihood that the tracking beacon will be sent before the user leaves the page. We've determined that on most pages, the optimal location for the asynchronous snippet is at the bottom of the
section, just before the closing tag.
Solution: Ensure that you add the Google Analytics tracking code onto this page before the closing tag.

Remove the deprecated method, "XXXXXXXXX"

We have detected that you are using a recently deprecated method. This method is no longer active within the Google Analytics library and should be updated.
Using a deprecated method will not prevent Google Analytics from collecting data. However, it is very likely that using a deprecated method is affecting data integrity.
Solution: Review your code and ensure that you are only using active methods found in the Google Analytics library: https://developers.google.com/analytics/devguides/collection/gajs/methods/.

Tag is included in an external script file. Ensure data is being collected as expected.

We have detected that the Google Analytics tag is included in an external script file rather than being placed on the page source code itself.
While data may still report to your Google Analytics account, you'll want to ensure that the tag is executing the _utm.gif request as expected.
Solution: Ensure that the tag in the external script file is executing as expected.

Tag is included in an iFrame. Ensure data is being collected as expected.

We have detected that the Google Analytics tag is included in an iFrame rather than being placed on the page source code itself.
While data may still report to your Google Analytics account. You'll want to ensure that the tag is executing the _utm.gif request as expected.
Solution: Ensure that the tag in the iFrame is executing as expected. You can learn more about Google Analytics and Framed sites here: https://support.google.com/analytics/answer/1012049?hl=en.

"

The value for parameter 'X' in method 'X' should not be quoted.

This error denotes that you have added quotes to a parameter that should not be quoted. Only strings should be passed in with quotes. All other types should be left unquoted. Any value that is not a string, such as a booleans, object literals, functions or arrays, should be passed in without quotation marks. Use only quotation marks when you are passing in something that is meant to be interpreted as a string. If you are migrating from the traditional syntax, any function parameter that was passed in without quotation marks should remain unquoted in the asynchronous syntax
Adding quotes to any value that is not a string can cause Google Analytics to either incorrectly record values OR fail to record values for the associated method.
Solution: Ensure that you are only using quotes for strings. You can review which values are considered strings and should be passed in quotes in our documentation here: https://developers.google.com/analytics/devguides/collection/gajs/methods/

"

Unknown method name: 'XXXXXXXXXXX'

We have detected a method that does not exist in the Google Analytics tracking library.
Calling a method that does not exist in the Google Analytics library means that data associated with this method would not record any data. General data collection for Google Analytics may not be affected.
Solution: Review your code and ensure that you are only using methods found in the Google Analytics library: https://developers.google.com/analytics/devguides/collection/gajs/methods/.

Verify your code since this is a non-standard implementation.

We have detected that the Google Analytics tracking code on this page is a non-standard implementation.
Using non-standard code implementation on a page may prevent data from reporting into your Google Analytics account, and any associated data may be considered unreliable.
Solution: Verify that your code is set up properly as indicated by the tracking code given in your Google Analytics account.

Warning: Opted out of Google Analytics

No Google Analytics HTTP response because of opted out extension denotes that your browser is currently using an extension that tells the Google Analytics JavaScript not to send data to Google's server. This is strictly a tracking issue generated by the extension and is not reflective of the tag implementation.
This does not actually affect tracking for other site visitors. It only prevents your browser from getting tracked across the web where Google Analytics is implemented.
Recommended Action: You may consider de-activating the extension while troubleshooting the implementation on your site. For more information about the Chrome Extension, please visit the Chrome Store: https://chrome.google.com/webstore/detail/google-analytics-opt-out/fllaojicojecljbmefodhfapmkghcbnh

Missing HTTP Response

Missing HTTP Response denotes that, while the Google Analytics code was detected in the page source, the script itself did not execute. Each time the Google Analytics script executes, we expect an HTTP Response carrying the tracking request to Google’s servers.
This means that the Google Analytics code is not implemented properly on the page and no data will be collected.
Recommended Action: Reinstall the Google Analytics snippet by removing the current iteration, copy a new version from the Analytics interface, and insert that version into the site.