Authorising the widget

  • Resolved adejones

    (@adejones)


    1 year, 11 months ago

    Hi guys, love the plugin and have been using it for years since a previous version/plugin got too big for its boots.

    I currently have this installed on around 230 websites, and needless to say I am being continuously asked to re-authorise the widget for various customers and I have assured them all that this is out of my hands but I am happy to do so on their request, however I am getting a bit tired of it and looking for solutions, so I have been doing a bit of trial and error.

    In my analytics dashboard I currently have around 30-40 sites per ‘analytics account’ i.e. clients #1 has 30-40 properties, clients #2 has 30-40 properties, clients #3 has 30-40 properties

    I saw your post here: https://deconf.com/error-refreshing-the-oauth2-token-message-error-invalid_grant/ and where it talks about 25 refresh tokens per account, I assumed it meant per ‘analytics account’ within the same Google account hence why I split my sites between multiple ‘analytics accounts’ (confused?) – however, I put one site on it’s own ‘analytics account’ within the same Google account as all the others and it unlinked after just 13 days, if my thinking was correct then it should never have expired because it was on its own with no other sites/properties in that account being authorised.

    So am I right in assuming that when you talk about account, you mean Google account and not just an ‘analytics account’?

    In which case, the way round this for me would be the long winded way of creating several @gmail.com accounts (i.e. [email protected], [email protected]) then put 25 sites within each analytics dashboard?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Alin Marcu

    (@deconf)

    So am I right in assuming that when you talk about account, you mean Google account and not just an ‘analytics account’?

    Unfortunately I’m talking about Google Accounts. The only way around I know is creating multiple API Projects, also described on the tutorial.

    Plugin Author Alin Marcu

    (@deconf)

    So am I right in assuming that when you talk about account, you mean Google account and not just an ‘analytics account’?

    Unfortunately I’m talking about Google Accounts. Another option would be creating multiple API Projects, also described on the tutorial you’ve mentioned or letting users authorize with their own accounts.

    Thread Starter adejones

    (@adejones)

    Thanks for the reply, it is so confusing when the articles all talk about Accounts because it is not clear whether it means Google account or ‘accounts’ within the analytics dashboard so thanks for clarifying.

    OK I have a new customer so I have created a new email address, and created a new google analytics account using that, so are you saying that I can now put 25 websites within that new google account and they shouldn’t ever need re-authorising?

    Plugin Author Alin Marcu

    (@deconf)

    Well, theoretically yes, practically no. Here’s why. For example, let’s say you authorize 25 websites, and at some point for a random reason you decide to delete the plugin on a few sites, not uninstall it. At this point, when you reauthorize again, you already have 25 refresh tokens issued and each site you reauthorize will start to invalidate older refresh tokens. It’s just an example, but there are few case scenarios that could generate this issue.

    Thread Starter adejones

    (@adejones)

    OK thanks, so if I load up 25 sites on to the new Google account, but if any of those 25 customers ever cancel their services with me then the trick would be not to replace their analytics property with another, that way after the initial 25 authorisations there should never be another, and the number of properties would only go from 25 downwards and never have any replacement properties.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Authorising the widget’ is closed to new replies.