Not being able to request historical data for keywords because we are limited to have 10,000 keywordPlans

[Junhyung Ki]

Recently we migrated the process from using AdWords to GoogleAds api as AdWords is sunsetting by the end of next month.

Previously, we could directly get the keywords search volume data from Google
but now we first ask Google to create and give us a keywordPlan then we associate the keywords to the keywordPlan and send it back to Google to get the keywords search volume data. (as exampled here: https://developers.google.com/google-ads/api/docs/keyword-planning/generate-historical-metrics)

The problem started appearing from early this morning and we are not able to get search volume data from Google because we have exceeded 10,000 keywordPlans
and the limit is 10,000 per customer.

--------------------------------------------------------------------------------------------------------- error_code { resource_count_limit_exceeded_error: RESOURCE_LIMIT } message: "This request would exceed a limit on the number of allowed resources. The details of which type of limit was exceeded will eventually be returned in ErrorDetails." trigger { string_value: "ENABLED_KP_PLANS_PER_USER_PER_CUSTOMER" } location { field_path_elements { field_name: "operations" index: 0 } } details { resource_count_details { enclosing_id: "200947807" limit: 10000 limit_type: KEYWORD_PLANS_PER_USER_PER_CUSTOMER existing_count: 10000 enclosing_resource: "customer" } } ---------------------------------------------------------------------------------------------------------

My summary would be:

We are updating historical data for keywords on a regular basis and every time we update them we create a new keywordPlan and we've finally reached a point where we are no longer able to create a new keywordPlan as we are limited to have 10000 keywordPlans per customer.

How can we get this data without creating a keywordPlan then? the example (https://developers.google.com/google-ads/api/docs/keyword-planning/generate-historical-metrics) only shows the way with creating a keywordPlan. Please let me know.

[Ashly Suma Varghese]

We are also facing this similar issue. Was there any work around that you found to resolve the issue? Please advise.

Thanks in advance.

[Ashly Suma Varghese]

Thanks Ernie for this.

We will give this solution a try. Thanks alot. Have a nice day.

Thanks,

Ashly

On Tue, Mar 29, 2022 at 7:59 AM Google Ads API Direct Support <googleadsa...@google.com> wrote:

Hi Ashly,

Thank you for following up. I would like to reiterate the response of my colleague below to this concern:
"Thank you for reaching out to us.

Since you have encountered resource_count_limit_exceeded_error: RESOURCE_LIMIT error, it means that this request would exceed a limit on the number of allowed resources. The details of which type of limit was exceeded will eventually be returned in ErrorDetails.

Since the logs returned the ENABLED_KP_PLANS_PER_USER_PER_CUSTOMER, then this indicates that you may have exceeded the limit of enabled keyword plans you can create within a single account. You can also check this guide as reference for the keyword plan limits per account.

It should also be possible to remove plans if the limit is reached. You can try and use the KeywordPlanOperation to remove on a keyword plan."

Let me know if you have questions with the suggestion provided by my colleague.

Regards,

Ernie John Google Ads API Team

ref:_00D1U1174p._5004Q2YrUYj:ref

[sudarshan gowda]

Hi, we are also facing a similar issue. Basically, we are using google ads API to get historical data for the keywords.  Now we have reached the 10,000 limits and want to remove the limit. Does the above solution works? If yes, could you please provide me the code snippet for the reference? That would be appreciated because we are quite confused about how and where to use "KeywordPlanOperation"? We created a loop to get the historical data for 10,000 keywords. Thanks in advance. 

[Parth Vallabhdas Makadiya]

As far as I know the limit per request is 10000 and you have 10000 req per day. So I think you need to optimise how you call.