Hi Ming,
Thanks for getting back to us.
For your other question, you may note that API and UI treat keyword plans can result in seeming discrepancies when comparing results between the two. To avoid misinterpreting the results, keep the following rules in mind:
- The Google Ads API always uses the settings at the KeywordPlanCampaign level.
- The Google Ads UI always uses the settings at the KeywordPlan level. However, these settings are not currently accessible to the API.
- If you create a KeywordPlan using the Google Ads API, it shows up in the UI as targeting all locations and languages.
- The UI also shows various metrics for all locations and languages; the settings at the underlying KeywordPlanCampaign are ignored by the UI. The UI might also prevent you from editing these keyword plans.
- If you create a KeywordPlan using the UI, the Google Ads UI sets geo targets for the underlying KeywordPlanCampaign under certain conditions.
- These settings are not presented to you on the UI, which can lead to a mismatch in metrics when comparing them against the values retrieved using the API.
- Editing the keyword plan settings in the UI can also cause the API and UI metrics to diverge.
This is because the Google Ads UI exposes these settings at the plan level and doesn't expose the underlying KeywordPlanCampaign and KeywordPlanAdGroup objects. When possible, avoid mixing the keyword plans created by the API and the UI.
In addition, I can see that you are using Google Ads API v10, however, please note that v10 is already deprecated, and after the sunset, all v10 API requests will begin to fail. We highly recommend to please migrate to a newer version prior to February 1, 2023 to ensure your API access is unaffected.
For additional information, please see Deprecation and Sunset, and Release Notes for the functionality and changes added in v12.
Regards,
 |
| Yasar |
| Google Ads API Team |
|
|
| |

ref:_00D1U1174p._5004Q2iNzTT:ref