GenerateHistoricalMetrics API Limits and Quotas and RESOURCE_EXHAUSTED errors

335 views
Skip to first unread message

Yusuf Coskun

unread,
Jun 8, 2022, 6:02:19 PM6/8/22
to Google Ads API and AdWords API Forum
Hi,

We have a tool that generates localized keyword suggestions to our clients based on historical search volumes. For that purpose we have been fetching historical metrics for ~3000 keywords on ~700 cities within US. And we have been doing this on a monthly basis. Up until last month we have been using adwords api without any problems and it was taking only a day to complete these requests.

We migrated to Google Ads API v10 and followed this guide to generate historical metrics. But we are struggling to make this work with the new API. We designed our app to create one KeywordPlan, one KeywordPlanCampaign and one KeywordPlanAdGroup for each city we are targeting (~700 cities) and create ~3000 KeywordPlanAdGroupKeyword under every KeywordPlan. However, without any luck, for the past week we haven't been able to successfully create all 3K  keywords for not even a single keyword plan. Everytime we make the api call for creating KeywordPlanAdGroupKeyword with 3000 create operations we got a RESOURCE_EXHAUSTED error.

I am aware of the Planning Service specific limitations explained here and we are putting a 2 seconds delay between each request to adhere the 1 QPS requirement. Basically our app makes;
1 mutate request for creating 700 KeywordPlans
1 search request for fetching the KeywordPlans
1 mutate request for creating 700 KeywordPlanCampaigns
1 search request for fetching the KeywordPlanCampaigns
1 mutate request for creating 700 KeywordPlanAdGroups
1 search request for fetching the KeywordPlanAdGroups
700 mutate requests for creating 3000 KeywordPlanAdGroupKeywords under each KaywordPlanAdGroup.

Once again I want to emphasize that we are explicitly putting a 2 seconds delay between each request but nevertheless we are getting RESOURCE_EXHAUSTED error on the first mutate request for creating the KeywordPlanAdGroupKeywords.

I would think that we are hitting the 15K daily api operations limit as described in here
but I would expect this to happen after the 4th mutate request to create KeywordPlanAdGroupKeywords.

So my question is that what other rate/quota we are hitting here? What is the point that we are missing?

Finally, I would like to say that; this whole process of generating historical metrics along with 15K daily operations limit seems totally useless. A single keyword plan can have up to 10K keywords but we can make 15K operations per day with basic access level. This just doesn't makes sense.

As described here an account can have 10K KeywordPlans and each KeywordPlan can have 10K keywords. In order to fully utilize these limits ~100M api operations are required and with 15K daily operations it takes ~18 years to accomplish this with basic access level.

I really believe that I am missing something here and I would appreciate any help to know what it is.

Thank you.


Google Ads API Forum Advisor

unread,
Jun 8, 2022, 10:58:43 PM6/8/22
to yu...@winnowpro.com, adwor...@googlegroups.com
Hi Yusuf,

Thank you for reaching the Google Ads API support team. I am Sherwin and I hope that you are doing well today.

To further help you with your concern why you still get the "Resource_Exhausted" error, could you please provide us the complete and recent request and response logs with request ID and request header generated on your end? You can provide it via the Reply privately to author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

Regarding this concern "In order to fully utilize these limits ~100M api operations are required and with 15K daily operations it takes ~18 years to accomplish this with basic access level". I would recommend you to apply for Standard access because this allows the developer token to execute an unlimited number of operations per day for most services.

Best regards,
Google Logo
Sherwin Vincent
Google Ads API Team
 


ref:_00D1U1174p._5004Q2bdmzF:ref
Reply all
Reply to author
Forward
0 new messages