Re: Timezone reference table updated

Hi Brandon, I explained a bit on the other thread. Basically, I think you should just need to specify date & time with the account timezone, no need to shift for your current timezone. If you could explain your use case,

Re: Timezone reference table updated

This is the first time that we pulled AccountTimeZoneId in reports so I am not sure if this has always been the case. It's creating issues on our end since at the moment -05:00 is US/Central, not Eastern so our DateTime logic gets messed up; $date = new DateTime('2012-07-15 00:00:00 -05:00'); // 2

Re: Timezone reference table updated

Brandon, are you saying you only just started getting inaccurate results for timezone? Has it not always been like this? On Tuesday, August 14, 2012 9:31:51 PM UTC+1, Brandon Parise wrote: > > The timezone is not being shifted based upon the observance of daylight > savings time. > > I pulled a

Re: Timezone reference table updated

The timezone is not being shifted based upon the observance of daylight savings time. I pulled a report for today: 103526900,2012-08-14,1.0,4,1,7.59,9,(GMT-05:00) Eastern Time The current offset should be GMT-04:00 B On Wednesday, February 29, 2012 6:05:16 PM UTC-5, Eric Koleda wrote: > > Hi

Timezone reference table updated

Hi All, We've recently updated the timezone reference table in our documentation: http://code.google.com/apis/adwords/docs/appendix/timezones.html This table now includes the POSIX name of the timezone used by the CreateAccountService as well as the display name returned in the AccountTimeZone