No, changes like that should not affect the CustomerSyncService. The main
use case of service is intended to keep the data structure of the account
in sync if there are multiple entities that access the account. For
example, you can grab a list of changes since the last time you looked at
the account and update your local representation of the account to match
the new canonical representation on the server.
Statistics and read-only attributes that are not settable by any users
should not trigger any change in the CustomerSyncService.
Mike, AdWords API Team
On Wednesday, November 30, 2016 at 7:58:54 PM UTC-5, David Antunes wrote:
> I get the feeling that the CustomerSyncService is reporting too many
> Do changes for example in the FirstPageCPCBid, or TopOfThePageBid, etc of
> an Ad for example count as "changed" in the CustomerSyncService?
> Many thanks!
Also find us on our blog and Google+:
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@example.com
To unsubscribe from this group, send email to
For more options, visit this group at
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.