Timezone changes?

[jstedman]

We have seen a change in behavior where accounts which previously
would have discrepancies in reporting due to a difference between the
timezone our system works in(PST) and the timezone of the account(GMT
in this case). The numbers used to be off which made sense, but as of
June 25th the numbers have been matching perfectly. The reports are
still being pulled at this time using the v13 reporting.

This would be considered a good thing, but any unexplained change
scares me and there have not been any changes on our side.

Was there a change in the AdWords backend that maybe caused this
change in behavior?

[jstedman]

While trying to make sense out of this, I attempted to find out what
timezone the account that is having the "correct data" issue(we
actually generated a Jira issue for this) and see if it was indeed in
the GMT timezone or if it got moved somehow.

The ServicedAccountService always returns the dateTimeZone value as
null. We will definitely be needing to retrieve this value, the old
AccountService does support it, will the ServicedAccountService be
updated to include this in the future?

[jstedman]

Correction, we won't be "needing" to retrieve it, but it would
definitely be useful.

[jstedman]

Sorry to be clogging the pipe, I have just been informed that we do
have a tool that uses the AccountService to get timezone information
for accounts, so this feature can be moved back into the "needing"
column.

[Eric Koleda]

Hi,

I'm not aware of any changes with the time reporting of reports, are you seeing this behavior across the board?  In regards to the ServicedAccountService, the description for dateTimeZone says that it isn't returned by the service, but it is a popular request.

Best,

- Eric Koleda, AdWords API Team

[Rob Ryan]

Yeah, second this request, one of the only a small amount of things the old v13 supports which haven't been picked up by the new API's.