All terms

CRO Glossary

Metric Decomposition

Breaking a top-level metric into its component drivers to find where and why an experiment moved the needle.

Metric decomposition means splitting a headline number like revenue per visitor or overall conversion rate into the smaller pieces that multiply or add up to it. Revenue per visitor, for example, can be decomposed into conversion rate times average order value, or into traffic mix times per-segment conversion rates. When a test shows a lift (or no lift) at the top level, decomposition tells you which underlying lever actually moved.

Practitioners reach for this when a result is ambiguous or surprising. A flat overall conversion rate might hide a win in new visitors offset by a loss in returning visitors, or a price change might lift conversion rate while quietly dragging down average order value so net revenue stays flat. Without decomposing, teams risk declaring a test a wash when it actually has real, actionable sub-effects.

For example, an experiment adds a trust badge near checkout. Overall conversion rate is unchanged, but decomposition shows mobile conversion rose while desktop fell slightly, and that the badge increased click-through to checkout without affecting completion rate. That's enough to redesign the test rather than discard the idea.

The main caution is that decomposing a metric into many parts multiplies the number of comparisons being eyeballed, increasing the chance of chasing noise. Decomposition should inform hypotheses for follow-up tests, not replace a pre-registered primary metric.

Related terms

See this in the wild

ABWatcher watches how top teams apply metric decomposition.

Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.