Hi,

Thank you for reaching out to the Google Ads API support team.

After reviewing your concern, I understand that you are observing the data 
discrepancy in the values of Keyword Planner between the Google Ads UI and the 
API. Please find the answers for your questions below:

1. Could you please confirm which seed type (KeywordSeed, KeywordAndUrlSeed, 
etc.) corresponds to this functionality in the API?

I would suggest you to use UrlSeed for the URL of a webpage or entire website 
related to your business. The URL seed targets only a specific URL. If there 
are no hits, the search automatically expands up to the pages from the same 
domain.

2. Are there any additional fields or parameters I should pass in the 
GenerateKeywordIdeasRequest to better align API results with what is shown in 
the UI?

I would suggest you to exactly match the API and UI with all the filters 
mentioned in this link.

3. Could you please confirm whether this relevance score is available through 
the API, and if not, is there any alternative metric or approach recommended to 
approximate it?

Kindly note that  the relevance score (like 99, 94, 89) displayed in the Google 
Ads UI's Keyword Planner is not directly available through the Google Ads API. 
You can see that there is no field for "relevance score" in 
KeywordPlanIdeaService.GenerateKeywordIdeas.

If you still face descripancies after following the above suggestions, kindly 
provide us with the complete API logs (request and response logs with 
request-id and request header) generated at your end along with the 
corresponding uncropped UI screenshot (from Google Ads account) highlighting 
the keywords generated.

If you are using a client library and haven't enabled the logging yet, I would 
request you to enable logging for the specific client library that you are 
using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to 
enable logging at your end. For REST interface requests, you can enable logging 
via the curl command by using the -i flag.

Thanks,

Google Ads API Team


Feedback
How was our support today?


[2025-05-02 09:04:10Z GMT] This message is in relation to case 
"ref:!00D1U01174p.!500Ht01qVTx7:ref" (ADR-00303099)

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/adwords-api/BdMcW000000000000000000000000000000000000000000000SVMMIY00sEKf3rOrRISCJwhkfn5BBA%40sfdc.net.
  • AP... Amit Tomar
    • ... Amit Tomar
      • ... Amit Tomar
        • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to