Closed (fixed)
Project:
Google Analytics
Version:
6.x-3.3
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
8 Sep 2011 at 23:24 UTC
Updated:
7 Nov 2012 at 16:35 UTC
The "In-Page Analytics" report in the new Google Analytics beta doesn't work and is giving me an error saying:
Problem loading In-Page Analytics
We've identified problems in your setup. These may cause problems loading In-Page Analytics.Your site doesn't load ga.js from Google. If you host the Google tracking code on your own servers, it isn't updated automatically and can miss important changes.
Looking at the code produced by this module, I see it IS being loaded from Google:
<script type="text/javascript">
<!--//--><![CDATA[//><!--
var _gaq = _gaq || [];_gaq.push(["_setAccount", "UA-1236423-1"]);_gaq.push(["_setVar", "anonymous user"]);_gaq.push(['_setCustomVar', 1, "User roles", "anonymous user", 1]);_gaq.push(['_setDomainName', 'store.bioworldusa.com']);_gaq.push(["_trackPageview"]);_gaq.push(["_trackPageLoadTime"]);(function() {var ga = document.createElement("script");ga.type = "text/javascript";ga.async = true;ga.src = ("https:" == document.location.protocol ? "https://ssl" : "http://www") + ".google-analytics.com/ga.js";var s = document.getElementsByTagName("script")[0];s.parentNode.insertBefore(ga, s);})();
//--><!]]>
</script>
Anyone else experience this problem or know how to fix it?
Comments
Comment #1
hass commentedReport it to google who provided you the false alarm, please.
Comment #3
timbrewer100 commentedYou might want to take a look at this helpful article here.
I found I received this error because I don't track administrative users.
Comment #4
technikh commentedI had same issue. resolved it.
my issue was domain name http://www.example.com
but google was pointing to http://example.com in iframe
changed from www.example.com to example.com in analytics account settings and it worked great. hope this helps for others..
Comment #5
philbar commentedThanks TechNikh! That was indeed the problem. I'm using a sub-domain setup.
Comment #6
jefgodesky commentedI'm noticing that I get the error when I'm logged in, but not when I'm logged out. I think it might have something to do with the admin overlay.Never mind, the error is different.