ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH

2016-01-18 Thread google
We created an API which creates an AD_PERFORMANCE_REPORT for the last day in XML format. Running it with the token with our test-account, everything works as it should. So today our token got approved for the acctual account (Login is MCC). So we changed the Login data accordingly in the app.con

Getting Intermittent "CustomerSyncError.TOO_MANY_CHANGES" response for the same requested time frame

2016-01-18 Thread Giles Bodger
Hi all, Question on having to full sync because of "too many changes" error We have an implementation that for many accounts will try to do a sync every 15 minutes for the latest changes since the previous sync. This has been running fine for the last 3 years or so, but i have noticed recently

Re: ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH

2016-01-18 Thread google
OK, we solved it. In case someone else has same problem. The accountnumber passed to create the Reports for, can't be a MCC account number! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.c

Re: ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH

2016-01-18 Thread Thanet Knack Praneenararat (AdWords API Team)
Hello, Thanks so much for sharing your issue and solution. Yes, reports should be requested using a non-MCC account number. Best, Thanet, AdWords API Team On Tuesday, January 19, 2016 at 12:26:20 AM UTC+9, goo...@gruener-fisher.de wrote: > > OK, we solved it. In case someone else has same probl