[Plugin: Google Analytics for WordPress] Won't authenticate with Google Analytics.

Hey ive just had the same problem.

However i could almost put my problem out there as i know what caused it, just need help to fix it. What i did was delete my old admin user and created a new one. Once the original admin account was deleted thats when the analytics stopped working. Now i need to know how to fix it. It was great while it lasted, its a perfect plugin, however i think its google. Google Analyticator is the best plugin with great results. please help us fix this problem, im about to go live ??

I had the same problem, though it was not caused by the scenario described by waynmeyer. Thanks for your help.

I’m having the same problem with just one of my wp sites.

I get an error that says something about “insufficient permission”

It get’s worse. With the recent update, I went in and checked everything, to find that Google Analytics has stopped showing any data since May 22, of this year. I’ve been relying on this plug-in, and with the summer, didn’t review my Google Analytics – but was incredibly prolific. No numbers to show for it?

now, with the last update, I can’t fix the problem (won’t authenticate), and I have no tracking data since May.

Yea, I read the support pages.., and manual authentication doesn’t work either. Something bad happened. Any ideas? I have no way to know what happened in May, either.

In looking at the google analytics admin page, this message is displayed.

“Tracking Not InstalledLast checked: Sep 1, 2012 10:27:24 AM PDT
The Google Analytics tracking code has not been detected on your website’s home page. For Analytics to function, you or your web administrator must add the code to each page of your website.”

I’ve manually authenticated…, several times over the past few weeks. Clearly something is not working…, could be user error – I’m open to that. Need any guidance experts can offer.

Same problem with my wp-installation – I already documented it here: https://www.ads-software.com/support/topic/plugin-google-analytics-for-wordpress-authentication-with-google – since I never had this issue before, I guess it must have something to do with the plugin’s recent update.

Hey everyone

I’m still having the same problem, however I believe it was for the better. I recently just decided to do without the plugin. Here’s what I did that works 100x better.

Firstly I should mention that I believe it’s the google auth problem rather then the plugin. What should work is to flush out the plugin from your database table. Always backup if you going to try this. Simply login to your server host and use php my admin to find that database table from the plugin, then reinstall and activate as normal see if that works. Clear the cache while you at it.

I was going to do the above until I played with google analytics and decided that there is way better results there. People forget that the actual core of every plugin has better features “standard” and free. So I decided to link that up to. My iPhone app analytics pro. Now I’m way better off as I can watch my analytics on the go. I instantly fell inlove with the instant results on the go that I’ve never looked back.

Any other experiences in finding and alternative would be great to share.

OK, any more ideas from the wizards…, I need help. I just “inspected” the home page html for my site, and the google analytics code is inserted in 3 places, so the message from GA is incorrect. It just isn’t detecting my key.

Ideas?

Hi Andrew

Did you try the database trick? Flush out the old and start fresh?

I am getting “Invalid Token” when I click on button “Click here to authenticate with Google.”

I try to install google analytics for word press and try to activate and get error:

The application that directed you here claims to be “Google Analytics for WordPress by Yoast”. We are unable to verify this claim as the application runs on your computer, as opposed to a website. We recommend you deny access unless you trust the application.

How do you FIX IT? Please Help!

(https://www.whatattractsmentowomen.org) Thank You ….Charlie

Hi Waynmeyer,
I’m a little uneasy with the “flush database” approach. Probably over my head. Sure would be good to have Yoast comment here…, this seems to be a bigger issue with the last few updates not “updating” cleanly.

I’ll try the uninstall, and reinstall…, but now I’m cosidering just dropping the plug-in. I see several other forums are suggesting that’s the better route. Inserting the std. asynch code in the footer that Google tells you to do may not give the granularity that Yoast’s plug-in is supposed to deliver, but at least that works – by other’s accounts.

FWIW, folks, I always wait til I have a support issue before sending plug-in developers’ a paypal donation. If the support is good, then I’m all over a 3figure donation to a developer that produces both a great plug-in and good service and support. This one, with all the hype, is not going in the right direction. …best to vote with your wallet. ;-]

I would rather not give up – if someone could at least identify the problem, and point to a solution – even if it is coming in a future revision from Yoast. Communication is key.

I have a batch of sites using this plugin, and suddenly the Dashboard widget isn’t working on ANY of them. Most are still feeding traffic back to GA, but you need to visit GA to see the results. So having read through the above and being short for time, I have to say that I think Google must be at fault here – or that this fantastic plug-in hasn’t kept up. Our developer, on who we all rely, isn’t a lively correspondent! Positively taciturn.

Matthew,

I don’t know…, I spent about 12 hours the past two days, and think that the issue is either a bug, or has to do with “caching”…, Plug-ins often cache so they don’t have to regenerate common code from the DB. That would be an obvious thing to do here. And, if the updates yoast puts out don’t “clear the cache” as part of the install process, then the changes to the plug-in don’t apply. This could be due to an install bug, or could be a glitch in the update for a number of reasons.

What is needed, like what is found in well developed performance-based caching plug-ins (nice list of these found at: https://j.mp/OMJzPN), is a button to clear the plug-in’s cache, manually, and rebuild from the database the yoast content for the header/footers. THAT would be a nice plug-in feature. [Or even an idea for a standalone plug-in that selectively cleared cache for plugins that misbehave.]

I’ve found a few other leads, and checked all those. And, there seems to be a “_utm.gif” call missing from the Yoast code, at least in my site – I learned about this on the Google Developer Analytics site. https://j.mp/REwt7f . Assuming I read it right – which it is entirely possible that I did not!.

I’m not coder, so I can only read what it says, and it indicates in debugging, that there needs to be this call, with two parameters – also missing…

I like Yoast’s stuff, but I can’t feel good about paypal’ing donations to a developer that doesn’t respond. And, his Bit.Ly plugin has never worked for me, or a dozen of my friends…, I gave up on that one.

We’re all fallable ;-] I’m continuing my search for answers.

For others reading this thread, I did find another data point that indicated that google tracking fails if you have a naked domain name (one without the “www.” The issue, if you configure google analytics’ profiles for the name with “www.” in front of your domain, and it should not be…, (IF your domain is a naked one…) then GA will fail, as it considers naked domains different than ones with the “WWW.” in front of them.

I’m not the expert here – please refer to the site where I found this: https://j.mp/OhBiUI for the full story.

FWIW, I found that I had this issue – and ensured that I had every location in my database to use the naked domain name, that means in every place in SEttings, and such, and even at my host, under the cpanel, … as well as the multiple places you have to have it in your GA settings, I put all the same domain syntax.

Alas, that has not fixed this for me – but it has eliminated that issue as one variable.

I am putting this here in hope that this helps someone.