Re: lastChangeTimestamp in CustomerSyncService interpretation

Hello, I apologize for the delay in getting back to you. Unfortunately, this is currently working as intended. You need to include a time zone in the request, in the min and max fields. Then, the response will be in the same time zone you specified in the selector. Unfortunately, this service d

Re: lastChangeTimestamp in CustomerSyncService interpretation

Hello Mike, Any update on this? Thanks, On Monday, 17 August 2015 19:13:16 UTC+5:30, Michael Cloonan (AdWords API Team) wrote: > > Hello Chirag, > > Can you please send a SOAP request/response that exhibits this behavior *only > to me* by using the drop-down arrow at the top of my post? This w

Re: lastChangeTimestamp in CustomerSyncService interpretation

Hello Chirag, Can you please send a SOAP request/response that exhibits this behavior *only to me* by using the drop-down arrow at the top of my post? This will help me look into and troubleshoot what may be going wrong. Regards, Mike, AdWords API Team On Monday, August 17, 2015 at 1:01:40 AM

Re: lastChangeTimestamp in CustomerSyncService interpretation

Hello Umesh, I am getting lastChangeTimestamp as *PST8PDT* only for few of my accounts. I have checked the account timezone. It is set for (GMT+05:30) India Standard Time

Re: lastChangeTimestamp in CustomerSyncService interpretation

Hi Chirag, The lastChangeTimestamp field will return the date based on dateTimeZone

lastChangeTimestamp in CustomerSyncService interpretation

Hello All, If I got lastChangeTimestamp in CustomerSyncService as *20150814 011235 PST8PDT * Should I consider same as *2015-08-14 01:12:35 GMT - 8?* Is lastChangeTimestamp always be in *PST8PDT? or* It should be in* different zone account wise?* There is no documentation there to explain t