Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: Extensions
-
Fix Version/s: None
-
Component/s: AdMax
-
Labels:None
Description
Caitlyn found an issue related to the timezone used in setting the start/end date in BudgetOrderService. I made the fix @ https://github.com/thesearchagency/core/commit/a34a9593343f9f201d9ca3eef37a706248dc4dc1
Basically the timezone must be America/Los_Angeles, despite the timezone of the account. This is a change from v13. I found a blog post about this @ https://groups.google.com/forum/?fromgroups#!topic/adwords-api/_5u04EsITRQ[1-25]
In screenshot_sydney_time, you can see the time is Sydney is 1:51am (Optus is in Sydney time).. note, this screenshot was taken during the second ADS call.
In screenshot_adwords_wrong, the timezone used in the BudgetOrderService is Sydney/Australia. As you can see, the start date of the budget is incorrect. It should be 1:43am (not 6:43pm). The budget is also set to pending because it isn't 6:43pm in Sydney yet.
In screenshot_adwords_correct, the timezone used in BudgetOrderService is America/Los_Angeles. As you can see, the start date of the budget is correct. It reads 1:51am and the budget is active.
Please test this in Yell and make the change if the bug is reproducible.
