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.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
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
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
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
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.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and
