Time zone appears to be set to spain, so when I refresh a query on the morning of the 27th, I can't see data for the 26th until 10am Sydney Time as it's not the 27th in Spain until then.
I also had an issue where when pulling the last 120 days and manually refreshing each query one by one, only one day of data was being pulled.
The timezone should correspond to the user, so if the user is in Aus, the AU=us timezone should be used.
Hi all, for these 3 datasources (Bing, DV360 and Criteo) we can configure the calls to their APIs by sending a timezone. We have thought of sending the timezone of the spreadsheet.
As an example. Bing has by default the timezone of "PacificTimeUSCanadaTijuana". If you are in Australia on 30/10 and in Tijuana on 29/10, if you make a data call to Bing for that day (30), it will not return data, unless you indicate that the call is for the 30th timezone Australia.
Do you want us to configure the calls to these APIs by sending the corresponding timezone, or do we leave the calls as they are now?
Thanks for your email.
We have set the time zone to the same it’s on the spreadsheet you are using, so makes more sense. Now we need to check the consistency with all datasources. It appears that there are ones we can use based on the initial setup per account like GA but there other API that depends on the timezone you want
We will update you tomorrow with more information
consider a defaul timezone that the user can chanrge, they might need to run a report in a different zone for international clients