How to identify expensive reports now

[Hisashi Hayashi]

I have a question regarding the following document.
https://ads-developers.googleblog.com/2024/05/google-ads-api-resource-usage-policy.html

I tried multiple query patterns, but query_resource_consumption allways returned zero.

Does this mean these queries will not be throttled after June 17, 2024?
Or does query_resource_consumption always returns zero until June 17, 2024?

Regards

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

Kindly note that in order to manage API resource usage, Google throttles query patterns that consume excessive resources in GoogleAdsService.Search and GoogleAdsService.SearchStream. This throttling only affects the specific query pattern, allowing other services, methods, and query patterns to function normally. Starting from June 17, 2024, requests using throttled query patterns will experience the following changes:

• For API versions v16 or older, you'll receive a "QuotaError.RESOURCE_EXHAUSTED" error.
• For API versions v17 or later, you'll receive either a "QuotaError.EXCESSIVE_SHORT_TERM_QUERY_RESOURCE_CONSUMPTION" or "QuotaError.EXCESSIVE_LONG_TERM_QUERY_RESOURCE_CONSUMPTION" error, depending on whether the excessive resource consumption occurred over a short period (a few minutes) or a long period of time.

In order to assist you further, kindly provide us with the complete API logs (request and response logs with request-id and request header) generated at your end and uncropped UI screenshot of the Google Ads account where you are facing the issue.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

​​​​​​​You can send the details via Reply privately to the author option, or direct private reply to this email.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02tIvvf:ref" (ADR-00234370)

Thanks,
 

Google Ads API Team

[Hisashi Hayashi]

Hi,

I would like to know how to identify expensive queries right now.

I manage tens of thousands of accounts, and each account runs multiple queries every day.
If there are any expensive queries, errors may occur frequently after June 17th.
To avoid this, I would like to know in advance whether each query would be throttled.

Therefore, I checked query_resource_consumption, but it was all zero, so I couldn't tell if there was a problem.

Regards

2024年5月10日金曜日 7:59:16 UTC+9 Google Ads API Forum Advisor:

[Google Ads API Forum Advisor]

Hi,

As requested earlier, in order to investigate why the query_resource_consumption is returning zero, provide us with the complete API logs (request and response logs with request-id and request header) generated at your end.