Date and time dimensions
Date and time in GA4 are a family of dimensions — date, hour, minute and combinations — that stamp each event with when it occurred, expressed in the property's reporting time zone rather than the visitor's local time or UTC. They are the backbone of every trend line. Because the boundary of a 'day' depends on the configured time zone, changing it shifts which events fall on which calendar date.
What this means
GA4 derives several time dimensions from each event's timestamp: date (YYYYMMDD), plus hour, minute, and composite fields. All are computed in the property's reporting time zone, the single clock GA4 uses to bucket events.
These dimensions are what every time-series report, cohort, and intraday chart is built on.
Why time zone matters
Because the day boundary is defined by the property time zone, an event at 23:30 local-UTC can land on a different calendar date than another tool using UTC or the visitor's zone would record. GA4 also does not retroactively reprocess history when you change the time zone — only data after the change uses the new clock.
This is the most common reason daily counts differ from server logs or a second analytics tool.
- Derived in the property reporting time zone
- date, hour, minute and composite fields
- Time-zone changes are not applied retroactively
How it appears in analytics and logs
A date/time value places an event on the property's clock. A daily total that disagrees with another tool usually reflects a different time-zone setting or day boundary.
Diagnostic use case
Use the date and time dimensions to build trend lines and intraday patterns, remembering every value is in the property's reporting time zone.
What WebmasterID can help detect
WebmasterID timestamps events first-party in a consistent zone, so trend comparisons across tools are reproducible without third-party tracking.
Common mistakes
- Assuming GA4 dates are in UTC or visitor-local time.
- Expecting a time-zone change to reprocess historical data.
- Comparing GA4 daily totals to a UTC tool without adjusting.
Privacy and accuracy notes
Date and time describe when an event happened, not who triggered it. WebmasterID records event timing first-party without attaching it to a personal profile.
Related pages
- Date dimension
Date is the dimension that records the calendar day of an event in YYYYMMDD form, computed in the GA4 property's reporting time zone. It is the default x-axis of most trend reports. Its day boundary is the property's midnight, not UTC or the visitor's clock, so the same raw event can be assigned to a different date than another tool would choose.
- Hour dimension (absolute)
Hour is the dimension that buckets events into a specific date-and-hour in the property reporting time zone — an absolute point on the timeline, like '2026-06-24 14:00'. It differs from hour of day, which collapses every day's 2pm together for daypart analysis. Absolute hour is for following one continuous span; hour of day is for recurring behavioural patterns. Confusing the two produces wrong conclusions.
- Day of week dimension
Day of week is the dimension that groups events by weekday (Sunday through Saturday, or a 0-6 index) so you can see weekly patterns. It is derived from each event's timestamp interpreted in the property's reporting time zone. The big caveat: weekday boundaries depend on that time zone, so a global audience spanning many zones will have its 'days' defined by your reporting clock, not theirs.
- Web analytics
Build reproducible trend lines first-party.
Sources and verification notes
- Google Analytics Help — [GA4] Dimensions, metrics, and other termsLists time dimensions; reporting time zone governs bucketing.
- GA4 Data API — Schema (time dimensions)Documents date, hour, minute and related dimensions.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.