Add Timezone Selection Support for Data Sources and Presets in Windsor#1308

Currently, Windsor uses the timezone defined by each data source (e.g., Facebook Ads account timezone) and aligns presets like last_1dT to UTC. This causes issues for clients in non-UTC timezones, as data for the current day may appear incomplete once UTC rolls over, even though their local day is still active.

Clients have requested the ability to override or select a timezone directly within Windsor’s connector settings or at the date preset level. This would allow them to ensure that “today’s data” always reflects their business timezone without needing to over-fetch (e.g., using last_2dT or last_3dT).

Request

Add support for timezone selection in Windsor connectors, enabling users to:

Set a custom timezone per data source or task.

Have date presets (last_1dT, last_7dT, etc.) respect that selected timezone.

facebook code