On last Update, plugin disconnected and stopped tracking in GA

  • Greetings,

    The last time I updated plugins, the plugin disconnected and stopped tracking in Google Analytics.

    While hosting is still tracking traffic, I would like to avoid this in the future.
    And since I use this plugin on tons of sites… I’d like to use install a tracking code backup, or if there could be some kind of reconnect reminder, after the update?

    I know how to install manual tracking for now, but I wanted to check and make sure it wouldn’t pose a conflict.

    Thanks so much for your assistance.

    Best
    Amanda

    plugin disconnects API on update

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)

  • This has happened to me twice now. It’s infuriating lately to have to go and check on dozens of sites one by one.

    This happened here as well. We have a large number of sites that we use this plugin for and never received word that the plugin had been disconnected. It seems user activity started to peter off around December 8th-11th according to GA and we had no idea that we needed to re-authorize until a client emailed us about it. I would really like to know if this issue is going to happen again and what I can do about it.

    Hi,

    The normal behavior won’t require a plugin re-authorization after an update.

    Furthermore, as mentioned on plugin’s documentation, if an authorization error is detected the authorization is automatically cleared without affecting the tracking code.

    I’ve also checked the code to make sure that there isn’t any token reset call that could accidentally clear the tracking configuration. Practically, the tracking code can be disabled or cleared only after a user interaction (for example a user which is trying to re-authorize the plugin but fails to do so).

    If you think that the above isn’t the case, please provide some more details. It would be interesting to see the error displayed on the Errors & Debug screen which could determine the described erroneous behavior.

    @jimmycrackedcorn

    It’s infuriating lately to have to go and check on dozens of sites one by one.

    I hope you don’t authorize the sites using the same Google account, because there are some refresh token limits enforced by Google and you’re basically authorizing the sites in a loop. When the 26th site is authorized the first one loses its authorization. For details see https://deconf.com/error-refreshing-the-oauth2-token-message-error-invalid_grant/

    • This reply was modified 6 years, 11 months ago by Alin Marcu.

    Alin- I think you’ve just made me aware of something I did not know regarding a limit of 25 sites authorized on one Google account. Hmmm. That’s not good. Thank you.

    This same thing has been happening to us starting in early December. Out of 55 clients it’s happened to about 8 of them.

    I went into the Error & Debug log and it says last error none.

    Hi,

    @jmilesmiller you need to check the Errors & Debug screen before reauthorization.

    Are you authorizing all the sites using the same account?

    I will check the Errors & Debug screen before re-authorization the next time I see it.

    No, we are not authorizing all the sites using the same account.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘On last Update, plugin disconnected and stopped tracking in GA’ is closed to new replies.