Google Analytics keeps disconnecting, requires "Reauthorization"

[TotalMarketExposure]

I have many campaigns connected to our Google Analytics account (all websites in same GA account) but I keep getting the message "Our connection to your Google Analytics account was lost. Don't worry, you won't lose any data. Please reauthorize now.".  I go through the motions of "reauthorizing" and it tells me I'm successful.  Minutes later it gives me the same message.  I even keep my GA account logged in on the same computer, trying to avoid this.  As a result, I'm not getting my Analytics data in my campaign.  Help!

[S2RSolutions]

I had this issue for the longest time. We would follow all the suggested fixes yet the problem would keep happening.

Worked with the Moz help team for some time to find a solution.

I was told that the API to GA had some "limits".

I believe there could only be 25 calls for the google account. Once you hit the 26th, the first one would loose the connection. Which is what you are seeing with that Moz error message.

Sorry this is not the best explanation, I am not very technical.

What we ended up doing was creating a new dedicated Moz GA account for each 20 URLs (so we had a bit of wiggle room) we were monitoring and made sure nothing else hit the GA api for those URLs within that account. Havent had a disconnect issue since.

Hopefully this helps you as well.

[ThompsonPaul]

Unfortunately, this is a known bug, and for some reason, Moz still hasn't put a link to the solution on the same page as the error is reported. (The error has been occurring for users for over 6 months, so this is pretty inexcusable IMO).

Anyway - instead of re-authorising your Google account, you're going to need to completely disconnect it from your Moz campaign, then reconnect and re-authorise it. Your system is essentially storing a broken auth token, and just re-authorising doesn't replace the token. That only happens if you fully disconnect then reconnect the account.

Hope that helps?

Paul

P.S. Here a link to a previous Moz response to the same issue including screenshots for the process if you need them.