Search…
Time Zones
Configure time zones for collections and tile
Verb attempts to convert time-based data when your data is ingested. By default, time-based data is stored in Universal Coordinated Time (UTC). While a UTC format will work for the vast majority of scenarios, there are situations where the output data needs to be converted to a given time zone instead of UTC. To convert the data, use the transformation feature to create a calculated column or data view in the model. Verb provides a Convert Time Zone transformation step.

End-User Time Zone Conversion

The time zone picker can be displayed to end-users so that they may convert data to their preferred time zone.
End-Users will view this option from the date filter if one is displayed. If there is no date filter displayed then the time zone picker will display as a button in the filter area.
The menu will show UTC selected by default and the end-user's local browser time will be listed as the second menu option.
The time zone list contains a complete list of standard global time zones as well as common aliases such. For example, both "America/Chicago" and "US/Central" will render a report with a time zone offset of -6 (or -5 hours depending on whether daylight saving time is in effect) from UTC.

Programmatic (SDK) Conversion

To convert the time zone programmatically, pass the preferred time zone into the x-timezone property in the SDK. Time zone codes will follow ISO standards.
SDK Embed Code

Collection Specific Details

Dashboard Collections

To configure end-user time zone controls on a dashboard collection go to the Filters Tab and turn on the Time Zone Conversion toggle at the bottom of the panel.
Programmatic options are available on dashboard collections regardless of the Time Zone Conversion toggle configuration.

Contextual Tile Collections

Contextual Tiles only allow for programmatic conversion of the time zone via the SDK.

API Collections

API collections will always present data in UTC.

What if Data is Not in UTC in My Data Source?

Verb assumes that all date-time information is in UTC upon ingestion and when data is presented in a collection it will be shown as though it is UTC.
If the data is not stored in the source as UTC then it's important to convert it to correctly show date-time information. To convert the data, use the transformation feature to create a calculated column or data view in the model. Verb provides a Convert Time Zone transformation step.
Copy link
Outline
End-User Time Zone Conversion
Programmatic (SDK) Conversion
Collection Specific Details
What if Data is Not in UTC in My Data Source?