Re: db migration, are accents now ignored for spanish terms
Hi Bram, I don't think there is any way to get that information from the API. Best, - Eric On Feb 14, 3:31 pm, bramiozo wrote: > 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 > 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 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 > > > 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 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 > > > > > 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 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 > > > > > > > > > > > > > > wrote: > > > > > > > > > Just to confirm, this is the intended behavior. > > > > > > > > > Best, > > > > > > > > - Eric > > > > > > > > > On Sep 20, 5:12 pm, AdWords API Advisor > > > > > > > > > > > > > > > > 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 wrote: > > > > > > > > > > > Besides the rather large numerical discrepancy between > > > > > > > > > > different > > > > > > > > > > backends one thing I noticed was that t
Re: db migration, are accents now ignored for spanish terms
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 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 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 > > 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 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 > > > > 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 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 > > > > > > > > > > > > wrote: > > > > > > > > Just to confirm, this is the intended behavior. > > > > > > > > Best, > > > > > > > - Eric > > > > > > > > On Sep 20, 5:12 pm, AdWords API Advisor > > > > > > > > > > > > > > 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 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 yo
Re: db migration, are accents now ignored for spanish terms
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 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 > 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 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 > > > 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 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 > > > > > wrote: > > > > > > > Just to confirm, this is the intended behavior. > > > > > > > Best, > > > > > > - Eric > > > > > > > On Sep 20, 5:12 pm, AdWords API Advisor > > > > > > > > > > > > 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 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
Re: db migration, are accents now ignored for spanish terms
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 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 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 > > 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 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 > > > > wrote: > > > > > > Just to confirm, this is the intended behavior. > > > > > > Best, > > > > > - Eric > > > > > > On Sep 20, 5:12 pm, AdWords API Advisor > > > > > 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 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
Re: db migration, are accents now ignored for spanish terms
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 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 > 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 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 > > > wrote: > > > > > Just to confirm, this is the intended behavior. > > > > > Best, > > > > - Eric > > > > > On Sep 20, 5:12 pm, AdWords API Advisor > > > > 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 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
Re: db migration, are accents now ignored for spanish terms
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 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 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 > > wrote: > > > > Just to confirm, this is the intended behavior. > > > > Best, > > > - Eric > > > > On Sep 20, 5:12 pm, AdWords API Advisor > > > 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 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
Re: db migration, are accents now ignored for spanish terms
Hello This is a VERY SERIOUS issue. "Vídeos" is Spanish "Vidéos" is French "Videos" is English "Música" is Portuguese "Musica" is Spanish "Secretária" is a woman (pt) "Secretaria" is a building (pt) "País" means country (pt) "Pais" means parents (pt) This used to be correct on previous Adwords API. What has happened? Do you mean to tell us this is the way Google is handling the data inside for the search results also!?!?! Please fix this HUGE BUG asap. Regards, Manuel -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
Re: db migration, are accents now ignored for spanish terms
Hi Calford, The TIS choosing to combine statistics for the accented and non- accented version of a word does not reflect any changes in the way Google.com search or AdWords ad serving behaves. As far as I know all accents are treated the same way. Best, - Eric On Oct 8, 9:10 am, calford wrote: > I just ran a small test and got a bit confused > > i searched for café in google.fr and google.es > > and the adwords campaigns on the results page are related to coffee. > > So the search and adwords does take into consideration the accents, > but the api just doesnt show the results? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
Re: db migration, are accents now ignored for spanish terms
I just ran a small test and got a bit confused i searched for café in google.fr and google.es and the adwords campaigns on the results page are related to coffee. So the search and adwords does take into consideration the accents, but the api just doesnt show the results? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
Re: db migration, are accents now ignored for spanish terms
If this does not apply for all accents, can we get a list of the ones that are affected? On Sep 30, 10:15 am, bramiozo wrote: > 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 > 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 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 > > > wrote: > > > > > Just to confirm, this is the intended behavior. > > > > > Best, > > > > - Eric > > > > > On Sep 20, 5:12 pm, AdWords API Advisor > > > > 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 wrote: > > > > > > > Besides the rather large numerical discrepancy between different > > > > > > backends one thing I noticed was that theaccentsfor theSpanish > > > > > > 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
Re: db migration, are accents now ignored for spanish terms
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 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 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 > > wrote: > > > > Just to confirm, this is the intended behavior. > > > > Best, > > > - Eric > > > > On Sep 20, 5:12 pm, AdWords API Advisor > > > 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 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 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
Re: db migration, are accents now ignored for spanish terms
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.html "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 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 > wrote: > > > > > > > Just to confirm, this is the intended behavior. > > > Best, > > - Eric > > > On Sep 20, 5:12 pm, AdWords API Advisor > > 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 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
Re: db migration, are accents now ignored for spanish terms
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 wrote: > > > Just to confirm, this is the intended behavior. > > Best, > - Eric > > On Sep 20, 5:12 pm, AdWords API Advisor > 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 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
Re: db migration, are accents now ignored for spanish terms
Eric, I have to urge a reconsideration of ignoring accents, this is really undermining the usefulness of the api and what is more, of google SE itself. Accents are part of most languages which have a roman characterset, they convey meaning and in some cases the presence of accents might indicate a completely different meaning. Targeting your advertisement starts with the keywords, imo you should leave the keywords alone. I think this move will not remain without consequences, if google thinks that languages have accents for no particular reason and chooses to ignore them it will raise awareness of language conservation groups all over the world and it will be considered a nuisance by everyone who now have to type their accented keywords with a plus sign or quotation marks just to ensure that google will not mess it up. A trivial example is "røge" which means smoke in Danish, in the new google SE interface I get everything BUT røge and instead end up with french cousin "rogé", even a Russian one, simply because my browser is French, if I type "røge" I mean "røge" ! Of all this doesn't explain why your non-roman character domains show significantly lower results, this imo undermines using google #SERP/SV as a reference. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
Re: db migration, are accents now ignored for spanish terms
The old keyword tool was supposed to have been shut down last month, but it is still running. For how long? Please keep it running forever... But, does it still get feed with updated data? Why this move? You really wanted to avoid people using the tool to search for unique keywords stats didn't you? That's what the paid Adwords API is for, right? ;) On Sep 24, 9:38 am, bramiozo wrote: > Thanks Eric, did they tell you why because accented terms in French, > Portuguese, Spanish ARE searched. > > This behavior applies to what roman character languages exactly and/or > to what accents ? For instance German seems to be ok with the umlaut > (ü,ö etc.) > but ç with French is ignored, how did they decide what accents to > include and what not ? > Does the development team expect foreign advertisers to ignore accents > and misspell their content (I assume not) or is it a catch-all > solution where > accented and non-accented results are added ? > > This means that accented terms for these particular languages/accents > are ignored also in the SERP's ? > > I think it undermines the fidelity of the results since it is unknown > to what extent the results come from the accented terms and to what > extent > it comes from the non-accented terms, furthermore the accents are > ignored with the advent of idn's where exact searches on accented > terms might > be relevant for indexing. > > Sorry but it does raise some questions :) . > > On Sep 22, 2:50 am, AdWords API Advisor > wrote: > > > Hi, > > > Just to confirm, this is the intended behavior. > > > Best, > > - Eric > > > On Sep 20, 5:12 pm, AdWords API Advisor > > 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 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
Re: db migration, are accents now ignored for spanish terms
Thanks Eric, did they tell you why because accented terms in French, Portuguese, Spanish ARE searched. This behavior applies to what roman character languages exactly and/or to what accents ? For instance German seems to be ok with the umlaut (ü,ö etc.) but ç with French is ignored, how did they decide what accents to include and what not ? Does the development team expect foreign advertisers to ignore accents and misspell their content (I assume not) or is it a catch-all solution where accented and non-accented results are added ? This means that accented terms for these particular languages/accents are ignored also in the SERP's ? I think it undermines the fidelity of the results since it is unknown to what extent the results come from the accented terms and to what extent it comes from the non-accented terms, furthermore the accents are ignored with the advent of idn's where exact searches on accented terms might be relevant for indexing. Sorry but it does raise some questions :) . On Sep 22, 2:50 am, AdWords API Advisor wrote: > Hi, > > Just to confirm, this is the intended behavior. > > Best, > - Eric > > On Sep 20, 5:12 pm, AdWords API Advisor > 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 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
Re: db migration, are accents now ignored for spanish terms
Hi, Just to confirm, this is the intended behavior. Best, - Eric On Sep 20, 5:12 pm, AdWords API Advisor 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 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
Re: db migration, are accents now ignored for spanish terms
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 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
