Campaign Dashboard Error: "Our Connection to Your Google Account Has Been Lost"

[Kingalan1]

I keep getting the following error in my Campaign Dashboard:

“Our connection to your Google account was lost. Don’t worry, you won’t lose any data”. Please reauthorize now.

I do reauthorize but by the time I log out and log back in, the same message gets displayed.

Any ideas?

Thanks,

Alan

[samantha.chapman]

Hey there!

Sam from Moz's Help Team here!

Typically, this means that your Google Analytics authorization token has become invalid. Nothing to worry about though!

Google goes through a process called "Oauth" when it comes to authorizing access to the services that are linked to your Google account. Under any single Google account, tokens are used to provide access to a bunch of different services, from Gmail to the apps on your phone. Google has a 25 token limit for each account, which means you can have up to 100 profiles in a single account, but will only be able to connect 25 of them to other services in total.

If a connection is lost and the token remains valid, the re-auth feature you will see in that pesky red error message will re-connect your profile. If it is not valid, you will need to revoke the token manually and disconnect/re-connect your GA account. Tragically, the re-auth button in the red notification box will not work in this scenario...

What you'll want to do is this:

1. Firstly, make sure you are completely logged out of all Gmail/Google accounts.

2. Follow this link: https://accounts.google.com/issuedauthsubtokens. You'll be prompted to log into your Google Analytics account.

3. Revoke the token for Moz.

4. In your Moz campaign, disconnect and then re-connect through the "Connect another GA Account" link, and re-select the profile.

   This should refresh your token and get your GA account set. Let me know if you're still running into problems after this and I'll take another look!

[ViviCa1]

I was getting the same yesterday. Clicked the link and reauthorised, then refreshed the page and the notification was back up. I figured it must be a bug given that I had just reauthorised (several times).