Hi,
Thanks for reaching out to the Google Ads API Forum.
I understand that you were able to retrieve historical info for keywords plan via Google Ads API but the response shows it as response.metrics == []. Can you please confirm if the UI's Keyword Planner is showing the same results as the API response shown? If yes, then Google Ads API mirrors the Google Ads UI. If not, then you may note that the KeywordPlanService.GenerateHistoricalMetrics has similar functionality in the UI's Keyword Planner. But, the API requires that you create a KeywordPlan first, and there are differences when working with a keyword plan using the Google Ads API versus the UI. You may refer to these recommendations on how to avoid mismatches in historical metrics when mixing usage. For more information, you may refer to this page.
Regards,
![]() |
Google Ads API Team |
Hi Ana,
Thank you for coming back to us. I hope you are doing well today.
Moving forward to your concern about there are differences when working with a keyword plan using the Google Ads API versus the UI, for our team to further compare, investigate, and validate why you are encountering issues, could you please provide us with the complete logs (request and response with request-id) generated on your end (where the error is shown) and the Google Ads UI screenshot (Non-cropped) of the data you are retrieving? This will help us to provide right information and recommendations in Google Ads API perspective.
Have a great day.
Regards
Hi,
Thanks for coming back to us. I hope you are doing well today.
In addition, you can provide information needed via Reply privately to the author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.
Have a great day.
Regards,
Hi Trent,
Thank you for reaching out to us.
Could you confirm if you already consider differences when working with a keyword plan using the Google Ads API versus the UI? You may refer to these recommendations on how to avoid mismatches in historical metrics when mixing usage. For more information, you may refer to this page.
However, if you have indeed considered it, could you also please provide us with the complete logs (request and response with request-id) generated on your end (where the issue is shown) and the Google Ads UI screenshot (non-cropped) of the data you are retrieving? This will help us provide the right information and recommendations from the Google Ads API perspective.
You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.
Best regards,