Data mismatch between Google UI (Keyword planner) and API (TrafficEstimatorService)

[SR]

The forecast result between Google UI (Keyword planner) and API (TrafficEstimatorService) are not matching. 

1. Same ad account used in UI and API

2. Same Keyword, language, location, max cpc and daily budget

3. Network - Google and Search partner

'networkSetting': {

                  'targetGoogleSearch': 'true',

                  'targetSearchNetwork': 'true',

                  'targetContentNetwork': 'false',

                  'targetPartnerSearchNetwork': 'false'

                  }

But there is huge difference on impressions, clicks data between UI and API. Please let me know if any other setting is required or what is the exact issue. I gone through the forum and found few answers for the same question and tried incorporating the same but still I am getting the same result. Please advice on how to proceed with this. Thanks.

[SR]

Sharing an example for better understanding:

Keyword: digital marketing, Location: India, Language: English, Budget: 7500.00, Max cpc: 15.00

UI result: Impressions: 24,202, clicks: 1519

API result: Impressions: 10506, clicks: 405

[Google Ads API Forum Advisor Prod]

Hi,

Thank you for reaching out and sharing that information. Can you please share the complete detailed request and response logs of the API call via Reply privately to author as well as a screenshot of the UI keyword planner?

Regards,
Mitchell
Google Ads API Team

ref:_00D1U1174p._5004Q20WSYQ:ref

[Amandeep Walia]

Hello

Was this sorted please also share the details for this problem even more people are facing the same issue. Also can you clarify whether the clicks and impressions from keywordplanner api are daily basis or the complete count for the provided time period while creating the keyword plan. If yes then how the "total cost" key is dependent on this.

[Google Ads API Forum Advisor Prod]

Hi Amandeep,

If you are asking about the discrepancy between the UI and the API, then please note that the AdWords TrafficEstimatorService actually runs on a different back-end server than the UI keyword planner. The discrepancies between the UI and the API are expected. If you want API results that are closer to the UI, you should use Google Ads API keyword planning instead.

As for your second question, clicks and impressions returned are daily estimates.

Regards,

Danica Google Ads API Team

ref:_00D1U1174p._5004Q20WSYQ:ref