This report is unavailable (400)

Hi,

The plugin needs to be network activated to have/use those settings.

What does that mean and how do I do that?

My fault, I thought you’re talking about a multisite install, since you were mentioning a Network feature. That’s a WordPress multisite feature, so it doesn’t apply when you have multiple independent websites (with single installs).

There are some solutions to overcome the limitation but it really depends on each use case (how the “network” is organized and other particularities).

I have 100 independent WordPress installations — all on the same dedicated server and all in the same Google Analytics account. Anyway to make this work so I don’t have to reauthorize the plugin every few days?

Having the same issue here – I have around 100 independent WP installations as well, all on the same dedicated server and in the same Google Analytics account. Every time I log in, each site seems to have the 400 error and I have to re-authorize. Any solutions to this would be appreciated!

As I said above, you need to give details about your use case:

1. Are those sites yours? Are you an agency building/managing sites for clients?
3. Describe your business model.

Depending on your business model, there are different solutions or none.

how the “network” is organized and other particularities

by “network” I meant “your business model”, sorry for the confusion.

My site has suddenly got the same issue:

This report is unavailable (400)

What can I do? Can i send an email to you Alin if you need the information? That would be great….

Thanks,

Ive got a load of “Errors & Details”? i can send that to you…..10 errors there?

Well, if it suddenly stopped it’s probably not because of the plugin, right?

If you don’t post the error no one is going to help you, because no one will know the cause.

Start by checking the plugin’s FAQ page and documentation and if you can’t solve it yourself, open a new topic and give details.

Posting on other topics, unrelated to your issue, is considered rude around here.

Hi Alin,
Thanks for your patience with us users – I know support is frustrating!

If it helps, we run a dedicated server with multiple WordPress sites for our clients, we have a maintenance contract with them to keep everything up to date and secure – sites belong to the client but we do all updates and ensure everything is working for them. 9 times out of ten your plugin has the 400 error and I have to reauthorize it when I login every month. Analytics for our clients are all setup within one account, there are 100 clients in this account – this account is the one that keeps getting disconnected and requiring re-authorization. 100 is the max that Google allows in an account, we have a second account with only about 20 clients in it so far, and these seem to be staying authorized without any issues.

Let me know if you need any additional information. Thank you for the help!

@rich99 – If you’ve only got the 400 error once, it is not the same issue – you likely just need to reauthorize with Google to fix – clear authorization and then get the token key again – easy fix.

@imagedesign, basically the restriction is 25 refresh tokens for the same Client/Account pair.

Start by reading this: https://developers.google.com/identity/protocols/OAuth2#expiration

Here are some options:

• Let your clients have their own Google Accounts. They will authorize the plugin using their own account. And if you also need access to their analytics data (maintenance, or other contractual stuff) they can share the Properties/Views using the User Management feature from Google Analytics.
• Create four API Projects, and authorize 25 views per project. Unfortunately the realtime component won’t work without access to Realtime API enabled on each project, see:
  https://developers.google.com/analytics/devguides/reporting/realtime/v3/. Also consider that there is a “larger limit” on the total number of tokens a user account can have across all clients.
• Use five accounts with 25 Properties / account.

I would go for option one, is the safest and it can’t get affected by the number of allowed tokens, which is subject to change. It was never changed (AFAIK), but it may.

@imagedesign – thanks, i will have alook at that, cheers!

@alin Marcu – blimey i wasnt trying to be rude at all! Same error really, thought it was easier to merge them together instead of tons of same topits, oh er missus. If i cant get it to fix i will start a new topic, messgae heard! ??