Supermetrics Support Forum

Twitter Ads Error: Expect Time to Be Midnight in the Account's Local Timezone

This guide applies to the follow error for Twitter Ads connectors and the Twitter Ads part of the Ad Data + GA connector for Data Studio:

Query failed: Expect time to be midnight in the account's local timezone for day granularity

This error is due to issue with the timezone handling in the request for data from Twitter's API. We added a feature now to allow the user to define the timezone explicitly, which should resolve this error when it arises.

For Google Sheets

The timezone is defined by the Sheet's properties. To check and change that, please see this guide:

https://support.google.com/docs/answer/58515?co=GENIE.Platform%3DDesktop&hl=en

Though you can set it to any timezone, we recommend that you set it to the Twitter ad account's defined timezone.

Note: This setting also determines when scheduled refreshes (aka triggers) run. If you change this value, you may need to check your triggers - if they need to be adjusted as well, delete and recreate the trigger to have it set to the new timezone settings for the file.

For Data Studio

You can set the timezone in the data source main configuration under the Reporting timezone drop-down.

Blue box around "Reporting timezone" option

Though you can set it to any timezone, we recommend that you set it to the Twitter ad account's defined timezone.

For Excel

The timezone for the Excel Online file is defined by the Office 365 settings for the Microsoft user account. To check and change that, please see this guide:

https://support.office.com/en-us/article/change-your-display-language-and-time-zone-in-office-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b

If using Excel for Desktop, the timezone is defined by the local computer's date/time settings.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.