TargetingIdeaService: How can I get keyword suggestions for more than 10 locations using LocationSearchParameter?

[Will Sampson]

Hi,

I'm using the TargetingIdeaService to retrieve a list of keywords, their average cpc, competition, and search volume.  One of the parameters I use to get the list of keywords is a collection of Location Criteria IDs.  In some cases I'd like to get keyword data for more than 10 locations.  Since the LocationSearchParameter doesn't allow you to send more than 10 I've decided to make multiple calls to the API and combine the average cpc, competition, and search volume afterwards.  So far I've tested with two locations in very different parts of the USA with exactly the same population, getting the individual and combined keyword data but have thus far been unable to determine how the service is combining them.  How can I combine these values myself when doing multiple api calls so it matches the combined values I'd be getting back from the service?  Or alternatively is there a better way for me to get combined keyword data for more than 10 locations?

[Vincent Racaza (AdWords API Team)]

Hi Will,

You are correct, the TargetingIdeaService only accepts up to 10 locations to be targeted for keyword requests as LocationSearchParameter. In regards to the workaround of combining the data (e.g. average CPC, competition, etc.) from the different requests for different locations, it seems that it would be difficult as the data being returned is based on the specific parameters on your request. For example, you cannot just combine or add the average CPC from multiple requests as we are not 100% sure how the backend computes this per request.

In the AdWords UI's Keyword Planner, it accepts more than 10 locations, however, when clicking the "Get ideas" button, it shows you this warning message "These statistics are for the first 10 locations you selected. But don't worry, you'll get forecasts for all of the locations.". With this, there appears to be no available workaround for your requirement since both the AdWords UI and API behaves the same way.

As a recommendation, you can start with fewer locations first. For example, the first request will target 2 locations, the second request will target another 2 different locations, and the third request will target all the 4 locations. By the result of each request, you can compare and check if you can combine the results (per keyword idea) of first and second requests and if their combination is equal to the result of the third request. If the result combination of first and second requests is indeed equal to the third request, then most probably, the formula (e.g. you can check if you just need to do an addition, or you need to get their average per data) that you are using is correct. You can then use that formula in the combination of your multiple requests for more than 10 locations.

Furthermore, since AdWords API and UI returns the same result and behaves the same way, then this is more on the AdWords product level concern. You can post this concern in the AdWords Community Forum for further assistance on how to combine (e.g. formula) results from different requests with different locations.

Thanks,

Vincent

AdWords API Team

[Will Sampson]

Vincent,

So far I've done as you said and tested regions together and separately several times and have no idea how the service is combining the keyword data by region.  Average cpc and competition are doing something entirely different than an average, its not weighted by population so I assume it must be taking something else into account.  The values aren't TOO far off from an average but enough that I wouldn't feel comfortable using it in my application.  I'll poke around in the AdWords Community Forum as you've said.

[Vincent Racaza (AdWords API Team)]

Hi Will,

Yes, you can post in the AdWords Community Forum to confirm how the backend computes these data when there are targeted locations and if they can provide any recommendation/workaround on this product-level limitation.