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.
What this means
This dimension concatenates date, hour, and minute into one value in the property time zone, giving the finest time bucket available in standard GA4 reporting. It is the natural axis for watching a narrow window unfold minute by minute.
For anything longer than a few hours, coarser grains like hour or date are easier to read.
Latency caveat
GA4 processing is not instantaneous, so the most recent minutes can appear incomplete and then fill in as data finishes processing. A dip in the latest minutes is often latency, not a real drop, and should not trigger alarm on its own.
For true second-by-second live views, GA4's Realtime report is the intended surface; the minute dimension is for after-the-fact granular analysis.
- Per-minute timestamp in property time zone
- Finest standard reporting time grain
- Recent minutes can lag due to processing
How it appears in analytics and logs
A date-hour-minute value pins an event to a specific minute. Sparse or delayed minutes can reflect processing latency rather than an actual absence of traffic.
Diagnostic use case
Use date hour and minute to monitor short, time-critical windows like a launch or incident, where you need per-minute resolution in property time.
What WebmasterID can help detect
WebmasterID can surface per-minute event timing first-party for launch and incident monitoring, without third-party tracking.
Common mistakes
- Treating processing latency in recent minutes as lost traffic.
- Using minute granularity for long date ranges that overwhelm reports.
- Confusing this dimension with the Realtime report.
Privacy and accuracy notes
This dimension records precise timing, not identity. WebmasterID records minute-level timing first-party without attaching it to a person.
Related pages
- 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.
- 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 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.
- Website observability
Per-minute monitoring of launches and incidents.
Sources and verification notes
- Google Analytics Help — [GA4] Dimensions, metrics, and other termsLists combined date/hour/minute time 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.