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.
What this means
Conversion rate = conversions ÷ base. The base might be sessions, users, unique visitors, or visits to a specific step. Each choice answers a different question, so the base is part of the definition, not an afterthought.
Why the denominator matters
Conversions-per-session and conversions-per-user diverge whenever people take multiple sessions to convert. Mixing them — or comparing a session-based rate to a user-based one — produces nonsense. Pin the numerator (what is a conversion) and the denominator, and keep them stable.
- Per session vs per user vs per visit differ
- State the numerator and denominator explicitly
- Comparing different bases is meaningless
How it appears in analytics and logs
A conversion rate only means something once you know its numerator (what counts as a conversion) and denominator (sessions, users, or visits). A 'rate change' can be a definition change in disguise.
Diagnostic use case
Define conversion rate with an explicit denominator and conversion definition, so it is comparable over time and across reports.
What WebmasterID can help detect
WebmasterID measures conversions from first-party events you define, so the rate reflects your own funnel, not a cross-site profile.
Common mistakes
- Reporting a conversion rate without stating the base.
- Comparing session-based and user-based rates.
- Changing the conversion definition and reading it as a trend.
Privacy and accuracy notes
Conversion rate is an aggregate ratio; it needs no personal identifiers. WebmasterID computes it from first-party events.
Related pages
- Funnel analysis: finding the leak
Funnel analysis follows visitors through an ordered set of steps (view → add to cart → checkout → purchase) and shows where they fall out. It turns a single conversion rate into a map of where the loss happens. The pitfalls are step definition, small-sample noise, and assuming a strict order where users actually skip around.
- Bounce rate: definition and why it misleads
Bounce rate is the percentage of sessions with only one interaction. Its definition shifted: classic tools counted single-pageview sessions; GA4 derives it from engaged sessions instead. A high bounce rate is not inherently bad — for a single-answer page it can mean success — which is why context matters more than the number.
- Custom events: tracking what matters to you
Custom events capture meaningful actions a pageview cannot — a CTA click, a signup, a video play, a form submit. The value is in a consistent naming taxonomy and well-chosen properties. The risk is putting personal data into event names or properties, which turns analytics into surveillance. This page covers both.
- Attribution analytics
Tie conversions back to sources directionally.
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.