# Change data source time zone Setting the correct time zone for your data source ensures that the date ranges you select in the app accurately match the data stored in the system. For example, if your marketing platform reports data in Eastern Time but your account is set to Pacific Time, setting the correct time zone eliminates discrepancies and prevents your visualizations from showing empty or misleading data. ## Change data source time zone You can change the time zone of a data source from either of the following locations: - [Data Manager > Data Sources](https://app.databox.com/data-manager/data-sources) - [Account Management > Data Manager > Data Sources](https://account.databox.com/data-manager/data-sources) To change the time zone: 1. Find the data source and click the down caret next to it. 2. Select **Change time zone**. 3. Choose a time zone from the dropdown list, or click **Use my time zone** to apply your profile time zone. 4. Select **Apply to all datasets** to apply this time zone to all [datasets](/understanding-datasets) from this data source. 5. Click **Save** to apply the changes. change-time-zone The change time zone option is unavailable when the integration only provides data in a fixed time zone set by the external provider. This is indicated by the presence of a specific time zone in the **Specification** section of the **Technical Details** tab on the integration's [Metric Library](https://databox.com/metric-library/) page. ## Considerations ### How time zone information is set When you add a new data source, Databox tries to detect its time zone by extracting information from the integration's API. If the integration provides this data, it's saved and used as the data source's time zone within Databox. If no time zone info is available from the integration, Databox defaults to the **profile time zone of the user** who connected the data source. ### How data is stored All synced data is stored locally in **UTC**, along with the original time zone offset when available. Storing timestamps in UTC ensures consistency across all data sources. However, because of this, **time-based filters and visualizations rely on the data source time zone setting** to translate UTC timestamps into the correct local time when querying and displaying your data. ### How time zones affect date ranges and filtering Thedata source time zone setting defines how Databox interprets the start and end of selected date ranges for that data source. For example, if your report shows data for "Today" and the data source time zone is set to Pacific Time, Databox will query data from midnight to midnight Pacific Time — even though the underlying data is stored in UTC. This ensures that filters and visualizations match the local time context of the data source. ### What happens when you change the data source time zone Changing the data source time zone affects how previously synced data is queried and displayed. Since the stored timestamps are aligned with the original time zone, switching to a different time zone can cause: - Empty or missing visualizations - Apparent loss of historical data - Date shifts or mismatches This happens because the system interprets date ranges differently after the change, leading to mismatched queries. If this occurs, **reverting the data source time zone** back to its original setting will restore the previously visible historical data. ### Multiple time zones involved and why they matter When validating synced data, it's important to consider several time zones: - Your local device's time zone — may affect how dashboards appear across tools - Your account's time zone in the external app (e.g., Google Ads, HubSpot) - The time zone used by the external app's reporting interface — might be fixed or adapt to your device - The time zone the external API returns data in — varies by provider - UTC storage in Databox — all data is stored in Coordinated Universal Time for consistency - The data source time zone setting in Databox — used to interpret date ranges when filtering and visualizing Ideally, these time zones align or are at least understood clearly when comparing data. Misalignments can cause confusion — such as seeing different values for the same metric depending on where or when you view the data. Yes, Databox automatically adjusts for Daylight Saving Time in time zones that observe DST, ensuring your data reflects the correct local time throughout the year. It's best to set the data source time zone immediately after adding your data source and **before any data sync occurs**. Changing it later can lead to issues such as missing or mismatched data, as described above. Admins can set the data source time zone for all applicable data sources. Users with User or Editor roles can only set the time zone for data sources they added.   Ask Genie Get instant answers or help with your data using the in-app AI assistant. Talk to an expert For customers: Get help with your setup, strategy, or making the most of Databox. Book a demo New to Databox? See how it works and get guidance on getting started. Send an email Reach out to support for help with your account, data, or technical issues.