Analytics and Tracking

User-Scoped

Also called User scope, user-level dimension

A dimension that belongs to the person rather than one visit, so it applies to every session they record.

Quick facts: User-Scoped

Category
Analytics and Tracking
Also called
User scope, user-level dimension
Level
Intermediate
Affects
Report accuracy, audience durability, segment definitions
Where to see it
GA4 (Admin, Custom definitions, Explorations), Google Tag Manager
In this article4
  1. How user-scoped dimensions work
  2. Why user scope matters
  3. Common mistakes with user scope
  4. How to act on it

How user-scoped dimensions work

Every dimension in GA4 is attached to something: a single event, the visit it happened in, an item in a basket, or the person themselves. User scope is the widest of those. Once a user-scoped value is set, GA4 holds it against that visitor’s identifier and applies it to everything they do from then on — in that visit and in the visits that follow.

Most of the time you set one yourself through a user property sent from your tag. Membership tier, account type, whether someone has bought before, which branch they registered at — anything that describes the person rather than the moment belongs here. GA4 keeps the most recent value it was given, so user scope holds a current state, not a history of changes.

Why user scope matters

Scope decides what a report is allowed to say. Break your sessions down by a user-scoped dimension and every session that person recorded lands in the same bucket, including sessions from before the value was ever set. That is exactly right for questions about people — how many existing customers came back this month — and quietly wrong for questions about moments, such as which campaign drove a particular visit.

It also decides how durable an audience is. An audience built on user scope keeps its members across visits, because the attribute travels with the person rather than expiring when the session ends. That is what makes user scope worth the effort for anything you intend to target, exclude or compare over a long period.

Common mistakes with user scope

The first is putting something at user scope that genuinely changes within a visit. Traffic source, landing page, product category and device all describe a moment, so they belong at session or event scope; forcing them to user scope produces reports where a single label is smeared across visits it had nothing to do with.

The second is expecting it to work backwards. Registering a property today does not relabel yesterday’s data, and there is no rebuild. The third is cardinality and privacy: GA4 limits how many user properties a property can register, so an identifier with a huge number of distinct values will crowd the list and start collapsing into an “other” row. Names, email addresses and phone numbers must never be sent at all.

How to act on it

Start from the question, not from the data you happen to have. Write down the sentence you want the report to complete — “customers on the premium plan convert differently from free users” — and only then decide whether the attribute in it belongs to the person, the visit or the event. If it belongs to the person, register it as a user property before the traffic you care about arrives.

Keep the list short and stable. A handful of well-chosen user-scoped dimensions, each with a small set of tidy values, is more useful than a long list nobody trusts. If you are setting this up alongside events and conversions for the first time, treat it as part of the GA4 measurement plan rather than a later addition.

Do and do not

Do

  • Decide the scope from the question you want answered
  • Register user properties before the traffic you want to measure
  • Keep values short, tidy and small in number

Do not

  • Put traffic source or landing page at user scope
  • Expect a new user property to relabel older data
  • Send names, emails or phone numbers as property values

Questions people ask about this

Is a user-scoped dimension the same thing as a user property?

Close, but not identical. A user property is the mechanism you use to send a value into GA4; user scope is the reporting behaviour that value then has. Every user property is user-scoped, but GA4 also holds user-scoped dimensions of its own that you never send, such as the first campaign that brought someone to the site.

Will setting a user property change my older reports?

No. GA4 applies the value from the moment it receives it and does not go back and relabel earlier events. Register a membership tier today and last month's sessions stay unlabelled. Plan the properties you want before a launch or a campaign rather than after it, or accept a gap when you compare periods.

Can I use a user-scoped dimension to build an audience?

Yes, and it is one of the better reasons to set one. Because the value stays attached to the person, an audience built on it keeps its members across visits instead of losing them when a session ends. That makes user scope a sensible home for anything you want to target or exclude over a long period.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.