When a conversion report mixes events and people

Repeated actions inflate the numerator while the denominator counts unique users. The useful response is a diagnosis that changes a decision, not another report describing the symptom. Use this play with the metric owner and the source-system owner. The working evidence should include metric dictionary, source records and cohort definition, with private or sensitive details removed from any shared example.

Confirm the problem in the actual workflow

Document the counting unit at each step and inspect repeated-event behavior. Start with one representative case and follow it from the original action to the reported outcome. Identify where the observed behavior first differs from the intended process. A screenshot of a final dashboard can be useful, but it may hide the source record, a delayed update or a decision made elsewhere.

Keep the unit of analysis explicit: a consistent account, user, event or revenue cohort. The same label can conceal different populations or stages. Before comparing two results, check that they describe the same kind of work and have had a comparable chance to complete it.

Separate the visible symptom from the cause

Write the numerator, denominator, unit, period, source and exclusions before interpreting the number. Separate observed data from assumptions and forecasts. A metric can be calculated correctly while still answering the wrong business question.

The symptom in this case is specific: repeated actions inflate the numerator while the denominator counts unique users. Ask which piece of evidence would distinguish an operating failure from a measurement failure or a mismatch in the original plan. If the evidence is unavailable, record the missing source and its owner instead of treating the preferred explanation as established fact.

A situation to work through

Five form submissions by one person are five events, but they are not five unique converted visitors.

This is an illustrative situation, not a reported client case. Record the equivalent evidence and assumptions for your own workflow.

Choose the smallest useful correction

Use a consistent unit or clearly state that the report measures event frequency rather than user conversion. Keep the change narrow enough that the responsible people can implement and inspect it. If a correction changes several things at once, describe it as a combined operating change; do not later claim that one small element caused the whole result.

Assign the correction to the metric owner and the source-system owner. Agree which artifact will show that the work is complete. An owner without an observable acceptance condition can close a task while leaving the original problem unresolved. A detailed checklist without an owner creates the opposite problem: the evidence requirement exists, but nobody is accountable for producing it.

Preserve the important limitation

Do not silently deduplicate events that represent legitimate separate transactions. This condition belongs beside the recommendation because it can change the decision. It should not disappear when the plan becomes a short presentation or a status update.

Twenty activated accounts divided by eighty eligible accounts is 25%. Dividing the same twenty accounts by two hundred individual signups produces 10%, but it mixes units. Both inputs can be real while the second ratio is unsuitable for an account-activation claim.

Verification worksheet

Download a working copy and follow the worksheet instructions. Keep unknown facts visible rather than filling gaps with guesses.

Decide whether to keep, revise or stop the change

Review ratios with compatible counting rules after the agreed observation period. Keep the correction when the intended behavior is verified and the guardrail remains acceptable. Revise it when the diagnosis was useful but the intervention did not resolve the cause. Stop and reassess when new evidence shows that the original problem was framed incorrectly.

Record what changed in metric dictionary, source records and cohort definition. This gives the next review a stable starting point and prevents a definition change from being mistaken for a performance improvement.

Related methods and next steps

• SaaS LTV: Three Formulas and When Each One Lies
• Segment for SaaS: Tracking Plan, Events and Costs
• Build a SaaS marketing board report
• ARPA and ARPU calculator

Return to the saas metrics topic guide, browse its complete resource collection, or use the working resource library. The primary reference provides relevant platform or methodological context; the diagnosis and example here are original editorial guidance.