Limit to number of sites – older sites get de-registered

@shaunbowen You are correct that this is an OAuth limitation, not specific to Site Kit.

The majority of Site Kit users are not reaching the OAuth limitations, and as you can imagine the OAuth restrictions are in place to mitigate any potential risk or abuse.

If you are a developer or working with many multiple WordPress sites you can follow some of the suggestions as per this WordPress support topic. You’ll see a workaround suggesting providing clients access to a property, allowing them to initially setup and authenticate via Site Kit.

I’ll be sure to pass on your feedback with the team this week.

Hi James, yes I thought this would be the reason.

Obviously there should be measures in place to prevent risk and abuse, but the max “refresh token limit” should be EQUAL to the max number of properties available to a single Analytics account.

I don’t much fancy migrating 200+ analytics properties to new user accounts, as the 2 factor authentication process is already time consuming for just a single account!

Can you tell me if the Analytics data is still gathered regardless of whether the refresh token is working or not?

@shaunbowen As long as you have placed the Analytics code on your side then yes, Analytics is gathering data. The tokens are used only to authenticate the OAuth application used for Site Kit with your site.

Well that’s the question – I won’t place the analytics code manually in the header, as Site Kit adds this for me. No point in adding it twice.

So are you saying the de-authorisation will remove the UA code from the header and footer?

@shaunbowen Apologies, if an access token expires the code snippet added by Site Kit remains on your site unless removed. No data will be lost, and data will be collected. You’ll just need to re-authenticate if you wish to continue using the Analytics module within Site Kit.

Ah, good, I was hoping that would be the case. I’m safe to leave Site Kit installed on sites, regardless then – I just have to hope the folks in the Analytics department of Google can increase the number of OAuth tokens allowed.

Hi @shaunbowen. While I’ll be brining this up with the team you can also use the Analytics feedback feature to leave comments raising the limitations.