Re: keyword planner suddenly throws error

2024-10-01 Thread 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
Panu: I don't know to what this refers. We have resolved the issue for this case. Please, open a new case with your details. This message is in relation to case "ref:!00D1U01174p.!5004Q02vEQ5U:ref" (ADR-00260556) Thanks, Bob Hancock Google Ads API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Re: keyword planner suddenly throws error

2024-10-01 Thread Panu Kuuluvainen
Hi Matt Thanks for your response. Not sure why keyword data for the date range I was trying wouldn't exist yet but you are probably right about the cause. So weirdly - yesterday dates '2024-10-02' to '2024-10-31' resulted in an error - if I pushed the forecasting period to '2024-10-

Re: keyword planner suddenly throws error

2024-10-01 Thread Matt Dworkin
Hey Panu, You're likely getting the error because keyword data for your date range doesn't exist yet. That was the problem for me. Best, Matt On Tuesday, October 1, 2024 at 8:42:05 AM UTC-4 Google Ads API Forum Advisor wrote: > Panu: > > I don't know to what this refers. We have resolved the

Re: keyword planner suddenly throws error

2024-09-30 Thread Panu Kuuluvainen
Period request.forecast_period.start_date PyDev console: starting. '2024-10-02' request.forecast_period.end_date '2024-10-31' Throws that error. If I use a slightly different timeframe like request.forecast_period.start_date '2024-10-21' request.forecast_period.end_date '2024-11-20' it works

Re: keyword planner suddenly throws error

2024-09-30 Thread Panu Kuuluvainen
Hi I have the same issue, getting INVALID VALUE in code that worked before. campaign_to_forecast PyDev console: starting. language_constants: "languageConstants/1011" geo_modifiers { geo_target_constant: "geoTargetConstants/2246" } keyword_plan_network: GOOGLE_SEARCH bidding_strategy { manua

Keyword Planner Suddenly Throws Error

2024-08-01 Thread Matt Dworkin
Hello, We've been using keyword planner via for a while, and today it randomly stopped working for our employees. Our look back date was 2024-07 (start) - 2024-08 (end). If we expand the look back to a few months ago, it seems to work. We get the following error: Failure: {"errors":[{"error