Google In-Page Analytics Errors
Hello lovely WA family!
For anyone who uses Google Analytics and knows that everything else is working properly, but sees this message upon trying to use Google 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.
We didn't find a tracking snippet on your site. In-Page Analytics cannot load. Please make sure you have tracking installed correctly. If your snippet is included in a separate JavaScript file, you'll have to manually check it is being loaded correctly.
I've found the solution. Now, let's get something clear straight away in case you're being given bad advice:
IT IS NOT THE ALL IN ONE SEO PLUGIN!
The failure to load in-page analytics errors was due to.....
wait for it.....
GOOGLE CHROME.
Yes, that's right, Google's own browser prevented Google's own analytics from loading as "insecure content." Hilariously ironic isn't it?
If you're not using Chrome, don't fret, because my research reveals similar conduct can occur in other browsers as well. All you have to do is find out how to force your particular browser to reload what it deems as unsafe content, and it should work for you as well! Checking for similar shields or warning icons in your address bar is the best place to start.
Anyway, here's the fix for Chrome:
When you try to load in-page analytics, have a peek up in your address bar next to the favorite star and you'll see a little shield icon. That's Chrome's notification of insecure content.
Normally, you should be able to click that little shield and say "load unsafe script", at which point it reloads the page and things work as intended.
However, as of the date of this blog post, the last release of Chrome (3.4xx) broke this button. So, if you're on that version and want it fixed immediately, go download Chrome Canary, the beta version for next release (3.6).
I tested it, and voila, Chrome now loads the unsafe script when I tell it to, and In-Page Analytics works!
Cheers and love,
Jen
Recent Comments
15
ooooh, I love the smell of tech help in the morning- good spot, good solution, good job, respect due! A
See more comments
when obtaining google analytic access code for authorization of plug in when I ask for the access code this is there communica 401. That’s an error.
Error: invalid_client
Bad request.
Request Details
scope=https://www.googleapis.com/auth/analytics.readonly https://www.googleapis.com/auth/analytics
response_type=code
access_type=offline
redirect_uri=urn:ietf:wg:oauth:2.0:oob
approval_prompt=force
client_id=Maurice
That’s all we know.
also can you explain client secret? what are they asking for