Conversions per user
Conversions per user is the total number of conversions (key events) divided by the number of users. It measures how many converting actions an average user took, which differs from conversion rate (conversions per session or per user as a percentage). Its value depends on which events are marked as conversions and on the same identifier limits as any user count, so the definition must be fixed to read it.
What this means
Conversions per user = total conversions ÷ users. Where conversion rate expresses conversions as a percentage of sessions or users, conversions per user is a raw average count — it can exceed one when users convert repeatedly (re-purchases, multiple leads). It answers 'how many converting actions does an average user take', not 'what share of users convert'.
What changes it
Two levers dominate. First, the conversion definition: in event-based tools you mark certain events as conversions/key events, and adding or removing one immediately changes the numerator. Second, the user denominator carries the usual identifier caveats — resets split one person into several users, lowering conversions per user. Because both are configurable, compare the metric only across periods with the same conversion set and stable identification.
- Conversions per user = conversions ÷ users (a count, not a %)
- Marking more events as conversions raises it mechanically
- Identifier loss inflates users and lowers the ratio
How it appears in analytics and logs
A conversions-per-user value reflects repeat converting behavior. It moves when you change which events count as conversions, so a shift can be a measurement change rather than a behavior change.
Diagnostic use case
Use conversions per user to see how many key actions a typical user takes, distinct from conversion rate, while holding the conversion definition constant.
What WebmasterID can help detect
WebmasterID records conversion events first-party with names you define, so conversions-per-user is computed from an auditable event set without third-party cookies.
Common mistakes
- Confusing conversions per user with conversion rate.
- Comparing periods after changing which events are conversions.
- Forgetting users are identifiers, not people.
Privacy and accuracy notes
Conversions per user is a ratio of aggregate counts derived from first-party data; it needs no personal identifiers. Conversion events should not carry PII.
Related pages
- Sessions per user
Sessions per user is total sessions divided by the number of users — the average number of visits each distinct user made in the period. It reads as a return-frequency signal, but it inherits every weakness of the user count: when identifiers reset, returning visits split across several 'users', dragging sessions per user toward one and understating real loyalty.
- Average revenue per user (ARPU)
Average revenue per user (ARPU) is total revenue in a period divided by the number of users in that period. It is a standard unit-economics metric for subscription and consumer products, summarizing how much revenue each user generates. ARPU depends heavily on which users are in the denominator (all users vs active vs paying) and the length of the period, and it differs from ARPPU and lifetime value.
- Conversion rate: definition and denominators
Conversion rate is the share of some base that converted. The trap is the denominator: conversions per session, per user, and per unique visitor give different numbers and mean different things. Without stating the base, a conversion rate is ambiguous — and comparing rates with different bases is meaningless.
- Attribution analytics
Define conversions and attribute them first-party.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.