termData, experimentation & growth

User Property

An attribute associated with a user or account and applied across their product activity until it changes.

Download Markdown (.md)

01What it means

A user property describes a useful characteristic of a user, device, account, or group, such as plan, region, role, or acquisition source. It may persist across events but can change over time; analysis must distinguish the value at event time from the latest value.[1][2]

02Why it matters

User properties support segmentation and cohort comparison, helping teams understand which populations experience different behavior or outcomes.

03When to use it

Use them for governed attributes needed across events. Avoid unnecessary personal data, unstable labels, and properties that belong to one event only.

04How it works

  1. Define the entity and analytical purpose.
  2. Choose a stable property name and value set.
  3. Set or update the property at a known time.
  4. Preserve event-time meaning where needed.
  5. Audit privacy, quality, and lifecycle rules.

05A practical example

Example

A workspace product records account_plan and member_role as user properties, allowing activation analysis by role while preserving the values present when each event occurred.

06Where it breaks

Properties can become stale, overlap during changes, or expose sensitive traits; identity merging may rewrite or fragment interpretation.

Common mistakes

  • Using latest values for historical questions without checking semantics.
  • Putting per-action context in a user property.
  • Collecting sensitive traits without necessity or governance.

07Sources

  1. User properties and event propertiesAmplitude Docs · Official documentationUser properties and event properties
  2. Look up event data for individual usersAmplitude Docs · Official documentationLook up event data for individual users
View saved topics

Start typing to search titles, definitions, categories, and frameworks.