All terms

CRO Glossary

Red Herring Metric

A metric that moves during a test but doesn't reflect real business impact, often leading teams to false conclusions.

A red herring metric looks like evidence of success or failure but is actually disconnected from, or only loosely correlated with, the outcome that matters. It typically shows up when teams track something easy to measure (page views, time on page, clicks on a non-critical element) instead of something harder to measure but more meaningful (revenue, retention, qualified conversions).

These metrics are dangerous because they create a false sense of confidence. A variant might increase "time on page" because the content is more confusing and users are struggling to find what they need, not because they're more engaged. Similarly, a spike in clicks on a redesigned button could reflect accidental clicks from a confusing layout rather than genuine interest.

A classic example: an e-commerce team tests a new product page layout and sees add-to-cart clicks rise 15%, but checkout completion stays flat — the add-to-cart click was a red herring, since users were abandoning at a later step and the real bottleneck was untouched. Guarding against red herring metrics means always tying primary test metrics as close as possible to actual business value, and treating upstream engagement metrics as supporting evidence rather than proof of success.

Related terms

See this in the wild

ABWatcher watches how top teams apply red herring metric.

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