Dear Eric, I seem to have sort of the same problem, but Brians solution didn't help me since now. We're using the API-Requests targeted with LanguageTargetSearchParameter and CountryTargetSearchParameter but have different results using the API and the Webinterface.
For the Keyword "wandpaneele" in the "EXACT"-Mode... i) Adwords API gives me the value of 2.400 for global_monthly_requests ii) Adwords Keyword Tool LOGGED IN WITH THE SAME USERNAME AS MY API- APPLICATION uses doesn't give me any stats about exactly this keyword (strange, isn't it?) iii) Adwords Keyword Tool External (NOT LOGGED IN, captcha-mode) gives me 8.100 for global_monthly_requests (some 340% divergence) iv) Adwords Keyword Tool LOGGED IN WITH ANOTHER USERNAME gives me 8.100 for global_monthly_requests We just wonder if the data available throughout the API is any reliable, or - as we pay for the API data - if only the API-Data is close to the truth. If you need my accounts'-data to help out pls refer to me via email. Thanks in advance Achim On 30 Jun., 22:45, AdWords API Advisor <adwordsapiadvi...@google.com> wrote: > Hi Brian, > > So it looks like the problem is due to the existence of two keyword > tools that use slightly different technology. > > 1) Search-based Keyword Tool:http://www.google.com/sktool/ > > 2) AdWords Keyword Tool:https://adwords.google.com/select/KeywordToolExternal > > The TargetingIdeaService and AdWords Keyword Tool share the same > underlying technology, and the search volume estimates should be the > same in both. The Search-based Keyword Tool uses slightly different > technology and is expected to deliver different search volume > estimates. Please using the AdWords Keyword Tool when doing > comparisons with the TargetingIdeaService. > > Best, > - Eric > > On Jun 29, 1:02 pm, Brian Jensen <bri.m....@gmail.com> wrote: > > > > > Thanks, Eric. > > > I appreciate you taking the time to review this issue and look forward > > to your findings. > > > Regards - > > Brian > > > On Jun 29, 8:03 am, AdWords API Advisor <adwordsapiadvi...@google.com> > > wrote: > > > > Hi Brian, > > > > I'll look into this a bit deeper and let you know what I find. > > > > Best, > > > - Eric > > > > On Jun 25, 5:36 pm, Brian Jensen <bri.m....@gmail.com> wrote: > > > > > Eric - > > > > > Thank you for your quick response. We actually went back and modified > > > > the 'GetRelatedKeywords.php' file from the v2009 client library > > > > examples with those additional parameters. It corrected the average > > > > monthlysearchvolumes (to show only US volumes) but the global > > > > volumes stayed the same. Both of these numbers (the average and the > > > > global) are still too high. > > > > > Using the same example: "twin air bed" > > > > Global EXACT match: 2900 (API) vs 320 (KW Tool) > > > > Local EXACT match: 2400 (API) vs 260 (KW Tool) > > > > > It actually makes sense that this only changed the local numbers since > > > > we only added language and country parameters - the global numbers > > > > should not change regardless of the language and country, correct? > > > > Can anyone else verify my numbers and the variance in returns we are > > > > seeing between the API and the KW tool? > > > > > Thanks - > > > > Brian > > > > > On Jun 24, 3:30 pm, AdWords API Advisor <adwordsapiadvi...@google.com> > > > > wrote: > > > > > > Hi Brian, > > > > > > Thedifferenceis likely due to adifferencein targeting. By default > > > > > theSearch-based Keyword Tool targets the results to your language and > > > > > country (English and United States for example). The API on the other > > > > > hand doesn't target the results by default, and will return the > > > > > statistics for all languages and countries. To emulate the results of > > > > > the keyword tool you need to include a LanguageTargetSearchParameter > > > > > and CountryTargetSearchParameter. > > > > > > http://code.google.com/apis/adwords/v2009/docs/reference/TargetingIde... > > > > > http://code.google.com/apis/adwords/v2009/docs/reference/TargetingIde... > > > > > > Best, > > > > > - Eric Koleda, AdWords API Team > > > > > > P.S. The GlobalMonthlySearchesSearchParameter and the > > > > > AverageTargetedMonthlySearchesSearchParameter are only required if you > > > > > want to limit the results to only ideas that have certain amounts of > > > > > searches. If you just want to return those values you need only to > > > > > include the GLOBAL_MONTHLY_SEARCHES and > > > > > AVERAGE_TARGETED_MONTHLY_SEARCHES AttributeTypes respectively. > > > > > > On Jun 23, 5:59 pm, Brian Jensen <bri.m....@gmail.com> wrote: > > > > > > > Hello - > > > > > > > We are using the TargetingIdeaService with the > > > > > > GlobalMonthlySearchesSearchParameter and the > > > > > > AverageTargetedMonthlySearchesSearchParameter with the STATS > > > > > > RequestType in order to returnsearchvolumes for specific keywords. > > > > > > > When I compare these results with the AdWords Keyword Tool, I'm > > > > > > baffled as to why the volumes are so far apart. > > > > > > > Example: "twin air bed" > > > > > > Global EXACT match: 2900 (API) vs 320 (KW Tool) > > > > > > Global PHRASE match: 6600 (API) vs 1000 (KW Tool) > > > > > > Global BROAD match: 33100 (API) vs 3600 (KW Tool) > > > > > > > In reading previous posts, I understand that the API should more > > > > > > closely match the SK Tool results than the Keyword Tool but even > > > > > > this > > > > > > doesn't hold true. For the example above the SK Tool returns 190. > > > > > > > Any ideas what we're doing wrong? > > > > > > > Thank you - > > > > > > Brian -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
