Re: KeywordPlanService.GenerateHistoricalMetricsRequest only returns GLOBAL results

[Lasse Bonner]

Btw, I have implemented the code following this guide: https://developers.google.com/google-ads/api/docs/keyword-planning/generate-historical-metrics?hl=en#create_a_keyword_plan.

On Thursday, May 19, 2022 at 4:06:05 PM UTC+2 Lasse Bonner wrote:

Hello, 

I am using Google Ads API v10.1 and I am creating a keyword plan with a campaign with a geotarget. The results returned by KeywordPlanService.GenerateHistoricalMetricsRequest for the given keywords and geotarget return global results only. I am expecting this to be an error, as it has been running without any issues for the last couple of months. 

For now I have reverted to using the old Google Adwords API, but as you probably know is already in sunset mode.

I have attached request logs for the entire flow of my api. To show you the problem I have attached a request containing the danish words "rød grød med fløde" and with geotargets for both Denmark and Portugal. It shows the same search volume data for both locations. 

Looking forward to hearing from you,

Best regards

Lasse Bonner

[Google Ads API Forum Advisor]

Hi Lasse,

Thank you for bringing this to our attention, I raised it with my team and we will get back to you as soon as possible. I am reposting your first post in a  redacted fashion because it contains logs :

Hello, 


I am using Google Ads API v10.1 and I am creating a keyword plan with a campaign with a geotarget. The results returned by KeywordPlanService.GenerateHistoricalMetricsRequest for the given keywords and geotarget return global results only. I am expecting this to be an error, as it has been running without any issues for the last couple of months. 
For now I have reverted to using the old Google Adwords API, but as you probably know is already in sunset mode.

I have attached request logs for the entire flow of my api. To show you the problem I have attached a request containing the danish words "rød grød med fløde" and with geotargets for both Denmark and Portugal. It shows the same search volume data for both locations. 


Looking forward to hearing from you,

Best regards
Lasse Bonner

Regards,

Aryeh Google Ads API Team

ref:_00D1U1174p._5004Q2YbrjF:ref

[Alexey Stupenkov]

Hello,

I have the same problem when i send requests to GenerateHistoricalMetricsRequest
In the results only global results, no matter what location is set.
Checked on versions V10 and V9.

Best regards,

Alexey Stupenkov

[Alex]

I am getting same problem on v9 and v10 incredibly annoying when trying to do work.

[Marek Rost]

Hello,

I am experiencing exactly the same issue. Historical metrics are ignoring Geotarget location from the Keyword plan and provide only global data.

Additionally to v9 and v10, I have used v8 API. Same results.

I would like to add that the issue started occurring somewhen after 2022-05-17 23:15 UTC+0 and before 2022-05-19 12:15 UTC+0 .

Aryeh, could you please get us some approximate timeline on this? What would be your skeptical estimate?

I'm postponing moving to AdWords API due to the fact there are only yearly averages available in it.

[Audrey Arndt]

Hello,

We're also facing the same issue and running up against the clock for the switch to Ads from Adwords while this issue is ongoing. Any timeline on a fix is appreciated.

Thanks!

[Anthony K GROSS]

Hi there,

We are also facing to this problem. We did v9 or v10, from google-ads on Python and via REST directly : same issue : generate_historical_metrics doesn't care about geo_constant_target, network, ... and return metrics without any parameters except Keywords. Even previewing the keyword_plan on Google Ads Dashboard let it crash.
Please, can you give us a any timeline to fix this issue ?

Thanks bros !

[Google Ads API Forum Advisor]

Hello Anthony, Marek, Lasse,

We're investigating this. Unfortunately, I cannot give any timelines right now, but I'll keep you informed once I hear more new information.

Best,
Thanet, Google Ads API Team

ref:_00D1U1174p._5004Q2YbrjF:ref

[Rutger Heijmerikx]

Wow, I've spent HOURS investigating this. The new API having this issue on this after multiple versions is beyond my understanding. Figures why I only discovered this just now.

I've implemented the new API way ahead of time before the old one was end of life,  thinking it would save a lot of stress. I'm throwing in some keywords here for others to find this post.

Adding geoTargets or languageConstants at the KeywordPlanCampaign API call, for retrieving HistoricalMetrics using generateHistoricalMetrics does not have any effect on searchvolume information.

[synibleworkers]

This is a major issue, which needs to get fixed this week before the Adwords API goes completely offline, otherwise there is no way to get search volume stats. Whoever has power here, please let the API developers know how urgent this is. 

[Google Ads API Forum Advisor]

Hello,

We're working on that. We'll immediately update this thread once we have update.

[zulm...@mail.com]

Sorry, but this is getting weird, it's already been a week to fix what was broken in just one day...
Don't want to offend anyone, but are you sure everything is ok?

Thanks!

[Google Ads API Forum Advisor]

Hello,

I'm sorry for your inconvenience.
We're working on fixing it. If I have new information to share, I'll immediately update this thread.

[Ahmed Amir]

Hello,

One more message to share our astonishment to see this problem taking so long to be corrected.

We hope for a quick fix.

Thanks,

[Richard Pergament]

Hi, just want to chip in that this is also a mission critical problem for us.

Best regards,

Richard Pergament

[Alexey]

Dear Google Ads API Team,

maybe you need help fixing a bug?

Our team is ready to help.

Just let me know.

Best regards,

Alexey.

[Marek Rost]

Dear Ads API team,

we are quickly approaching 14 days with absolutely no information except reassurances that you're "working on it".

Can we at least assume that in light of this - apparently serious and difficult to fix issue - the sunset of Google AdWords API will be postponed and you will NOT hit us with 50% failure rate on all API requests starting tomorrow? (Related blog post in Ads Developer blog:  https://ads-developers.googleblog.com/2022/05/adwords-api-has-officially-sunset.html )

[Mehmet Kocak]

Der Google Ads API Team,

The API ignores not only the GEO & Location targets but also the "keyword_plan_network" ( https://developers.google.com/google-ads/api/reference/rpc/v10/KeywordPlanNetworkEnum.KeywordPlanNetwork ). 

So no Matter if you use "GOOGLE_SEARCH" or "GOOGLE_SEARCH_AND_PARTNERS" you get always search volume refers to "google and partner".

Best regards,
Mehmet

[Google Ads API Forum Advisor]

Hello All,

Sorry for keeping you waiting for many days. The issue should be fixed now. Could you please retry your requests to see if it works? If it doesn't, please Reply privately to author and attach your requests and responses. If the issue is not related to the geo targets set at the campaign level, please create a separate post, so we can track it better. 
Again, I'm sorry for your inconvenience.

Best,
Thanet, Google Ads API Team

ref:_00D1U1174p._5004Q2YbrjF:ref

[Jeff Reuter]

The issue still persists for me.

[Google Ads API Forum Advisor]

Hi Lukas,

Thank you for the reply.

Since you insist that the issue still persists on your end, could you provide more details of it so our team can further investigate it? Also, you may note that we have a new guide for this behavior, you can check this documentation for more details.

Best regards,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2YbrjF:ref