So I just thought I'd follow up here to see if there might be any new thinking regarding this issue. I attempted to get some information about this in the AdWords forum but no-one seemed to have any idea why the Estimator behaves this way.
Eric (or whomever), is there another resource I can use to either get this fixed? The problem is wasting resources both for my client and for Google as we have to send these keywords in batches of 5 at a time. Ian -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
