How a user property works
A user property is a name-and-value pair you attach to a visitor rather than to something they did. You set it from your tag, from the Google tag configuration, from Google Tag Manager or from the Measurement Protocol, and GA4 stores it against that visitor’s identifier. From that point on it applies to everything they record, in the current visit and in later ones, until you send a different value.
Because it replaces rather than accumulates, a user property always describes the present state. Plan level, account type, whether someone is a registered customer, which language they chose, which branch or city they signed up at — all of these are natural fits. Once registered as a custom definition in the admin area, the property becomes a dimension you can use in reports, explorations and audience rules.
Why user properties matter
They let you split behaviour by who someone is instead of only by what they clicked. That is usually where the useful finding sits: existing customers behaving differently from first-time visitors, one plan converting on a different page from another, a segment that reads plenty and never enquires.
They also make audiences durable. An audience built on a user property keeps its members between visits because the attribute travels with the person, which is what you want for anything you intend to exclude, nurture or compare over months rather than days. Set alongside your events, they turn a user-scoped view of the data into something you can act on.
Common mistakes with user properties
The largest is privacy. Names, email addresses, phone numbers and anything else that identifies a person directly must never be sent to GA4, and hashing them is not a licence either. If you need a login-based identifier, that is what the User-ID feature exists for, and it needs its own decision and disclosure.
The second is scope confusion. Anything that changes within a visit — the campaign that brought someone in, the page they landed on, the device they used — belongs to session or event scope. Forced into a user property, it produces reports where one label is smeared across visits it never described.
The third is volume. GA4 limits how many user properties a property can register, and values with a very large number of variations are of little use as report rows anyway. The fourth is expecting history: a property applies from the moment it is received and never backfills earlier data.
How to act on it
Start by writing the sentences you want to be able to say about your customers, then work back to the smallest set of properties that would make them true. Three or four well-chosen attributes with tidy, stable values beat a long list nobody maintains.
Send each one as early in the visit as you can, so the events that follow are covered, and check the values in the debug view before you rely on a report. Keep a short written note of every property, what it means and who owns it — that document is the difference between an account that still makes sense next year and one that does not. If you are building this at the same time as events and key events, treat it as part of the GA4 setup plan.
