Both the v13 account service and the new reporting service will return different kind of values. The v13 account service uses the timezone ID, such as "Europe/Berlin". This is a good idea, as it can be used with timezone databases that have historical data and know how to convert between daylight saving time correctly.
The timezoneId field in the generated reports will give you the GMT offset. E.g. for one of our accounts this would be '(GMT+01:00) Berlin'. I could parse this value and work with the GMT offset, but the offset will change between summer/winter time. So I'd have to pull this report on daily basis and update the value in my database to track changes. What I also noticed is that the timezone will not be correct for historical data in the report. E.g. when I request a report for june, I won't get the correct summer time offset: 'Jun 1, 2011' - '(GMT+01:00) Berlin' -> should be +2 -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
