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 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
Re: JobError.TOO_LATE_TO_CANCEL_JOB
Thanks Eric. I thought as much. I'll check my queue again. On Nov 6, 8:10 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Daragh, I'm actually working on a blog post about this now, but the short version is that you can only REMOVE a job if it is in the PENDING state and it hasn't yet received all the parts. If all the parts have been received, and it enters the job queue, it cannot be deleted. Instead you must wait for it to complete. Best, - Eric Koleda, AdWords API Team On Nov 4, 3:00 am, daragh99 darag...@gmail.com wrote: Hi there, I've submitted a number of jobs to the sandbox. I've got 10 jobs in the PENDING state, but when I try to remove them I get JobError.TOO_LATE_TO_CANCEL_JOB. What does this mean? What do I need to get these jobs out of the queue? Is it a case of waiting? I can't find any documentation. Thanks, Daragh -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: v201008 reporting columns
We have found some more discrepancies between the columns returned by getReportFields and those actually available. requestIdf6d766aff713a9475564cd7b921680fb/requestId ... did NOT return HourOfDay, however we find that we can successfully request an ADGROUP_PERFORMANCE_REPORT with this column included. As before, this makes us nervous for a couple of reasons. Firstly, we would prefer not to build reports based on undocumented columns, out of fear that they might be more likely to be removed than documented ones. Secondly, it raises questions about what other columns we could use that we haven't tripped over accidentally. Finally, with our own development cutoff date quickly approaching, we are wondering if v13 reporting might not be a more stable option, and if you intend on keeping it around for longer than previously hinted at? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: JobError.TOO_LATE_TO_CANCEL_JOB
Hi Eric, All my jobs have received all their parts and have been processing since Friday morning (nearly four days ago). Each job is merely submitting 100 ads. Is it normal for this to take so long, even in the sandbox? Daragh On Nov 8, 3:39 pm, daragh99 darag...@gmail.com wrote: Thanks Eric. I thought as much. I'll check my queue again. On Nov 6, 8:10 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Daragh, I'm actually working on a blog post about this now, but the short version is that you can only REMOVE a job if it is in the PENDING state and it hasn't yet received all the parts. If all the parts have been received, and it enters the job queue, it cannot be deleted. Instead you must wait for it to complete. Best, - Eric Koleda, AdWords API Team On Nov 4, 3:00 am, daragh99 darag...@gmail.com wrote: Hi there, I've submitted a number of jobs to the sandbox. I've got 10 jobs in the PENDING state, but when I try to remove them I get JobError.TOO_LATE_TO_CANCEL_JOB. What does this mean? What do I need to get these jobs out of the queue? Is it a case of waiting? I can't find any documentation. Thanks, Daragh -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
