Hi Eric,

what I mean is:
suppose I do a query for some accented term in the latin characterset
and the google adwords api gives me
a non-zero number, how do I know if that number represents the real
number of queries for that term and not
for the unaccented term ?

Greetings,

Bram

On Jan 5, 11:50 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
> Hi Bram,
>
> I'm not sure I understand the problem.  Can you provide an example
> that demonstrates the problem?
>
> Best,
> - Eric
>
> On Dec 30 2010, 7:21 pm,bramiozo<brami...@gmail.com> wrote:
>
> > Hi Eric,
>
> > is there a consistent way in which I can check whether the results
> > apply to the seed keywords ?
> > I have tried checking the keywords from the result with the seed
> > keywords but that doesn't do the trick,
> > I see in the results from the web tool that indeed the accents are
> > removed, shouldn't the api do the same ?
>
> > (I use the php soap library btw)
>
> > Greetings,
>
> > Bram
> > On Nov 9, 10:12 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
> > wrote:
>
> > > Hi Manuel,
>
> > > Thank you for your feedback, I'll pass that along to the appropriate
> > > team.  Please be clear that this behavior I'm describing only applies
> > > to the TargetingIdeaService and the Keyword Tool, and has no bearing
> > > on Google search results or ad serving.
>
> > > Best,
> > > - Eric
>
> > > On Nov 7, 1:25 am, manuel <manuel_pa...@sapo.pt> wrote:
>
> > > > You say: "statistics for accents and non-accented keywords are
> > > > combined into a single search volume number."
>
> > > > This is absolutely wrong. Google can't simple combine two absolute
> > > > different words, with a complete different meaning into one, just
> > > > because they "look" alike.
>
> > > > I see Google is now doing the same mistake on the search results!!!
>
> > > > I don't know what language experts Google has consulted, but in
> > > > French, Spanish and Portuguese there are a lot of words that when
> > > > accented gain a complete different meaning!
>
> > > > Regards,
>
> > > > On Sep 28, 1:54 am, AdWords API Advisor <adwordsapiadvi...@google.com>
> > > > wrote:
>
> > > > > Hi All,
>
> > > > > To be clear, the changes in how accents are 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 for accents and 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 <jslasc...@hotmail.com> 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 
> > > > > > <adwordsapiadvi...@google.com>
> > > > > > wrote:
>
> > > > > > > Just to confirm, this is the intended behavior.
>
> > > > > > > Best,
> > > > > > > - Eric
>
> > > > > > > On Sep 20, 5:12 pm, AdWords API Advisor 
> > > > > > > <adwordsapiadvi...@google.com>
> > > > > > > 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<brami...@gmail.com> wrote:
>
> > > > > > > > > Besides the rather large numerical discrepancy between 
> > > > > > > > > different
> > > > > > > > > backends one thing I noticed was that the accents for 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 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

Reply via email to