Event Property
An attribute describing the context or details of one recorded event instance.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/event-property/
01What it means
An event property is a key-value attribute attached to a specific occurrence of an action, such as an order’s value, a search’s query length, or an error’s code. Unlike a user property, it describes that event at that moment rather than a characteristic intended to persist across events.[1][2]
Properties should describe the event at occurrence time; mutable account traits belong in user or account properties unless intentionally snapshotted.
02Why it matters
Properties let teams segment and interpret behavior without creating a separate event name for every variation.
03When to use it
Use properties for context that varies per action. Govern names, types, allowed values, privacy, and cardinality through the tracking plan.
04How it works
- Define the question the property supports.
- Choose a stable name, type, and meaning.
- Attach the value when the event occurs.
- Validate representative and edge-case values.
- Document and govern changes over time.
05A practical example
A Completed Checkout event includes payment_method, item_count, currency, and order_value properties, enabling analysis without separate checkout events for every combination.
06Where it breaks
Missing, inconsistent, high-cardinality, or sensitive values can make analysis unreliable or create privacy risk.
Common mistakes
- Encoding property values in event names.
- Using a current user trait as historical event context.
- Collecting data without a decision use.
07Sources
- User properties and event propertiesAmplitude Docs · Official documentationUser properties and event properties
- Official events and propertiesAmplitude Docs · Official documentationOfficial events and properties