Data area, time and data retention
Product Introduction And Core Concepts: Data area, time and data retention
A correct understanding of Regions, time fields, and data retention periods is a prerequisite for accurately reading overview indicators, event records, visitor statistics, and risk trends.
Compliance significance of Region
Region determines the storage and computing area of application data, and is also the isolation boundary for server keys and Webhooks.
- An application can only belong to one Region.
- Applications in the same Region share the server key of the Region.
- Webhook can only be bound to applications in the same Region.
- Event and visitor queries should be executed in an explicit App × Region context.
- The console will not summarize the data of all Regions under the organization. When viewing other regions, please switch to the corresponding Region first.
Console statistics time zone
The console uses UTC+0 for daily statistics. “Today” therefore means from UTC+0 00:00:00 to the current time, which may differ from the calendar day in your location.
When viewing day-level metrics or selecting a query date, understand the time range in terms of UTC+0. For example:
Today (UTC+0)
2026-08-25 00:00:00 to the current timeServer reception time and customer business time
| time | what does it mean | how you can use |
|---|---|---|
| Geelab server receiving time | The time Geelab received the identification request | Filter and sort events in the console, view statistical metrics, and locate an identification request |
| Customer business hours | The time your application or server records and saves business data with it | Align identification events with orders, logins, or other business actions |
Use request_id to pinpoint a specific identification request.
Customer business time comes from your business system and may be affected by the client clock, the time zone used, or network latency. When comparing business logs, please confirm the source and time zone of this time, and use it differently from the time received by the Geelab server.
The webhook delivery log also records the delivery time. There may be a gap between event reception time and Webhook delivery time due to processing and network transmission. When troubleshooting delivery issues, please check the events separately request_id, server reception time and Webhook delivery time. The current version will not automatically retry after failure.
Package data retention period
The event details and visitor statistics that can be queried by the console are limited by the package data retention period, such as the last 30 days or the last 90 days. The actual retention period is based on the current organization package and console prompts.
event list
Events that have exceeded the retention period may no longer be queried in the event list, and full event details cannot be opened through the Request ID.
Visitor first appearance time
Visitor’s last visit time
The latest access time indicates the time when the device was last recognized within the current queryable data range.
Number of visitor events and risk signals
Risk trends and comparisons
Trends and cycles may be incomplete if the selected time range or previous period exceeds the data retention period. When you see the prompt "Incomplete data" or "No data from the previous period", please narrow the scope of the query and do not interpret missing data as zero.
Advice when reading data
- Before querying events, first confirm the current organization, application, region and time range.
- When comparing business logs, confirm the time field and time zone used by both parties.
- When looking at the "Date of First Occurrence", pay attention to whether it has a "storage period" qualification.
- When investigating risk signals, continue from summary cards into specific events and don’t just look at aggregate numbers.
- When long-term auditing is required, external log or data archiving should be planned according to enterprise requirements and the console should not default to permanently saving all events.