Google Ads API Resource Usage Policy Update

What's changing?

We are updating nan Google Ads API assets usage argumentation to throttle GoogleAdsService.Search and GoogleAdsService.SearchStream query patterns that devour excessive amounts of API resources. If a peculiar query shape is throttled, different services, methods, and query patterns will proceed to activity unaffected.

Starting nan week of June 17, 2024, and only for nan throttled query patterns, requests will beryllium affected arsenic follows:

• If you usage type v16 aliases older of nan API, you will person a QuotaError.RESOURCE_TEMPORARILY_EXHAUSTED error.
• If you usage type v17 aliases later of nan API, you will person a QuotaError.EXCESSIVE_SHORT_TERM_QUERY_RESOURCE_CONSUMPTION aliases QuotaError.EXCESSIVE_LONG_TERM_QUERY_RESOURCE_CONSUMPTION, depending connected whether nan excessive assets depletion was for a short play of clip (a fewer minutes), aliases a agelong play of time.

To thief you place and show your costly reports, we will besides return a costs metric for individual reports. To position nan costs for successful reports, spot nan pursuing fields:

• SearchGoogleAdsResponse.query_resource_consumption section erstwhile moving reports utilizing GoogleAdsService.Search method.
• SearchGoogleAdsStreamResponse.query_resource_consumption section erstwhile moving reports utilizing nan GoogleAdsService.SearchStream method.

Why this change?

We are making this alteration to sphere nan reliability and stableness of nan API.

What do I request to do?

Before June 17, 2024, update your applications to do nan following:

• Handle nan caller correction codes erstwhile making GoogleAdsService::Search aliases GoogleAdsService::SearchStream calls
  • If you usage type v16 aliases earlier of nan Google Ads API, past grip QuotaError.RESOURCE_TEMPORARILY_EXHAUSTED errors.
  • If you usage type v17 aliases later of nan API, grip nan QuotaError.EXCESSIVE_SHORT_TERM_QUERY_RESOURCE_CONSUMPTION and QuotaError.EXCESSIVE_LONG_TERM_QUERY_RESOURCE_CONSUMPTION errors.
  • If 1 aliases much of your reporting query patterns are throttled, you should reappraisal and hole nan query pattern. Here are immoderate ways to amended query performance:
  • Run nan query little frequently.
  • Use a little costly query shape aliases view.

To study much astir optimizing your queries, spot manage information efficiency.

• [Optional] Incorporate nan caller query_resource_consumption metric into your monitoring systems to observe and grip caller costly queries.

How to get help

If you person immoderate questions astir this alteration aliases request thief optimizing circumstantial query patterns, cheque retired nan Google Ads API support page for options.