Common Errors and Suggested Actions

  • This page provides examples of common AdMob API errors and tips for preventing and resolving them.

  • Errors are categorized by error code (e.g., 400, 401, 403, 429) and include detailed messages and troubleshooting steps.

  • Common issues include invalid arguments, authentication failures, permission issues, and exceeding quota limits.

  • Refer to the Google API Error Model and the provided links for further guidance on error handling.

This page lists examples of common errors and provides tips on preventing and handling them. See the Google API Error Model for additional guidance.

Error Code
400
Invalid Argument

Message
Invalid account information in request url: 'accounts/pub-XXXXXXXXXXXXXXXX'

Details
Replace pub-XXXXXXXXXXXXXXXX with your publisher ID, see the instructions to find your publisher ID.
Invalid Argument

Message
Cannot request more than 100,000 rows in one report request.

Details
Change the max_report_rows field to a value from 1 to 100,000, inclusive.
Invalid Argument

Message
Requested metrics and dimensions are incompatible.

Details
Visit the reference documentation to determine which metrics and dimensions are incompatible for both network and mediation reports.
401
Unauthorized

Message
Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.

Details
The access token is not authorized for the following account. Follow the steps on the getting started page to complete authentication. Ensure that you are signed in to the correct account with the required user roles when accepting the consent screen.
403
Permission Denied

Message
AdMob API has not been used in project XXXXXXXXXXXX before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/admob.googleapis.com/overview?project=XXXXXXXXXXXX then retry.

Details
Access to the specified resource was denied. This commonly occurs when the AdMob API is not enabled for your project. Visit the Google Cloud Console to enable the AdMob API.
Access Denied

Message
The requested resource is not accessible to the effective user

Details
Access to the specified resource was denied for the effective user. To learn more on user roles and to check permissions, please see the following new user roles article.
429
Resource Exhausted

Message
Quota exceeded for quota group 'ReportingReadGroup' and limit 'Reporting read requests per user per 100 seconds' of service 'admob.googleapis.com' for consumer 'project_number:XXXXXXXXXXXX'.

Details
The quota limits have been exceeded. Visit the Quota page to understand the quota limits.