If you're unable to authenticate with Google, here are the recommended steps for troubleshooting the problem:

1. Verify Google allows the authentication.

First check that Google is allowing your website to authenticate with Google's servers. If you're able to click the Grant Access button and get sent back to Analyticator's settings page, Google is accepting the authentication of your website. If you receive the following message during authentication, it is recommended to first try adding your domain as an authenticate domain in your Google account. Should that fail, post in Google's API support forum for help, as the problem exists on Google's end.



2. Verify your server is not hitting a memory limit.

If you receive an error message, a blank page, or other unexpected result after being sent back to Analyticator's settings, your server may be hitting a memory limit. Try the solutions in this FAQ, and attempt to re-authenticate.

3. Verify your server is not having issues connecting to Google Analytics.

Occasionally, some servers have issues with one or more of the connection methods Google Analyticator uses to authenticate with Google. To attempt to resolve these incompatibilities, a compatibility setting is provided. At the bottom of Google Analyticator's settings page use the "Authentication compatibility:" setting. Attempt to disable cURL first, then disable cURL and PHP Streams. After each setting change, attempt to re-authenticate with Google.

4. Verify your server is not blocking outbound SSL connections.

If all of the above solutions do not allow you to authenticate with Google, the final recommended step is to contact your host for support. In some instances, hosts will disable outbound SSL connections or have issues with their SSL library installed in PHP. Point your host to this support article, and let them know that Google Analyticator is attempting to make an outbound SSL connection to http://google.com/ (which does not always resolve to the same IP) and uses port 443. The default connection method is cURL, with fallbacks to fsockopen and fopen.

5. Enjoy Google Analyticator without authenticating.

Hopefully one of the above methods will work. If not, Google Analyticator can still be used without authenticating. Provided you manually add your UID to Analyticator, everything will work fine with the exception of the dashboard widget and theme widget.