|AdWords TimeZone not as set/reported.|
Is this only me? What happens when clocks go back?
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.
|This is particularly irritating as we are not allowed to change our timezone again. |
Do you have a rep? If so, it is possible to change the setting through your rep after the fact (if you ask really, really nicely).
I don't have a rep. I'm sure that I don't spend enough by at least 10x to get one!
Paging AWA! B^>
|...This is particularly irritating as we are not allowed to change our timezone again, and the error is not mine! |
This can be adjusted once by the support team, DamonHD, so contacting AdWords support should have done the trick for you in terms of changing it around. I apologize that they have not responded. It might be worth checking your filtered email to see if a response may have been sent to a spam folder for some reason. And also worth writing in once again.
|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? |
Unfortunately, I've been able to spend very little time onWebmasterWorld for the past week or so, due to lots going on in other areas. So I'm seeing this request for the first time just now - and to set reasonable expectations, I doubt I can get updated on this by the end o' today. But I'll certainly make a start.
Oh my! Calling in the big guns, eh?!
AWA2, feel free to jump in any time you like. I won't limit you to one post a month as I've done in the past. And I'll even have your computer returned. ;)
The issue is not simply one of getting my current setting adjusted, it's the whole issue of whether the timezone randomly gets some unrequested/unwanted daylight-savings adjustment done, which means it wanders by an hour twice a year.
I want fixed, non-adjusted, GMT+0 times, which is what I selected, and what I'm being told I've got, but is not what is actually happening. If I'd been offered "GMT/BST London-local time" which might be right for many people, I'd still have selected "GMT+0". Note that you may also end up with an internal systems problem at G/AW with the 23/25hr days as daylight savings comes and goes, so I suggest that this needs an urgent investigation to avoid a glitch in a week-or-so's time!
This is a matter of clear thinking, and doing what it says on the tin! B^>
No point in using up more support time until we know what is going on inside the tin. Find that engineer!