Hi,
Thanks for reaching out to Google Ads API Forum.
With regards to your concern, based on our Blog post KeywordPlanAdGroupForecast and KeywordPlanKeywordForecast will be deprecated in the Google Ads API. This change will be effective on June 1, 2023.
Starting June 1, the GenerateForecastMetricsRequest will still be used to fetch forecasts, but the KeywordPlanAdGroupForecast and KeywordPlanKeywordForecast will be empty. The KeywordPlanCampaignForecast will be returned as usual. If you are using KeywordPlanAdGroupForecast or KeywordPlanKeywordForecast in your applications, update your applications to ensure that they can handle blank responses.
Links included in this email:
![]() |
Google Ads API Team |
Hi all,
Thank you for getting back to us.
Please see my responses for your concerns respectively.
There is no example for using KeywordPlanCampaignForecast for now. In the meantime, you may refer to this guide (https://developers.google.com/google-ads/api/docs/keyword-planning/generate-forecast-metrics#generate-metrics).
Hi Aqeel,
Thanks for getting back to us.
There is no definite timeline for the availability for code examples in our documentation. However, you may also check with the Client library owner by opening an issue with the Issue Tracker in GitHub with your chosen client library.
Hi Aqeel,
Thank you for coming back and for the update. I hope you are doing well today.
With regards to your concern, could you please confirm if you already reached out to the Github where the sample code came from for this concern? If not yet, we recommend confirming this issue to the Github team.
However, since you also mentioned that this is also related to API, if you're encountering Google Ads API issues or errors, for our team to further compare, investigate, and validate why you are encountering issues, can you provide more information?
We do this to check if there’s an error thrown on your side and provide accurate recommendations.
If you haven't enabled logging yet, it can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link. For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output.
Reference links:
Have a great day.
Hi,
Thank you for your patience.
Upon checking, we are unable to replicate the behavior your reported. As per testing, we were able to get the expected output.
Please see further details below:
Keyword: plombier
Response:
---------------------------
Keyword: garde meuble
Response:
---------------------------
Keyword: location voiture
Response:
---------------------------
Combining the 3 keywords:
First request:
Keyword: plombier, garde meuble, location voiture
Response:
---------------------------
Keyword: location voiture, plombier, garde meuble
Response:
---------------------------
Keyword: location voiture, garde meuble, plombier
Response:
---------------------------
As you may have referred to our documentation, the expected response will only contain the data found here.
Let me know if you have any questions or if the issue persists on your end, provide us with the logs for the all of the scenarios you listed which shows the issue in your end so we can further investigate.
Hi Aqeel,
I hope all is well.
I would like to double check if the issue described on your forum thread "When using multiple keywords, generateKeywordForecastMetrics it only returns the response against the last keyword I used" dated on July 4, 2023 has been resolved on your end or not. I would like to provide my additional insights on your described concern, and I did perform all the steps to check to see if indeed said behavior was observed or not.
So, let me provide you additional insights with my replications based on your concern description. I tried to use multiple keywords and see the response, then I saw that it had a different response when I used only 1 keyword.
Also, I tried to put a keyword sequence like how you were added in your request, but still I couldn’t see the observations that you described. You may see below screenshot showing requests with different keywords variations along with responses for each request for better understanding:

If you are still seeing behavior that you mentioned, could you please privately provide the latest full logs(complete request and response logs with request ID and request header) showing the behavior, so that we can investigate the issue further?