Event name dimension
In GA4's event-based model every interaction is an event, and the event name dimension is the label that identifies it — page_view, scroll, click, or a custom name. Reports group by event name, so consistent, well-chosen names are the backbone of analysis. Reserved and automatically collected names, plus naming drift across implementations, are the main things that complicate it.
What this means
GA4 treats every hit as an event with a name and optional parameters. The event name dimension is that name: page_view, session_start, scroll, or any custom event you define. Because reports pivot on event name, it is the primary key for interaction analysis.
Reserved names and discipline
GA4 automatically collects some events and reserves certain names; reusing a reserved name for a custom event causes conflicts. Enhanced measurement adds its own events (scroll, click, file_download) you may not have defined. The bigger risk is human: 'signup', 'sign_up', and 'Signup' are three different rows. A documented naming convention keeps the dimension coherent.
- Every interaction is a named event
- Reserved/auto-collected names can collide with custom ones
- Inconsistent naming fragments reports
How it appears in analytics and logs
An event name value is the label your tag attached to an interaction. Unexpected event names usually mean an automatic/enhanced-measurement event or an inconsistent custom name, not a new behaviour.
Diagnostic use case
Use event name to slice interactions by type, enforcing a single naming convention and avoiding collisions with reserved or auto-collected event names.
What WebmasterID can help detect
WebmasterID records interactions as named first-party events, so you can read interaction types by name without third-party tracking and keep naming consistent across pages.
Common mistakes
- Reusing a reserved GA4 event name for a custom event.
- Letting naming drift (signup vs sign_up) split one event.
- Forgetting enhanced-measurement events you did not define.
Privacy and accuracy notes
Event name labels an interaction type, not a person. Parameters on the event can carry data, so they — not the name — are where PII review belongs.
Related pages
- Custom events: tracking what matters to you
Custom events capture meaningful actions a pageview cannot — a CTA click, a signup, a video play, a form submit. The value is in a consistent naming taxonomy and well-chosen properties. The risk is putting personal data into event names or properties, which turns analytics into surveillance. This page covers both.
- The page_view event: the base of web analytics
page_view is the event fired when a page loads. It is the base of almost every web-analytics model: sessions, pageviews, and most reports build on it. In classic sites the tracker fires it automatically on load; in single-page apps you fire it on each route change. Its properties (path, title, referrer) drive most downstream reports.
- Page path dimension
The page path dimension is the path portion of a viewed URL — /blog/post — excluding the hostname and, by configuration, the query string. GA4 derives it from the page_location of each page_view. It is hit-scoped, so it counts every view of a page, and the most common pitfall is query strings (utm_*, session IDs) fragmenting one logical page into many distinct paths.
- Event Explorer
Browse interactions grouped by event name.
Sources and verification notes
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.