Hi Eric; finally after a couple of weeks, i wanted to go live with our v201109 migrated application since I thought that all basic API-features should be stable in the meantime (including real-time reports). Unfortunately just I experienced a delay of ~7 minutes with keyword reports. This is very sad and did not happen with v13 reports. Is there anything I can do to help you solving this issue ? (log excerpts etc.)
Best, Manuel Am Montag, 12. März 2012 23:40:21 UTC+1 schrieb Eric Koleda: > > Hi Manuel, > > I don't have any updates, but I'm glad to know the problem is no longer > affecting you. > > Best, > - Eric > > On Monday, March 12, 2012 7:28:39 AM UTC-4, Manuel wrote: >> >> Hi Eric, >> do you have an update ? When I tested a couple of days ago, the delay >> seemed to be gone, but I'd like to have a confirmation about this issue. >> >> Thanks in advance, best >> Manuel >> >> Am Montag, 27. Februar 2012 22:34:13 UTC+1 schrieb Eric Koleda: >>> >>> Hi All, >>> >>> The core engineering team has confirmed that some accounts may >>> experience a small delay between changing keyword data and seeing the >>> change in reports. The delay is in the order of minutes, and is leading to >>> the differences you are seeing. They are working to eliminate this delay >>> and I'll let you know when I have more information. >>> >>> Best, >>> - Eric >>> >>> On Friday, February 24, 2012 5:14:13 AM UTC-5, Manuel wrote: >>>> >>>> Hi Michael, hi Eric, >>>> I guess I'm experiencing the same issues with adhoc keyword performance >>>> reports. >>>> After adding and deleting several keywords via the API and retrieving a >>>> new report afterwards, some of the deleted keywords still exist in the >>>> report and vice versa, whereas UI results are up-to-date. >>>> Since our application syncronizes an account's data with the report, >>>> this behavior is crucial to us. >>>> As a matter of fact, by trying to syncronize with deprecated data, our >>>> application tries to delete already removed keywords, which will result in >>>> an API error >>>> >>>> EntityNotFound.INVALID_ID @ operations[0].operand.criterion.id; >>>> trigger:\'*****\' >>>> >>>> I already found out, that statistical data (clicks, conversions etc.) >>>> are updated in nightly cronjobs and are not presented in real-time. Does >>>> this circumstance also apply to the overall "up-to-dateness" of the >>>> keywords (without regarding statistical data). But that seems to be in >>>> contrary to your statement, that the report-data reflects the UI-data. >>>> >>>> I'm really interested in the outcome of Michael's case, since that >>>> seems to reflect the same issue. Please let me know, if I could help in >>>> any >>>> case. >>>> >>>> >>>> Best, >>>> Manuel >>>> >>>> PS: we did not experience those issues with the old v13 reporting >>>> services... >>> >>> -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
