Exact results for keyword search volume

[OMC Ticketsystem]

HI,

I´m using Python to query keyword search volumes.

The following is the snippet of my source to query the api:

    keywords = ['e-bike herren', 'transportkarre']

        targeting_idea_service = self.client.GetService(
        'TargetingIdeaService', version='v201409')
       
        # Construct selector object and retrieve related keywords.
        offset = 0
   
        selector = {
            'searchParameters': [
            {
            'xsi_type': 'RelatedToQuerySearchParameter',
            'queries': queries
            },
            {
            'xsi_type': 'LanguageSearchParameter',
            'languages': [{'id': '1001'}]
            }
            ],
            'ideaType': 'KEYWORD',
            'requestType': 'STATS',
            'requestedAttributeTypes': ['KEYWORD_TEXT', 'TARGETED_MONTHLY_SEARCHES'],
            'paging': {
            'startIndex': str(offset),
            'numberResults': str(self.PAGE_SIZE)
            }
        }
   
    more_pages = True
    while more_pages:
        page = targeting_idea_service.get(selector)
        # ..


This works but there is a significant difference between the intersection of the resulting search volumes and the search volume from the Google Keyword Planner. (e.g. 8817 vs 170 for "e-bike herren" and 15217 vs 1300 for "transportkarre"). I´ve come acoss KeywordMatchType which may be set to 'EXACT' to fetch better values. However I´am not seeing a way to define that in the above source. I tried defining "matchType": 'EXACT' at different places in the selector.

Can someone please tell how to make this call request exact data?


[Josh Radcliff (AdWords API Team)]

Hi,

According to the RelatedToQuerySearchParameter.queries documentation, that parameter will perform exact match queries.

You may want to take a look at our Targeting ideas guide, which includes tips on matching results from the service to the Keyword Planner UI.

Thanks,

Josh, AdWords API Team

[OMC Ticketsystem]

Thank you! The NetworkSearchParameter seems to do the work for me.