Reporting Timezone
Configure the workspace timezone and understand reporting dates, source timezones, and schedules.
Last reviewed July 13, 2026
The workspace timezone determines how supported reports and queries bucket timestamps into calendar dates. Source accounts and individual schedules can also carry their own timezones.
Configure the Workspace
- Open Workspace Settings → Account.
- Find Regional Settings.
- Select an IANA timezone.
- Save the change.
The current selector is the source of truth for supported identifiers. Its displayed offset is calculated for the current date and can change with daylight saving time.
Three Timezone Concepts
| Concept | Purpose |
|---|---|
| Event timestamp | The absolute instant recorded by the source, commonly stored in UTC |
| Source account timezone | The provider’s calendar boundary for daily platform data |
| Workspace reporting timezone | Vendo’s calendar boundary for supported reports and metric queries |
Do not convert a timestamp by adding a fixed offset. Use the IANA timezone so daylight saving and historical changes are handled correctly.
Scheduling
A source schedule can include an anchor time and anchor timezone. That timezone controls when the job is due; it does not necessarily change how provider data is dated. Confirm both the schedule and the reporting timezone when investigating an apparent one-day shift.
Validate
Choose records around midnight and a daylight-saving boundary. Compare the original timestamp, provider date, reporting date, and dashboard filter. Record which definition the business expects before changing settings.
Troubleshooting
| Symptom | Check |
|---|---|
| Record appears on adjacent day | Source timezone, workspace timezone, and timestamp type |
| Job runs at unexpected local time | Anchor timezone and daylight-saving transition |
| Platforms disagree by day | Each provider’s reporting boundary and attribution rules |
| Timezone unavailable | Exact IANA identifier in the current selector |