Timestamps are critical for ensuring accurate data tracking and display in the Verato UI. The way timestamps are handled can vary across different areas of the UI, depending on how data is processed and presented.
This article provides a detailed explanation of how timestamps are managed during data loading, storage, and display, and it also addresses important considerations for custom attributes and timestamp filtering across different UI tabs.
How Timestamps Work in Verato UI
1. Data Loading
When loading data into Verato, any timestamp field values are assumed to be in UTC (Coordinated Universal Time) by default.
Once the data is loaded, the timestamps are stored in UTC in the primary database for the system.
Recommendation:
If the customer data uses a different timezone, it essential to ensure that timestamps are converted to UTC before loading them into Verato. Failing to do so will result in inaccurate timestamps in the system.2. Data Storage
- After the initial data load, timestamps continue to be stored and processed in UTC within the primary database.
- When this data is read from the primary database and loaded into the analytics data warehouse, the UTC timestamp is retained.
- Similarly, any data processed by the systems which power the analytics and reporting within the Verato UI, also read and processes timestamps in UTC.
This ensures consistency throughout the system, so regardless of where the data is stored or processed, the timestamps remain in UTC format.
3. Data Display in Verato UI
The Verato UI displays timestamp data differently depending on which tab the customer is using.
Insights Tab
- The Insights Tab is powered by the business intelligence platform and generates metrics, statistics, and reports based on the analytics data warehouse.
- All data displayed in the Insights Tab is based on UTC timestamps.
- No timezone conversion occurs in this tab, meaning that all reports and metrics are shown in UTC, regardless of the customer's local timezone.
Stewardship Tab
- The Stewardship Tab pulls raw data directly from the primary database.
- Unlike the Insights Tab, the Stewardship Tab converts the stored UTC timestamps into local time based on the timezone of the customer accessing the UI.
- This means timestamps will be displayed in local time on the Stewardship Tab, which helps provide a more relevant view for customers working in different timezones.
Handling Custom Attribute Timestamps
In addition to managing standard timestamp fields, customers may use custom attributes to store additional data. It is important to note that if a customer chooses to store a timestamp in a custom attribute, Verato does not perform any timestamp conversion on that custom attribute.
Key Points:
- No automatic conversion: If a custom attribute contains a timestamp value, Verato will treat the value as a string and will not apply any conversion to UTC or local time. The system does not recognize the value as a timestamp unless explicitly configured.
- Customer responsibility: It is the customer's responsibility to ensure the proper representation of time for custom attributes. If a timestamp needs to be stored in UTC or any other specific timezone, the customer must perform the conversion before submitting the data.
Example
Let’s say a customer uses a custom attribute person_lunchtime with a value of "1:30 PM".
- Behavior: Verato will store this value as "1:30 PM" without interpreting it as a timestamp. No UTC conversion will occur.
- Implication: When retrieved later, the value will be displayed exactly as "1:30 PM", and it will not be adjusted to UTC or local time. If the customer intends for this time to be represented in UTC or another timezone, they must ensure this conversion is done manually before submitting the data.
Cross-Tab Filtering and Timestamp Discrepancies
When filtering data by timestamp on the Stewardship Tab and comparing that data to metrics or reports on the Insights Tab, it is important to understand the timezone differences between these tabs.
Stewardship Tab displays timestamps in local time, while the Insights Tab displays timestamps in UTC.
Discrepancy: If you filter data by timestamp on the Stewardship Tab and then cross-verify it on the Insights Tab, the customer may notice that the numbers or results do not align. This is because the same timestamp is displayed in different timezones depending on the tab (local time on the Stewardship Tab vs. UTC on the Insights Tab).
Recommendation:
- Caution is necessary when cross-verifying timestamp-filtered data between the Stewardship Tab and the Insights Tab.
- Always account for the timezone difference when comparing data between these tabs. Timestamps may need to be manually converted to UTC or local time, depending on the context, to ensure accurate cross-tab comparisons.
Summary
- Data Loading: The customer needs to ensure all timestamps are converted to UTC before loading data into Verato.
- Data Storage: Timestamps are stored and processed in UTC across Verato primary database and analytics data warehouse.
- Data Display: Insights Tab displays timestamps in UTC and Stewardship Tab converts and displays timestamps in local time based on the customer's timezone.
- Custom Attribute Timestamps: Verato does not perform any conversion on custom attributes with timestamp-like values. It is the customer’s responsibility to manage these values.
- Cross-Tab Filtering: The customer should be aware of timezone differences when comparing data between the Stewardship Tab (local time) and Insights Tab (UTC), and adjust timestamps accordingly.
Understanding these nuances will help ensure accurate data representation, storage, and filtering, allowing for more effective data analysis and cross-verification in Verato.