Rate Limits on Test vs Production accounts

[andrew....@sigla.io]

We are testing using a Google Ads Test account and have been running into the rate limit often with our standard access api key.  From reading other posts on this site and the AdWords documentation I've heard that production accounts with ads running have higher rate limits than test accounts. How much higher are the limits on active production accounts?

[Milind Sankeshware (AdWords API Team)]

Hi Andrew,

Unfortunately, we cannot comment on exact limits for an established production account. The standard access allows the developer token to execute an unlimited number of operations and report requests per day. Please note that the new AdWords account may have a significantly more restrictive rate limit (i.e., lower QPS) than established accounts. For more information please refer to this guide. Let me know if you have any further questions.

Thanks,
Milind, AdWords API Team

[andrew....@sigla.io]

Are you unable to give even an approximate estimate?  The guide you linked to recommends using different rate limiters for different account types.  How can we be expected to estimate the needs of these rate limiters without knowing where our targets are?

Thanks,

Andrew Ellison

[Milind Sankeshware (AdWords API Team)]

Hi Andrew

AdWords API uses a Token Bucket algorithm to meter the requests and determine the queries per second (QPS) rate. This is intended to prevent malicious or out-of-control software from overwhelming the AdWords API servers and affecting other users. The rate limits can fluctuate based on different variables, including server load. Hence, we don't recommend a fixed Queries Per Second (QPS) limit. It's extremely important to understand how to handle RateExceededError, and develop your software with rate limits in mind. Our recommendation is to check the throttling mechanisms suggested in the guide to control and handle the rate limit errors.

It is possible to keep a track of the operational limits (with DEVELOPER scope). You will be able to calculate the API operations using the guidelines provided here. The rate limit with ACCOUNT scope, can only be handled by slowing down.