Re: TOO_MANY_CHANGES error when access customersync service

Sorry I missed the email. Thanks for the response. I will look into it. Thanks Tirtha On Thursday, February 21, 2019 at 2:01:07 PM UTC-8, googleadsapi-forumadvisor wrote: > > Hi Tirtha, > > Yes, I had replied to you privately on the same day. Let me share my > response here: > > Upon checking

RE: TOO_MANY_CHANGES error when access customersync service

Hi Tirtha, Yes, I had replied to you privately on the same day. Let me share my response here: Upon checking the change history, I see that the timestamp when the ad groups were created in the campaign (id = 1690014842) is Jan 29, 2019, 1:52:49 PM. As you noticed these are in GMT. Hence

Re: TOO_MANY_CHANGES error when access customersync service

Hey Sree, Did you find my private message with the details? Thanks Tirtha On Wednesday, February 13, 2019 at 11:25:37 AM UTC-8, googleadsapi-forumadvisor wrote: > > Hi Tirtha, > > The service would always return campaign ids based on the selector > irrespective of whether it was changed or

RE: TOO_MANY_CHANGES error when access customersync service

Hi Tirtha, The service would always return campaign ids based on the selector irrespective of whether it was changed or not. But the campaignChangeStatus will reflect

Re: TOO_MANY_CHANGES error when access customersync service

Hi Sree, Few followup questions. The documentation says that the *changedCampaigns* object contains all campaign ids from the selector even if the campaign *did not change*. But ad_group_ids which show up within the *changedAdGroups* have some changes in them. I was testing with an account

RE: TOO_MANY_CHANGES error when access customersync service

Hi Tirtha, Please find my responses inline: 1. How small of a time window can i provide to the customersync service? The dateTimeRange is expected in the