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.
What this means
The hour dimension assigns each event a unique date-and-hour bucket in the property time zone, placing it at one absolute point on the calendar. It is the grain for following an unfolding span — a campaign day, an incident window — hour by hour without daily smoothing.
Each value occurs once in the data; there is no folding across days.
Absolute hour versus hour of day
Hour of day is a recurring 0–23 field that aggregates every day's same clock hour to reveal dayparts; absolute hour keeps each hour distinct on the timeline. Use absolute hour for trend continuity and hour of day for 'when in the day are people active?' patterns.
Mixing them — reading an absolute-hour chart as a daypart pattern, or vice versa — leads to misattributed peaks.
- Unique date+hour bucket in property time zone
- One occurrence per value, no day folding
- Contrast with recurring hour-of-day
How it appears in analytics and logs
An hour value is one specific calendar hour. If a pattern repeats every day at the same clock time, you likely want hour-of-day instead of absolute hour.
Diagnostic use case
Use the absolute hour dimension to trace a single continuous timeline hour by hour, rather than the recurring daypart view that hour-of-day gives.
What WebmasterID can help detect
WebmasterID can bucket events into absolute hours first-party, supporting timeline analysis without third-party tracking.
Common mistakes
- Reading absolute hour as a recurring daypart pattern.
- Using hour for very long ranges that crowd the report.
- Forgetting the property time zone defines the hour bucket.
Privacy and accuracy notes
The hour dimension records timing, not identity. WebmasterID records hourly timing first-party without profiling visitors.
Related pages
- Hour of day dimension: intraday timing patterns
Hour of day is the dimension that buckets events into one of 24 hours (00-23) so you can read intraday rhythms — when traffic peaks, when conversions happen. Like day of week, it is computed from the event timestamp in the property's reporting time zone. Daylight-saving transitions and a globally distributed audience both complicate it: the hour is your clock's hour, not the visitor's.
- Date hour and minute dimension
Date hour and minute is the dimension that combines calendar date with the hour and minute of an event into a single per-minute timestamp, expressed in the property reporting time zone. It is the finest standard time grain GA4 offers in reports and is built for tight, short-window monitoring — a launch, an outage, a flash sale — where hour-level detail is too coarse.
- 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.
- Web analytics
Hour-by-hour timeline analysis first-party.
Sources and verification notes
- Google Analytics Help — [GA4] Dimensions, metrics, and other termsDistinguishes absolute hour from recurring hour-of-day.
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.