Quotas

AI-generated Key Takeaways

• Quotas are in place to protect Google's infrastructure and ensure fair usage of the AdMob API for all users.

• Account, inventory, and reporting methods have separate quota limits, with varying allowances per minute and per day.

• When encountering quota errors despite staying within listed limits, implement client-side rate limiting and reduce the data volume of each request.

• Users exceeding the default quota limits can request an increase via the AdMob API Developer Forum, providing a clear description of their use case.

Quotas protect Google's infrastructure from processes that use the AdMob API in an inappropriate way. They ensure that individual actions cannot negatively impact the larger community.

Quota limits

The following table outlines each quota limit for the AdMob API. Note that quota limits apply to account, inventory, and reporting methods separately.

Key Point: There are additional back-end processing cost caps. When experiencing quota errors, such as 429 RESOURCE_EXHAUSTED, and your quotas are within the table below, the recommendation is to introduce client-side rate limiting as well as requesting fewer rows per request. The latter can be achieved by reducing the date range of your request and the number of dimensions.

Quota Description	Quota Limit
Account read requests per minute per project	900
Inventory read requests per minute per project	120
Inventory read requests per day per project	172800
Reporting read requests per minute per project	900

Follow the instructions for additional information on your quota limits.

Requests for additional daily quota

If you require more quota than the limit, reach out to us on the AdMob API Developer Forum and describe your use case.