DamonHD - 10:22 pm on Oct 19, 2006 (gmt 0)

Hi,

Am I the only person who's AdWords timezone is NOT what I set it to, and NOT what it claims to be, and that may go horribly pear-shaped when the clocks go back at the end of the month (one different dates in various places, of course)?

I set my timezone to be GMT+0, ie UTC, since I run all the timing in my system relative to UTC, and, for example, I avoid running too many ads at times when scheduled work makes the systems busier than normal.

AdWords *claims* to be "Time zone for all dates and times in data tables, reports and billing: (GMT+00:00) London" but it isn't. It's currently on BST (British Summer Time, an hour ahead, so resets to zero at 2300 UTC/GMT for example.

Will I get a different-length day when the clocks go back? I need to know if I have to adjust the timing (and possibly budgets) in all my scheduled campaigns on either side of the clock change.

This is particularly irritating as we are not allowed to change our timezone again, and the error is not mine!

AWA, could you possibly take the engineer responsible for this slip aside and tell them about the importance of the difference between GMT and BST, or UTC-based timezones and daylight-saving-adjusted timezones? If s/he is from a place without daylight saving, such as Japan, I almost forgive them. But could the position at least be made clear THIS WEEK?

I put a question in a couple of weeks ago to support, but as far as I can tell it was neither understood nor escalated as I asked it to be.

Rgds

Damon