403 rateLimitExceeded error?

[J]

I've noticed that the reporting API will return "rateLimitExceeded" (403 error code) throughout the day even though my application is nowhere near the quota limits.  

Here's the error:

[{"domain":"global","message":"Quota Error: Rate Limit Exceeded","reason":"rateLimitExceeded"}]

BTW, I don't see "rateLimitExceeded" on the reference page for errors: https://developers.google.com/analytics/devguides/reporting/core/v3/coreErrors

More recently, this error seems to occurring more and more frequently, which is causing a big problem for our application/system.

Can someone explain why we are receiving this error?  Any remedies?

Any help would be greatly appreciated.  Thanks!

[Jeetendra S.]

You are likely hitting the 10 QPS/IP limit. You just need to lower the rate at which you're sending your requests. Consider implementing some kind of exponential back-off for example.

You can read more on this in our quota policies.

https://developers.google.com/analytics/devguides/reporting/core/v3/limits-quotas

[Jamie Tsao]

Hi Jeetendra,

Thanks for your response.  According to the documentation, if our application uses the "userIp" or "quotaUser" parameter, then the 10 QPS is effectively applied PER USER.  If this is the case, there's no way we are sending even close to 10 queries per second PER USER.  Our application is designed to fetch data per profile at regularly spaced intervals.  Upon each successful report query, we process the data on our side before making another query so there's no way we can do 10 queries in a second (per user, that is).  

Here's the documentation I'm referring to:

• 10 queries per second (QPS) per IP.
  • In the APIs Console this quota is referred to as the per-user limit. By default, it is set to 1 query per second (QPS) and can be adjusted in the Quotas pane to a maximum value of 10. If the per-user limit is set to a value larger than 10 QPS, the Google Analytics quota policy will still take effect and limit per-user requests to 10 QPS.
  • If your application makes all API requests from a single IP address (i.e. on behalf of your users) you should consider using the userIP or quotaUserparameters with each request to get full QPS quota for each user. See the query parameters summary for details.

In addition, we have a backoff strategy anytime we encounter a 403 quota error.  We've seen incidences where a particular GA user/profile will get this 403 quota error 5 straight times, with each call being spaced out by more than 1 hour (incrementally more spaced based on backoff strategy).

Is there a way you can look specifically into the requests being made from our application, and find out what's wrong?  I believe we are following the proper protocol.

Thanks,

Jamie

--
You received this message because you are subscribed to a topic in the Google Groups "Google Analytics Reporting API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-analytics-data-export-api/ZkDPmejHNFw/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-analytics-data-...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
SumAll
Jamie Tsao

ja...@sumall.com

sumall.com

[Jamie Tsao]

Hi Jeetendra,

Could you provide further assistance?  These quota errors continue to occur and we're unsure about how to prevent them as we believe we're using the "quotaUser" param properly.

Any help would be appreciated.

Thanks,

J

[Jamie Tsao]

Can anyone from the GA team look into this issue?

We are well below our overall quota and we're using the "quotaUser" param which should put us well below the 10 QPS (per user) limitation as well.  I don't understand why we're getting these error throughout the day.  We've been getting this error over 3K a day.

Any help would be appreciated.

[Jamie Tsao]

Sorry to keep bumping this, but we continue to get over 3K quota errors every day, so it would be great if someone could provide some insight.

Either "quotaUser" param is not working as advertised or we're using it incorrectly.  

Please help!

[Cesar Del Solar]

Did you ever figure this out? We are also using quotaUser and it doesn't seem to be working properly (or I'm not using it properly?)

Please help!

J

To unsubscribe from this group and all its topics, send an email to google-analytics-data-export-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
SumAll
Jamie Tsao

ja...@sumall.com

sumall.com

--
SumAll
Jamie Tsao

ja...@sumall.com

sumall.com

--
SumAll
Jamie Tsao

ja...@sumall.com

sumall.com