Why do I get 'Storage not available. Aborting hit.' with Google Analytics?

Question

I'm setting up with the new Google Analytics tracking code.

<script>       (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){       (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),       m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)       })(window,document,'script','//www.google-analytics.com/analytics.js','ga');        ga('create', 'MYUACODE', 'MYDOMAIN');       ga('send', 'pageview', {           'page': '/setup',           'title': 'Setup Page'         });      </script> 

I've got this inside my HEAD tag as Google tell you to do Obviously MYUACODE and MYDOMAIN are the real variables in my page :)

However when I run this using Google Chrome and I turn on the Google Analytics Debug extension, I get the following message:

Registered new plugin: "linker"       analytics_debug.js:5 Creating new tracker: t0              analytics_debug.js:5 New visitor. Generating new clientId  analytics_debug.js:5 Storage not available. Aborting hit.  analytics_debug.js:5 

It seems to fire up correctly and starts setting up the items, but then it says Storage not available and it seems nothing ever gets to Google.

Now if I remove all this code and go back to the original Google Tracking code, it works fine, I just can't seem to get this new style to fire correctly.

Any thoughts? Help? Thanks in advance

Answer 1

I had the same error message. It seems to be related to not being able to set the cookie correctly. In my case, it happened when I was testing off localhost and I hadn't set my cookieDomain to none.

You may want to try something like the following and see if it works. I'm not sure if the method of passing your domain that you have works.

ga('create', 'MYUACODE', {   'cookieDomain': 'none' }); 

Answer 2

Google Analytics used to generate the tracking code with the hostname hard coded in the create method, which could cause this error when testing on a different hostname. Now when GA generates the tracking code it uses

ga('create', 'UA-XXXXXXXX-X', 'auto'); 

which automatically determines the cookieDomain value. Changing the hardcoded hostname to 'auto' in this method call has fixed this issue for me on several sites that had the old tracking code generated.