Custom Dimension
AnalyticsAlso: Custom Attribute · User Property
Quick definition
A custom dimension is a label you define and attach to analytics data to add context that Google Analytics 4 (GA4) does not collect by default. Examples include a user's membership tier, the content category of a page, or whether a visitor is a logged-in customer. Custom dimensions let you segment and filter reports in ways the platform cannot do on its own.
How it varies across Australia
Most Australian businesses running GA4 have the default dimensions active and nothing more. The gap between what they could know and what they actually track widens as their product or site grows more complex. Businesses that invest in custom dimension setup tend to have significantly richer segmentation available when they need it for attribution and conversion decisions.
See data and tracking maturity across Australian industries →The three scopes
Attached to a single event. The most common type. Use for things like content category, button label or form name.
Attached to a user profile and persists across sessions. Use for things like membership tier, account type or cohort.
Attached to an ecommerce item in a transaction. Use for things like product category, brand or variant.
What it actually means
Google Analytics 4 (GA4) collects a baseline set of information about every visit: the page, the device, the traffic source, the country. What it cannot collect automatically is anything specific to your business model. Whether a visitor is a free or paid user. Which editorial team wrote the article they read. Whether the session happened inside a native app or a web view.
Custom dimensions fill that gap. You define them, you name them, and you pass the value through the data layer or directly in your GA4 event. Once registered, they appear as filterable columns in your reports and are available in every downstream tool that reads GA4 data, including Looker Studio and BigQuery.
The value of custom dimensions compounds over time. The earlier you set them up, the more historical segmentation you have when you eventually need to answer a harder question. A business trying to compare the conversion rate of free-tier versus paid-tier users, for example, cannot answer that question without a user-scoped custom dimension recording the tier at session start.
Custom dimensions sit inside the Data & Tracking dimension of how we score businesses. They are one of the clearest signals of whether an analytics setup is mature or just switched on. Having GA4 installed is table stakes. Using custom dimensions to capture business-specific context is where the work begins.
Default analytics tells you what happened. Custom dimensions tell you who it happened to and why it matters.
How it shows up
Custom dimensions show up in GA4 reports as additional breakdown options when you explore data. You add them as a secondary dimension in a standard report, or build them into an exploration to cross-reference behaviour by segment.
They also pass through to BigQuery exports if you have the GA4 BigQuery link enabled, which means every custom dimension you register becomes a queryable field in your raw event data. That is where the real power sits for businesses doing more sophisticated attribution or lifetime value analysis.
The Australian context
Australian privacy obligations under the Privacy Act and the Australian Privacy Principles (APPs) apply directly to custom dimensions. If a custom dimension value could identify an individual, even indirectly, sending it to GA4 creates a compliance exposure. The most common mistake is passing user IDs, email hashes or CRM identifiers as custom dimension values without a legal basis for doing so in a third-party analytics tool.
The Privacy Act amendments currently moving through Parliament are likely to tighten requirements around exactly this kind of first-party data flowing to third-party platforms. It is worth reviewing your custom dimension values against your privacy policy before the amendments pass.
Where people get this wrong
Related terms
Common questions
How many custom dimensions can I have in GA4?
The standard GA4 property limit is 50 event-scoped custom dimensions and 25 user-scoped custom dimensions. GA4 360 (the paid tier) raises those limits significantly. Once you hit the cap, you cannot register new ones without deleting existing ones, which removes historical reporting for that dimension.
Do custom dimensions work retroactively?
No. GA4 only attaches a custom dimension value to events collected after you start passing it. Data collected before you set the dimension up has no value for that field. This is the main reason to implement custom dimensions early rather than after you realise you need them.
Can I use custom dimensions in Google Ads?
Yes, if you have your GA4 property linked to Google Ads. Custom dimensions registered in GA4 become available as audience conditions and remarketing signals in Google Ads, which is one of the more powerful downstream uses.
What is the difference between a custom dimension and a UTM parameter?
A UTM parameter is a URL tag that tells GA4 where traffic came from. A custom dimension is data you define about the user, session or event itself. UTM parameters feed into acquisition reports. Custom dimensions feed into behaviour and audience reports. They serve different purposes and are often used together.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →