Keyword Planning -- Geo Modifiers Limitation

[Reid Hommedahl]

I'm currently working with the python client library and using the Keyword Forecasting tool to estimate performance for different locations. However, I’ve run into an issue with geo targeting, and adding more than one geo_target_constant at a time.

What I’m Trying to Do

• I need to forecast keyword performance across 1,000+ ZIP codes.
• Each ZIP code has a corresponding Geo Target Constant.
• My current approach creates one campaign forecast per ZIP code, but this quickly exceeds API quota limits (error 429: "Resource has been exhausted").

The Problem

• The geo_modifiers[] field in criterion_bid_modifier seems to only allows one location ID per campaign.
• This means I have to make 1,000+ separate API calls, which isn’t scalable.

In the documentation example, only one geo_target_constant is added to the forecasting campaign:
https://developers.google.com/google-ads/api/docs/keyword-planning/generate-forecast-metrics

Is there a way to include multiple ZIP codes in a single forecast campaign? Or maybe some way to do batch-processing? 

Thank you!

[Google Ads API Forum Advisor]

Hi,

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

As per provided information, I understand that you are facing issues with geo targeting, and adding more than one geo_target_constant to campaign forecast. Please note that the geo_modifiers field indicates that the location to be targeted and the locations must be unique when targeting the forecast campaign. To assist you further, Could you please confirm whether you are adding ZIP codes at campaign level or at ad group level? Additionally, Please provide the complete API logs (request and response with request-id and request header) that containing how you target the single ZIP code to the forecast campaign?

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.

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-02-20 06:32:15Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH2hV:ref" (ADR-00288937)