Hi All, Thank you for the detailed information. I've been able to replicate this issue, and I'll work with the core engineering team to address it.
Best, - Eric On Feb 11, 9:44 am, Daniel <[email protected]> wrote: > Hi Eric, > > One example that is reproducible at the moment is the phrase 'catering > stockholm', which has the same meaning in both swedish and english. > > Using the online AdWords Keyword Tool and targeting Sweden and > swedish, we get the following results for the local estimated search > volume: > broad match: 49500 > phrase match: 49500 > exact match: 49500 > > Using the AdWords API with the same targeting and keyword yields the > following results: > broad match: 49500 > phrase match: 49500 > exact match: 480 > > So using exact matching and targeting Sweden/swedish gives us a local > estimated search volume which is clearly differing from the results we > get when using the online tool. > Other keywords/phrases that seem to experience the same differences in > online vs API values are 'webbyrå', 'restaurang stockholm' and > 'sökmotoroptimering'. It seems to affect only the volumes for exact > match data though. > > Best regards, > Daniel > > On Feb 10, 9:41 pm, AdWords API Advisor <[email protected]> > wrote: > > > > > > > > > Hi Martin, > > > STATS request are the preferred method of getting statistics for known > > keywords, while IDEAS is appropriate for generating related keywords. > > There have been cases in the past where STATS and IDEAS returned > > different results, and we're working to ensure that this doesn't > > happen going forward. I'm not seeing this behavior across all > > keywords, can you provide some samples that exhibit this behavior? > > > Best, > > - Eric Koleda, AdWords API Team > > > On Feb 9, 4:02 am, Martin <[email protected]> wrote: > > > > I've found out some more about the low values for exact keyword match > > > on local search volumes. > > > > Update: > > > > The search volumes in STATS requests differ from the search volumes in > > > IDEAS requests. This explains why we experience different values in > > > the keyword tools. Is this an old issue that has resurfaced? A fix for > > > clients would be to exploit STATS requests, which is how it had to be > > > done quite some time ago. However, to ensure values for all keywords > > > there is an overhead in API-units. > > > > Are you looking into this discrepancy between the two data sources? > > > > Best regards > > > -- > > > Martin > > > > On Feb 8, 10:44 am, Martin <[email protected]> wrote: > > > > > We have noticed a a huge drop in local (sv_SE) exact match targeting > > > > for most (or all) keywords we are interested in. > > > > > The search volumes in the API also differ largely from the values in > > > > the Keyword Tool. > > > > > Is there being work done to correct this issue? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [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
