Thanks Eric. I would suggest, if I may, to set to SE-algo so that it always searches strictly if one keyword is given.
Greetings, Bram On Sep 28, 3:54 am, AdWords API Advisor <[email protected]> wrote: > Hi All, > > To be clear, the changes in howaccentsare handled is part of a > larger change in the Keyword Tool backend, and the behavior is > consistent across the API and the web interface. My current > understanding is that the statistics foraccentsand non-accented > keywords are combined into a single search volume number. > > There are changes in search volume data across the board, as explained > in this blog post: > > http://adwords.blogspot.com/2010/09/updated-keyword-tool-out-of-beta.... > > "In addition to these improvements, we’ve also changed how we > calculate Global Monthly Searches and Local Monthly Searches. > Statistics in these columns are now based on Google.com search traffic > only. Previously, they also included traffic from search partners. > We've updated these statistics based on advertiser feedback, and hope > you find them more helpful for keyword selection." > > Your feedback regarding these changes is appreciated and I will pass > it on to the engineering and product teams. > > Best, > - Eric > > On Sep 24, 6:32 pm, JSL <[email protected]> wrote: > > > For your information, this "intended behavior" is quite an > > accomplishment in the sense that queries for some of the top latin > > accented keywords return absolutely no relevant adwords data. > > > Regardless of the "locations and languages" settings, a query for > > "crédit" (french) returns either nothing or irrelevant data for > > english credit keywords. > > > Pizza's on me at the next engineer meeting. > > > In all seriousness, success is the journey, not the destination -Bruce > > Lee > > > Good luck guys (and gals) > > > On Sep 21, 8:50 pm, AdWords API Advisor <[email protected]> > > wrote: > > > > Just to confirm, this is the intended behavior. > > > > Best, > > > - Eric > > > > On Sep 20, 5:12 pm, AdWords API Advisor <[email protected]> > > > wrote: > > > > > Hi, > > > > > I believe this was intentional, but I'll circle back with the > > > > engineering team and confirm. > > > > > Best, > > > > - Eric Koleda, AdWords API Team > > > > > On Sep 19, 10:23 am, bramiozo <[email protected]> wrote: > > > > > > Besides the rather large numerical discrepancy between different > > > > > backends one thing I noticed was that theaccentsfor the Spanish > > > > > terms are ignored, is this a bug or is this intentional ? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
