Quick definition: Delta (Δ) is the signed difference between two values, usually a treatment metric minus a control metric, expressed in the original metric’s units.
What is delta?
Delta is compact notation for change or difference. In product analytics and experimentation, it usually means the estimated treatment value less the estimated control value. A positive delta means the treatment estimate is higher under that convention; a negative delta means it is lower. The sign is meaningful only when the subtraction order is stated.
Delta is not automatically “lift,” “effect size,” or statistical significance. Lift commonly means relative change. Effect size can be a raw difference, standardized difference, risk ratio, odds ratio, or another estimand. Statistical significance concerns uncertainty under a model. Delta is simply the numerical gap to interpret with its units, uncertainty, and practical decision threshold.
Write a metric name with its unit: conversion-rate delta in percentage points, revenue-per-user delta in currency, or latency delta in milliseconds. Saying “delta is 2%” is ambiguous: it may mean two percentage points, a 2% relative change, or a decimal proportion. The distinction changes the decision.
Delta formula, units, and denominator
For a metric estimate m, define:
delta = m
For binary conversion among a shared analysis population, Δ = (converters. If treatment converts at 6.2% and control at 5.0%, delta is +1.2 percentage points, not 1.2%. Relative lift is separately (6.2% − 5.0%) / 5.0% = 24%.
| Metric | Delta unit | Interpretation |
|---|---|---|
| Conversion rate | Percentage points | Additional conversions per eligible unit. |
| Revenue per user | Currency per user | Average monetary difference across assigned users. |
| Page latency | Milliseconds | Change in observed response time. |
| Error rate | Percentage points | Change in failed requests per eligible request. |
Denominators matter before delta is calculated. A conversion delta comparing user-level treatment data to session-level control data is meaningless. For randomized tests, use the predeclared eligible assigned population for each arm. Do not replace it with people who clicked, rendered, or completed an intermediate step after treatment has influenced that step.
Delta in A/B testing
An A/B test estimates a delta in a chosen outcome under random assignment. Set the direction, unit, baseline, minimum detectable effect, and minimum practical effect before launch. The primary result should state the arm estimates, delta, sample sizes, and uncertainty interval. Confidence intervals show that a point delta is an estimate, not a guaranteed future result.
Use a decision rule that is aligned with value. A +0.05-point conversion delta may be statistically detectable at huge scale yet not pay for engineering or added support. Conversely, a small latency delta can be operationally important for a critical flow. For unfavorable metrics such as errors or time-to-complete, a negative delta may be good; write that interpretation plainly rather than assuming positive is better.
Do not choose the best-looking delta after examining many metrics, segments, and time periods. That selection inflates false-positive risk. Predefine the primary measure and label exploratory cuts accordingly; our multiple-comparisons guide explains why. Pair a primary delta with guardrail deltas for harms such as refunds, cancellation, failures, or complaint rate.
Worked delta example
A retailer tests delivery-date messaging. Control has 10,000 eligible users and 510 paid orders; treatment has 10,100 eligible users and 586 paid orders. The primary metric is paid-order conversion within 48 hours.
control = 510 / 10,000 = 5.10%treatment = 586 / 10,100 = 5.80%delta = 5.80% − 5.10% = +0.70 percentage pointsrelative lift = 0.70 / 5.10 = 13.7%
At 100,000 comparable eligible users, the point estimate corresponds to roughly 700 additional orders. That is a planning translation, not a certainty. The team calculates its preselected interval, checks that allocation and exposure logging are sound, then evaluates order value, delivery cancellations, and service contacts. A positive conversion delta that creates late deliveries may not be worth rollout.
Data-quality caveats
Delta inherits every measurement problem in both arm estimates. Inconsistent event versions, missing outcomes, duplicate transactions, timezone shifts, bot filtering, and identity fragmentation can manufacture a gap. Inspect numerator and denominator counts before interpreting the subtraction. A sample-ratio mismatch or variant-specific exposure failure can invalidate the comparison; investigate unexpected allocation using SRM diagnostics.
Rounding can also mislead. Displayed rates rounded to one decimal may imply a zero delta even when the underlying estimates differ. Retain sufficient precision for analysis, but present a rounded value that does not overstate certainty. For skewed monetary metrics, a mean delta can be driven by a small number of large purchases; report distribution-aware analysis and pre-specify handling of outliers.
Practical interpretation
Translate delta into a consequence at the expected volume and compare it with a pre-agreed threshold. For a binary metric, percentage points are often easiest: +0.4 points means four more outcomes per 1,000 eligible units. Show relative change as supporting context, especially when audiences expect it, but never allow it to replace the baseline.
Review the sign, unit, uncertainty, practical size, and downstream trade-offs together. A dashboard arrow alone is not an experiment decision. Maintain a consistent orientation across reports—treatment minus control is common—so a negative delta never silently changes meaning.
Common delta mistakes
- Omitting the subtraction order: the sign becomes ambiguous.
- Calling percentage points percent: absolute and relative change differ.
- Mixing incompatible denominators: the gap has no stable meaning.
- Treating delta as significance: uncertainty is a separate question.
- Hiding the baseline: practical scale cannot be judged.
- Ignoring guardrail deltas: a local improvement can damage value elsewhere.
Keep the analysis contract visible in the report: the analysis population, observation window, treatment assignment, and event source should sit beside the delta. If a reporting period, eligibility rule, or metric version changes, do not compare deltas across the break as though they were one series. This small amount of metadata prevents a numerical shorthand from becoming an unsupported claim.
Frequently asked questions
Is delta the same as relative lift?
No. Delta is usually an absolute difference. Relative lift divides that difference by the control value.
What unit should conversion delta use?
Use percentage points: 5% to 6% is +1 percentage point and +20% relative lift.
Can delta be zero while treatment matters?
Yes. Rounding can hide a small estimate, and a zero overall average can mask a pre-specified segment effect. Interpret the full analysis.
Should lower delta ever be better?
Yes. For latency, errors, cost, or churn, a negative treatment-minus-control delta can be an improvement.
Summary
Delta is a signed treatment-versus-control difference expressed in the metric’s original unit. State the subtraction order, units, denominators, arm estimates, and uncertainty. In A/B testing, judge it against practical thresholds and guardrails rather than treating a favorable number as a decision on its own.
Sources
- NIST/SEMATECH: Comparing process means
- UK Government Digital Service: Performance data
- CDC: Measures of effect