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.
What this means
The date dimension is GA4's per-day bucket, formatted YYYYMMDD and derived from each event's timestamp using the property reporting time zone. Almost every default trend line uses it as the time axis.
It is the coarsest commonly-used time grain and the one most reports default to.
Day-boundary effects
Because the boundary is property midnight, events near midnight can fall on either side depending on the configured zone, and totals can differ from a UTC-based system. Switching the property time zone changes future bucketing but does not rewrite historical dates.
For cross-tool reconciliation, align the day boundary before comparing daily numbers.
- Format YYYYMMDD in property time zone
- Default axis of daily trend reports
- Boundary is property midnight, not UTC
How it appears in analytics and logs
A date value is the property-time-zone calendar day of an event. A mismatch with another tool's daily figure usually traces to a different day boundary.
Diagnostic use case
Use the date dimension for daily trend reporting, knowing each event is bucketed by the property time zone's midnight rather than UTC.
What WebmasterID can help detect
WebmasterID assigns each event a consistent calendar date first-party, so daily comparisons stay stable across reports.
Common mistakes
- Assuming date is in UTC.
- Comparing to a UTC tool without aligning the day boundary.
- Expecting a time-zone change to restate past dates.
Privacy and accuracy notes
The date dimension records when, not who. WebmasterID records the event date first-party without linking it to an individual.
Related pages
- 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.
- Week dimension
Week is the dimension that groups events by the numbered week of the year (01–53). In GA4 the week begins on Sunday, so the first and last weeks of a year are usually partial. It smooths daily noise into a steadier trend, but the Sunday boundary and partial-week edges mean its counts are not directly comparable to ISO-week tools that start on Monday.
- Month dimension
Month is the dimension that groups events by calendar month (01–12) in the property time zone. It is the coarse grain for seasonal and budget-cycle reporting. Its main pitfall is that months have different lengths, so raw month-over-month comparisons mix a 28-day February with a 31-day March, which can masquerade as a trend if you do not normalise per day.
- Web analytics
Daily trend reporting first-party.
Sources and verification notes
- Google Analytics Help — [GA4] Dimensions, metrics, and other termsDefines the date dimension and reporting time zone.
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.