Hi Eric,
Is there any update on a fix for this bug? It's been almost three
weeks since you mentioned the engineering team were looking into this.
Thanks
Andrew
On Jul 12, 4:13 pm, AdWords API Advisor <
adwordsapiadvi...@google.com>
wrote:
> Hi,
>
> The core engineering team is working on this issue, but at this time I
> don't have any further details.
>
> Best,
> - Eric
>
> On Jul 9, 5:21 pm, k <
keen...@gmail.com> wrote:
>
> > Bump. I am having the same problem as Achim above. It is quite
> > maddening.
>
> > Has anyone figured out why there is such a huge discrepancy?
>
> > Can anyone explain how to get the stats for A SINGLE PARTICULAR
> >keywordusing the GUItoolwhen signed in?
>
> > If there is no fix for this, then I would at least like to understand
> > what is causing the hugedifference.
>
> > Thanks, K
>
> > On Jul 5, 7:42 am, GMTD <
i...@kntrst.com> wrote:
>
> > > Dear Eric,
> > > I seem to have sort of the same problem, but Brians solution didn't
> > > help me since now.
> > > We're using theAPI-Requests targeted with
> > > LanguageTargetSearchParameter and CountryTargetSearchParameter but
> > > have different results using theAPIand the Webinterface.
>
> > > For theKeyword"wandpaneele" in the "EXACT"-Mode...
> > > i) AdwordsAPIgives me the value of 2.400 for global_monthly_requests
> > > ii) AdwordsKeywordToolLOGGED IN WITH THE SAME USERNAME AS MYAPI-
> > > APPLICATION uses doesn't give me any stats about exactly thiskeyword
> > > (strange, isn't it?)
> > > iii) AdwordsKeywordToolExternal (NOT LOGGED IN, captcha-mode) gives
> > > me 8.100 for global_monthly_requests (some 340% divergence)
> > > iv) AdwordsKeywordToolLOGGED IN WITH ANOTHER USERNAME gives me
> > > 8.100 for global_monthly_requests
>
> > > We just wonder if the data available throughout theAPIis any
> > > reliable, or - as we pay for theAPIdata - if only theAPI-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, AdWordsAPIAdvisor <
adwordsapiadvi...@google.com>
> > > wrote:
>
> > > > Hi Brian,
>
> > > > So it looks like the problem is due to the existence of twokeyword
> > > > tools that use slightly different technology.
>
> > > > 1)Search-basedKeywordTool:
http://www.google.com/sktool/
>
> > > > 2) AdWordsKeywordTool:
https://adwords.google.com/select/KeywordToolExternal
>
> > > > The TargetingIdeaService and AdWordsKeywordToolshare the same
> > > > underlying technology, and thesearchvolumeestimates should be the
> > > > same in both. TheSearch-basedKeywordTooluses slightly different
> > > > technology and is expected to deliver differentsearchvolume
> > > > estimates. Please using the AdWordsKeywordToolwhen 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, AdWordsAPIAdvisor <
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 (KWTool)
> > > > > > > Local EXACT match: 2400 (API) vs 260 (KWTool)
>
> > > > > > > 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
> > > > > > > seeingbetweentheAPIand the KWtool?
>
> > > > > > > Thanks -
> > > > > > > Brian
>
> > > > > > > On Jun 24, 3:30 pm, AdWordsAPIAdvisor <
adwordsapiadvi...@google.com>
> > > > > > > wrote:
>
> > > > > > > > Hi Brian,
>
> > > > > > > > Thedifferenceis likely due to adifferencein targeting. By default
> > > > > > > > theSearch-basedKeywordTooltargets the results to your language and
> > > > > > > > country (English and United States for example). TheAPIon 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
> > > > > > > > thekeywordtoolyou 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, AdWordsAPITeam
>
> > > > > > > > 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 AdWordsKeywordTool, I'm
> > > > > > > > > baffled as to why the volumes are so far apart.
>
> > > > > > > > > Example: "twin air bed"
> > > > > > > > > Global EXACT match: 2900 (API) vs 320 (KWTool)
> > > > > > > > > Global PHRASE match: 6600 (API) vs 1000 (KWTool)
> > > > > > > > > Global BROAD match: 33100 (API) vs 3600 (KWTool)
>
> > > > > > > > > In reading previous posts, I understand that theAPIshould more
> > > > > > > > > closely match the SKToolresults than theKeywordToolbut even this
> > > > > > > > > doesn't hold true. For the example above the SKToolreturns 190.