Custom dimension
A custom dimension lets you report on an attribute GA4 does not collect by default — author, plan tier, content type — by registering an event or user parameter as a dimension. It must be defined before data flows, has event-scoped and user-scoped variants with quota limits, and is vulnerable to high cardinality: registering a near-unique value collapses reports into '(other)' and can edge toward identifying users.
What this means
Custom dimensions extend GA4 with attributes specific to your business. You attach a parameter to events (or set a user property), then register it in the admin so it becomes a reportable dimension. Event-scoped custom dimensions describe a single event; user-scoped ones describe the user across sessions.
Scopes, limits, and cardinality
Registration is not retroactive: a custom dimension only has data from when it was registered, so historical reports are empty. There are quotas on how many you can register per property and per scope. The biggest trap is cardinality — registering a parameter with very many distinct values (an ID, a timestamp) overflows the report into an '(other)' bucket and risks carrying identifying data. Keep custom dimensions low-cardinality and free of PII.
- Register before collection — no retroactive data
- Event-scoped and user-scoped, each with quotas
- High cardinality => '(other)' grouping and privacy risk
How it appears in analytics and logs
A custom dimension value is whatever parameter you registered. Empty history before the registration date, or an '(other)' row, signals late registration or a high-cardinality parameter, not lost data.
Diagnostic use case
Use custom dimensions for low-cardinality business attributes, registering them ahead of collection and avoiding near-unique values that trigger '(other)' grouping.
What WebmasterID can help detect
WebmasterID supports first-party custom attributes for business reporting while steering away from high-cardinality or identifying values that would compromise privacy.
Common mistakes
- Expecting data before the dimension was registered.
- Registering a high-cardinality parameter that overflows to '(other)'.
- Putting PII into a custom dimension value.
Privacy and accuracy notes
Custom dimensions can accidentally carry PII if you register the wrong parameter. WebmasterID treats custom attributes as opt-in and warns against high-cardinality, identifying values.
Related pages
- 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.
- Content grouping
Content grouping is a custom dimension that classifies pages into editorial groups — Blog, Product, Docs — so you can report by content type instead of one URL at a time. In GA4 it is populated by sending a content_group parameter on the page_view event. Because it is event-scoped and only as good as the values you send, untagged pages fall into '(not set)' and inconsistent naming fragments the report.
- 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.
- Event Explorer
See the parameters behind a custom dimension.
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.