
Costs
Part of Marketing funnels: ten steps to define customer states, handoffs, economics and data
Marketing Funnels Benchmarks: What to Record
See what internal marketing funnels benchmarks should record: populations, progress, timing, customer outcomes, economics, data quality, and decision context.
Choose the decision first, then decide which people, events and evidence make a comparison useful. Start with company-specific customer, product, route and cycle baselines before borrowing an outside percentage. Use the branches below to identify what to record and what would make the result ready for use.
If you cannot state the decision
If the decision is unclear, do not begin with a benchmark number. A measure is useful only when its population, stages and evidence can answer a specific business question; otherwise, the result may be precisely calculated yet still fail to support a choice.
The UK Government metric design resource connects purpose and intended benefits with hypotheses, data sources, context, reporting and review. Use that sequence to choose a performance indicator, rather than picking a number first and looking afterwards for a decision it might support.
Counts and eligible populations
- Number entering each state
- Eligible prior-state count
- Exclusions listed
- Population share shown
- Open and closed settings visible
For each state, record the number entering, the number eligible from the previous state, the exclusions and the share of the population represented. Those details make a comparison more meaningful by showing when a small sample or a change in customer mix could make a standalone percentage hard to interpret.
Rule of thumb: Name the decision before choosing its measure.
If the eligible population is uncertain
If teams might be counting different people or cases, settle the eligible population before calculating a rate. Company customers, economics, cycle length and evidence shape a benchmark; differences in stages, products, markets, time windows or data collection can make superficially similar percentages incomparable.
Record eligibility rules and exclusions alongside the population description. Keep the denominator visible for every state, and note what share of the intended population it represents. This makes it possible to distinguish a real change in funnel performance from a change in who was counted.
Rule of thumb: Agree who qualifies before comparing results.
If someone proposes a percentage
If a percentage is being offered as a target or comparison, check whether another person could reproduce it. Record its numerator, denominator, entity, eligibility rules, sequence, time window, sample size and uncertainty; without that context, readers cannot tell what the result represents.
Decision being made / Context to record
- Compare progress
- Eligible population, sequence and time window
- Compare timing
- Complete cohort and time to outcome
- Check quality
- Customer and product outcome
- Check evidence
- Data source and release version
Keep open and closed funnel settings explicit, and state whether the rate covers consecutive states or the whole journey. An external figure should not stand in for an internal baseline unless the populations and methods are comparable. A consistent definition matters across products and markets.
Rule of thumb: Publish a rate only with its denominator and eligibility rules.
If the question is how people move
If the decision concerns movement through the funnel, record progress and timing together. Track both consecutive-state and end-to-end rates, plus the median and distribution of time to progress, pauses, returns, assisted progress and confirmed exits.
Define event order and the maximum time allowed for progression. Separate activity recorded during a period from outcomes for cohorts that have had time to mature. The funnel examples illustrate state boundaries that can help make the sequence being measured explicit.
Analytics settings can affect who is counted. Check conversion windows, event order, unique counting and simultaneous events, then preserve the configuration with each benchmark. This makes it less likely that a settings change will be mistaken for a change in customer behaviour.
Rule of thumb: Keep the event sequence, window and counting settings with each rate.
If more progress may not mean a better outcome
If a stage rate improves but the customer result remains uncertain, pair progress with measures of quality and recovery. Depending on the decision, consider qualification, activation, fulfilment, repeat behaviour, retention, cancellations, returns, complaints, support, accessibility issues and recovery.
Choose measures that show whether growth supports durable customer outcomes, not merely whether more people cross a stage boundary. A movement increase is incomplete evidence when the quality or durability of the resulting outcome is not visible in the same comparison. The strategy examples also help frame outcomes beyond a single rate.
Rule of thumb: Pair each progress measure with the customer outcome it should advance.
If a conversion gain could add cost or pressure
If a stage improves, check whether the economics and capacity behind it also change. Monitor value, margin, acquisition cost, sales effort, service load, discounts, bad debt, cash timing and capacity by cohort or segment, rather than relying on one aggregate result.
A stage improvement may not create value if downstream costs, delays or poor fit rise faster. Compare costs and capacity in the same customer or segment context used for progress, so an apparent gain does not conceal a heavier service burden or weaker economics.
Rule of thumb: Keep a conversion gain provisional until cost and capacity are visible.
If the records or definitions have changed
If data quality could affect the comparison, record the conditions that make counts trustworthy. Track missing and duplicate events, invalid parameters, identity conflicts, source gaps, consent effects, processing delay, reconciliation differences, unresolved alerts and definition changes.
Keep analytics configuration with the benchmark, and distinguish a source or definition change from movement in the funnel. The NIST guidance on design choice relates objectives to practical constraints. Benchmark reporting is not a controlled effect estimate, and observation alone does not establish causation.
Rule of thumb: Treat tracking quality and configuration as part of the benchmark.
If the result will shape a forecast
If a benchmark will guide a forecast or decision, build an internal planning range from stable data across enough complete cycles. Segment only where the evidence supports it, and annotate product, price, channel, policy or tracking changes that may affect the comparison.
Use conservative, central and upside forecasts rather than a single copied industry number. The range is one input to marketing funnel decisions, not a substitute for deciding what evidence the business needs. Record each result's definition, formula, source, owner, period, maturity, sample size, exclusions, uncertainty and decision threshold.
Freeze the original value and show corrections separately. The funnel checklist covers exclusions and windows that can help make a range repeatable. Review the set quarterly and after material changes, removing measures that no longer support a decision while retaining their historical definitions.
Compare distributions and important exceptions as well as averages, so an improvement in one segment does not hide deterioration in another. Keep the evaluation question aligned with the evidence available; note whether a shift reflects changed business conditions, measurement, or both.
Rule of thumb: Revise a range when evidence or conditions change, and preserve its earlier definition.







