Thanks for researching this. We definately need to be able to get the changes that occurred (even with conversion optimizer adjustments). Without these changes, I really can't see the benefits of using this service. We've spent countless hours coding and troubleshooting the implemenentation of this service only to be "rewarded" by getting these TOO_MANY_CHANGES errors on most of our accounts. Will I need to use a millisecond difference in dateTimeRange to avoid this error? This seems like it will kill your service forcing users to do this.
On May 2, 3:13 pm, Eric Koleda <eric.kol...@google.com> wrote: > Hi, > > During this time frame the conversion optimizer was adjusting the bids on > many of your ad groups, which is why the service returned too many changes. > This is obviously inconvenient, and I'll talk with the team to see if there > is anything they can do to help with this case. > > Best, > - Eric Koleda, AdWords API Team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
