Experiments

Data Science

How to experiment with personalization in AI systems

Jun 1, 2026

min read

A graphic of a bar chart with an arrow pointing upward.

Standard A/B testing breaks when the treatment is never the same twice.

That's the core problem with running AI personalization experiments — your recommendation engine, dynamic content system, or LLM-based feature is generating a unique experience for every user, which means the foundational assumption behind classical A/B testing (one treatment, applied the same way to everyone) doesn't hold.

The result is noisy data, lift numbers that don't replicate, and false confidence in model improvements that are actually just reflections of pre-existing user quality differences.

This guide is for engineers, PMs, and data teams who are building or iterating on AI-driven personalization systems and need a reliable way to measure whether those systems are actually working. Here's what you'll learn:

Why standard A/B testing produces structurally misleading results for AI personalization — and what breaks specifically
How to separate user-level effects from model-level effects so you're measuring model quality, not user quality
How to measure lift accurately when every user receives a different AI-generated experience
How to detect bias and fairness problems that aggregate metrics will hide
What infrastructure primitives you need to run continuous AI personalization experiments at scale

The article moves in order from diagnosis to execution. It starts with why the standard testing method fails for this class of system, then works through experiment design, lift measurement, bias detection, and finally the infrastructure layer that makes all of it work in production.

Each section builds on the one before it, so the techniques in the later sections only make sense once the structural problems in the earlier ones are clear.

Why traditional A/B testing breaks down for AI personalization

Classical A/B testing earned its reputation as the gold standard for causal inference because it does one thing exceptionally well: it isolates the effect of a single, stable change applied uniformly to a randomly assigned group.

That structural simplicity is also its limitation. When the "treatment" is an AI system generating unique outputs for every user in real time, the foundational assumptions that make A/B testing valid start to crack — not metaphorically, but in ways that produce structurally misleading results.

The fixed-treatment assumption standard A/B testing actually requires

When Professor Alexandre Belloni at Duke Fuqua describes A/B testing as the gold standard for determining causal effect, the implicit qualifier is that the treatment is fixed and uniform. Think of the Obama 2008 campaign's headline and button-color tests: every user in the treatment group saw the same headline, the same button. The comparison was clean because the intervention was identical across the group.

That condition — one treatment, applied the same way to everyone in the variant — is what allows you to attribute outcome differences to the treatment rather than to noise or pre-existing user differences.

Standard A/B testing infrastructure is built around this assumption. Randomization creates comparable groups. A single variable changes. You measure whether the outcome difference exceeds what chance would produce.

How AI personalization violates that assumption by design

A recommendation engine doesn't serve the same ranked list to every user in the treatment group. A dynamic content system doesn't generate the same copy for every session. An LLM-based feature doesn't produce the same response twice. That's the point — personalization is valuable precisely because it adapts to the individual.

But this creates a fundamental problem for standard A/B testing: there is no single "treatment" to evaluate. Two users assigned to the same variant are receiving materially different interventions, driven by the model's real-time decisions about their context, history, and predicted preferences.

As GrowthBook's AI testing playbook notes, the goal of tuning "AI responses across thousands of use cases" is structurally incompatible with one-variable-at-a-time testing. Interaction effects compound this further — AI personalization systems often have multiple model components active simultaneously, and standard A/B frameworks have no native way to account for how those components interact across users.

What this means for experiment validity

The validity consequences are specific and serious. When an AI system routes users based on model decisions, naive treatment/control comparisons don't measure model quality — they measure a mixture of model quality and pre-existing user differences.

The mechanism behind this is covered in the next section; the point here is that the contamination is structural, not incidental.

Even when randomization is technically in place, the heterogeneity of AI outputs creates a second problem. GrowthBook's documentation puts it plainly: "Experimentation results work on averages, and this can hide a lot of systemic biases that may exist."

An average treatment effect calculated over a population where every user received a different AI-generated experience is an average of fundamentally different interventions. It tells you something, but not what you think it tells you — and it can easily mask divergent effects across user segments that would be visible if you were measuring a uniform treatment.

The symptoms practitioners experience — noisy results, inconclusive tests, lift estimates that don't replicate — often trace back to this structural mismatch. The problem isn't that the team ran the test wrong. It's that the testing method was designed for a different class of system.

This is diagnosable, and it's solvable. But the solution requires rethinking randomization design, how lift is measured, and what infrastructure is needed to run valid experiments on systems where the treatment is never the same twice.

Separating user-level effects from model-level effects in AI personalization experiments

The most dangerous failure mode in AI personalization experiments isn't a bug in your statistical test — it's a structural flaw in how you've set up the comparison.

When a recommendation engine routes higher-value users toward certain experiences, a naive treatment/control comparison doesn't measure whether your model is better. It measures whether your model happened to find better users. That distinction is the difference between a genuine insight and a false positive you ship to production.

What selection bias actually looks like in AI systems

Spotify's engineering team describes their personalization systems as learning "relationships between user characteristics — age, past behavior, product preferences — and preferred experiences". That's precisely what makes personalization valuable. It's also precisely what makes naive A/B comparisons invalid.

When a model's job is to identify the best experience for each user based on their characteristics, it is by design routing different users to different treatments. If your experiment assigns users to treatment and control groups after — or alongside — that routing logic, the groups are no longer exchangeable.

Treatment users may be systematically higher-value, more engaged, or more likely to convert, not because your model is better, but because your model already learned to find them. GrowthBook's own documentation puts it plainly: "Experimentation results work on averages, and this can hide a lot of systemic biases that may exist." In AI systems, those biases are often baked into the routing logic itself.

Randomization unit design — why user-level hashing is the foundation

The structural fix is to move randomization upstream of the model's decision-making. Randomization must happen at the user level, using deterministic user-level hashing, before the personalization layer makes any routing decisions.

This ensures that the same user consistently lands in the same experimental bucket regardless of session, device, or model state — and that bucket assignment is independent of any signal the model might use to route them.

Spotify's architectural approach captures the principle cleanly: "We build personalization systems using our ML/AI stack and improve them through our experimentation stack." Those are treated as distinct technical domains, not interleaved ones. The experiment layer sits above the personalization layer in the decision stack. When they're entangled, the model's routing decisions contaminate the randomization.

GrowthBook supports randomization across flexible units — user, location, postal code, URL path — which allows teams to lock assignment at the user level before any model inference occurs. The choice of randomization unit isn't a configuration detail; it's the primary mechanism for ensuring your treatment and control groups are actually comparable.

Holdout groups for isolating model-level effects

Even with clean user-level randomization, measuring the model's aggregate contribution requires a holdout group — a segment of users who receive no personalization, or a fixed baseline experience, while the rest of the population is exposed to the model. The holdout gives you a clean counterfactual: what would have happened without the personalization layer at all?

Without a holdout, you can compare model versions against each other, but you can't measure whether the personalization system as a whole is generating lift over a non-personalized baseline.

That's a meaningful gap, especially early in a system's lifecycle when the fundamental question is whether the model is adding value, not just which variant of it performs best.

GrowthBook supports holdout experiments, and this capability matters specifically because it separates the question of model quality from the question of user quality. A model that looks good in an A/B test against another model variant might still be underperforming a simple non-personalized baseline — or it might be outperforming it only for a specific user cohort, which would itself be a signal worth investigating.

Auditing for residual confounding

Even with correct randomization and holdout groups, residual selection bias can persist — particularly if the model was trained on data that already reflects historical routing decisions.

GrowthBook's warehouse-native architecture runs statistical computations directly against your existing data warehouse — Snowflake, BigQuery, Redshift, or Postgres — which means every calculation is reproducible and auditable without pulling data into a proprietary engine. That auditability is what lets you verify that your randomization is actually clean, not just assumed to be.

Segment-level analysis is the practical tool for detecting residual confounding: if observed lift is concentrated in high-value user cohorts rather than distributed across the population, that's a signal that user quality, not model quality, is driving the result.

Targeted rollout capabilities support this kind of cohort-level inspection. And for cases where pre-experiment user characteristics are imbalanced despite randomization, CUPED and post-stratification — both supported in GrowthBook — provide regression adjustment that can partially correct for those differences.

Landon Smith, Head of Post-Training at Character.AI, describes the practical value of this architecture: "GrowthBook has been an invaluable tool for Character.AI, helping us develop our models into a great consumer experience. We can compare different modeling techniques from the perspective of our users — guiding our research in the direction that best serves our product." That framing — comparing modeling techniques from the perspective of users, not just metrics — is exactly the orientation that user/model separation makes possible.

Lift numbers lie when every user receives a different AI-generated treatment

Getting randomization right is necessary but not sufficient. Once you've structured your experiment correctly, you still face a harder problem: computing a lift number that actually reflects model performance rather than measurement artifacts.

In AI personalization systems, the standard approach — calculate average treatment effect, run a t-test, ship if p < 0.05 — produces numbers that look credible but often aren't.

Why average treatment effects fall short for heterogeneous AI outputs

In a classical A/B test, every user in the treatment group receives the same stimulus. The average treatment effect is meaningful because you're averaging over a single, consistent intervention. In an AI personalization system, User A gets a recommendation driven by purchase history, User B gets one driven by browsing recency, and User C gets one based on predicted lifetime value. The "treatment" is a distribution of outputs, not a fixed stimulus.

When you compute ATE across this distribution, you're averaging across fundamentally different interventions. That average might look positive while the model is actively hurting engagement for a large segment of mid-tier users — if a small cohort of high-value users is responding exceptionally well, they'll pull the aggregate number upward and mask the damage elsewhere.

The standard lift formula — (treatment metric − control metric) / control metric — assumes you're comparing stable, consistent means on both sides. That assumption holds when everyone in the treatment group received the same thing. When treatment content varies continuously across users, the "treatment mean" is an average of fundamentally different interventions, and the lift number you compute is averaging across experiences that aren't comparable.

SUTVA violations and the evolving treatment problem

There's a deeper statistical issue that most teams don't catch until their results stop replicating. The Stable Unit Treatment Value Assumption (SUTVA), foundational to causal inference, requires two conditions: no interference between units, and a single version of the treatment. AI personalization systems routinely violate the second condition.

AI models analyze behavior in real time, which means the experience a user receives at day one of your experiment is not the same experience they receive at day thirty. If the model retrains or adapts during the experiment window — which is the entire point of a continuously learning system — then your early-period data and late-period data are measuring different interventions.

Pooling them produces a blended estimate that accurately describes neither. You can end up with a "significant" result that reflects the model's improvement trajectory rather than a stable treatment effect, which means the result won't hold when you try to reproduce it against a different baseline.

The practical mitigation is to lock model weights during the experiment window, or to explicitly segment your analysis by time cohort and check for consistency across periods before pooling. If lift is only appearing in the second half of your experiment, that's a signal worth investigating before you ship.

CUPED and regression adjustment for pre-experiment normalization

Even with a locked model and clean randomization, pre-existing user variance will inflate your standard errors and force you to run longer experiments than necessary. Heavy users, power purchasers, and highly engaged users all have metric trajectories that started before your experiment did.

If those users happen to skew toward your treatment group, you'll see lift that reflects user quality, not model quality.

CUPED — Controlled-experiment Using Pre-Experiment Data — addresses this by using each user's pre-experiment behavior as a baseline correction. If a user was already a heavy purchaser before your experiment started, CUPED accounts for that, so your lift estimate reflects the model's effect rather than the user's pre-existing tendencies.

The result is tighter confidence intervals — which means you can detect smaller real effects with the same sample size, or reach statistical confidence faster.

Platforms like GrowthBook support CUPED and post-stratification natively as part of their statistical framework, meaning this isn't a custom analysis you need to build outside your experiment tooling. GrowthBook's Bayesian engine extends this further by allowing informative priors from historical experiments — if past model comparisons have averaged 1% lift, you can encode that knowledge to tighten credible intervals on new experiments rather than starting from scratch each time.

Activation metrics and guardrail metrics

Not every user assigned to your treatment group actually receives a meaningfully different experience. Some users never trigger the recommendation engine. A second group visits the surface but doesn't interact with the personalization layer at all. For a third group, behavioral history is too sparse for the model to generate a confident output.

Including these users in your lift calculation dilutes the signal — you're averaging a real effect over a large population of users who experienced nothing different.

Activation metrics solve this by filtering the analysis to users who were genuinely exposed to a differentiated experience. The key discipline is defining activation criteria before the experiment runs, based on what it means to have actually received the personalized treatment, not based on which users showed positive outcomes.

Guardrail metrics are the other half of the discipline. Lift in your primary metric is only meaningful if it isn't purchased at the cost of degraded experience elsewhere — slower page loads, higher error rates, increased session abandonment. These need to be pre-specified, not added after you see the results.

GrowthBook's A/A test documentation makes the stakes concrete: with five unrelated metrics in a single experiment, the probability of at least one false positive reaches 41%. With two metrics, it's 19%. Post-hoc guardrail selection is just p-hacking with extra steps. Specify your primary metric, specify your guardrails, and hold to that list before you look at results.

The goal of this entire measurement stack — CUPED normalization, activation filtering, pre-specified guardrails — is to answer a single question cleanly: did the model-treated group actually behave differently, or are you measuring something else?

For AI personalization, where the causal chain from model output to user behavior is complex and partially opaque, lift measurement's focus on actual change against a baseline is almost always the right tradeoff.

Avoiding bias and fairness pitfalls in AI personalization experiments

A personalization model that shows +3% lift in aggregate can still be quietly degrading the experience for a meaningful slice of your user base. If your experiment reporting stops at overall averages, you will never see it.

This isn't a statistical edge case — it's a structural property of how AI systems learn, and it requires deliberate design choices to surface.

How AI personalization systems encode and amplify historical bias

The problem starts in training. Personalization models learn from historical behavioral data, which means they inherit whatever disparities already existed in user outcomes. GrowthBook's own documentation states this plainly: algorithmic systems can "learn or otherwise encode real-world biases in their operation, and then further amplify/reinforce those biases."

The amplification mechanism is what makes this particularly difficult to contain. When a biased model generates biased recommendations, those recommendations produce biased behavioral signals, which then feed back into the next training cycle with even more concentrated bias. The model doesn't drift toward fairness over time — it drifts away from it.

Sparse data compounds the problem. GrowthBook's documentation specifically flags that "sparse or poor data quality leads to objective-setting errors and system designs that lead to suboptimal outcomes for many groups of end users."

Underrepresented users generate less behavioral signal, so the model has less to work with for those groups — and its outputs are correspondingly less reliable for them, even when aggregate performance looks strong.

This isn't hypothetical. Research into LLM-based hiring tools found that models were 15% more likely to select whichever candidate appeared first in the prompt, all else being equal — a systematic positional bias that was completely invisible in aggregate accuracy metrics but measurable once researchers structured their analysis to look for it.

The same dynamic applies to recommendation engines and dynamic content systems: the bias exists in the decision pattern, not in the headline number.

Why aggregate lift metrics hide differential impact

GrowthBook's documentation is direct on this point: "Experimentation results work on averages, and this can hide a lot of systemic biases that may exist." The formal statistical mechanism here is Simpson's Paradox — a phenomenon where a trend visible in aggregate data reverses or disappears when the data is disaggregated by subgroup.

The Berkeley admissions case is the canonical illustration: overall admission rates appeared to favor male applicants (44% vs. 35%), but when broken down by department, women had higher admission rates in most departments. The aggregate number was real but misleading.

The same structure appears in AI personalization experiments when a model over-serves high-engagement or data-rich segments while underperforming for others — the overall lift is genuine, but it's being driven by a subset of users, and the rest are getting a worse experience than baseline.

Goodhart's Law adds another layer of risk. When a single aggregate metric becomes the optimization target, the model learns to maximize that metric for the users where it's easiest to do so. That tends to be your highest-signal, most-engaged segments — which means the model is systematically deprioritizing everyone else.

Metric slicing and cohort-level guardrails

The practical response is to build differential impact analysis into the experiment design from the start, not as a post-hoc audit. GrowthBook's documentation is explicit that "it is possible to measure this effect and ensure that results account for these groups" — but only if you instrument for it.

Metric slicing means breaking experiment results down by the user dimensions that matter for your product: demographic segments, behavioral cohorts, geographic regions, account tenure, or whatever groupings are relevant to your user base.

GrowthBook's product analytics capabilities support pivot tables and dimension-based filtering, which allows teams to surface differential treatment effects across cohorts rather than relying solely on aggregate experiment readouts. The guidance from GrowthBook's Simpson's Paradox documentation applies directly: "analyze the data by considering all relevant variables and subgroups" and "ensure that the experimental groups are similar in terms of demographics and behavior."

Guardrail metrics need to follow the same logic. A guardrail defined only at the aggregate level will pass a model that harms a specific cohort while lifting overall numbers.

Guardrail metrics should be defined per segment for any experiment where differential impact is a plausible risk — and for AI personalization experiments, it almost always is. When a guardrail fires, GrowthBook's kill-switch capability allows teams to immediately deactivate the feature without a full deployment cycle, which matters when the harm being detected is happening to real users in production.

Targeted rollouts serve a related function: validating model performance on specific cohorts before broad release, rather than discovering differential impact after the fact at full traffic. Shipping to a segment first and measuring cohort-level outcomes is a more honest test of whether your personalization model is actually working for all of your users — not just the ones it was implicitly optimized for.

The infrastructure gap that makes continuous AI personalization testing fail

The measurement techniques covered earlier in this article — regression adjustment, activation filtering, cohort-level slicing — only work in production if the infrastructure underneath them is built for the job.

Most experimentation stacks were designed for periodic A/B tests: launch a variant, wait two weeks, read a result, ship or kill. AI personalization doesn't work that way. Hightouch describes the gap plainly: rather than waiting weeks for a single test to conclude, AI-driven systems can test thousands of variations in parallel, adapting content, offers, and timing in real time. That scale demands infrastructure that treats experimentation as a continuous operational process, not a scheduled event.

Linking feature flags to model versions

The first primitive you need is a clean linkage between your feature flag system and your model versioning. Without it, you cannot reliably attribute outcome changes to a specific model version versus any other concurrent change in your system.

Feature flags serve as the deployment primitive here — they control which users are exposed to which model variant, enable gradual rollouts to limit blast radius, and provide an instant kill switch if a new model degrades a guardrail metric before you've caught it in your analysis. GrowthBook SDKs evaluate flags from a locally cached payload, so flag checks resolve in sub-millisecond time and your application continues to function correctly even if GrowthBook's servers are temporarily unavailable.

Feature flag rollout systems that expose this as a first-class capability allow experiments to be directly tied to flag IDs. The practical value is that your model deployment and your experiment assignment stay in sync — you're not managing two separate systems that can drift out of alignment.

Bandit-style traffic allocation for adaptive learning

Static 50/50 splits make sense when your treatment is fixed. When you're testing multiple model variants and want to minimize exposure to underperforming ones, multi-arm bandits are a better fit.

Spotify's engineering team describes bandits as dynamically reallocating traffic from poorly performing treatments to successful ones — which compresses the time between launching a variant and making a confident rollout decision.

There's an important distinction worth keeping in mind: multi-arm bandits operate at the model level, shifting traffic between discrete variants. Contextual bandits operate at the user level, selecting a variant based on user features — which Spotify explicitly characterizes as "essentially personalization."

Both are valid tools, but they answer different questions. Multi-arm bandits are the right primitive for model comparison experiments; contextual bandits belong in the personalization layer itself. Platforms that support native bandit configuration — burn-in period, schedule interval, and conversion window — treat this as a production-ready capability rather than a theoretical one.

Warehouse-native analysis as the source of truth

Analysis that runs inside a vendor's proprietary engine creates a reproducibility problem. You can't audit the calculation, you can't add metrics retroactively, and you can't slice results against user attributes that live in your own warehouse.

For AI personalization experiments — where you need cohort-level breakdowns to catch differential impact and regression adjustment to normalize pre-experiment variance — that opacity is a structural liability.

Warehouse-native analysis solves this by running statistical computations directly against your existing data infrastructure, whether that's Snowflake, BigQuery, Redshift, or Postgres. GrowthBook's architecture is built on this model: metrics are defined in SQL, calculations are reproducible, and you can add metrics to a completed experiment after the fact.

That last capability matters more than it sounds — in AI personalization experiments, you often discover the right guardrail metric after you've already launched.

Capturing institutional knowledge to compound personalization learnings

High-volume experimentation creates a compounding knowledge problem. Without program-level memory, teams repeat tests they've already run because nothing connects past learnings to new ideas.

Individual experiments produce results; a program produces compounding understanding of what works for which users under which conditions. Those are different things.

The infrastructure requirement here is a searchable, structured record of experiment history — not just results, but hypotheses, metric choices, and rollout decisions. GrowthBook addresses this through a learning library that surfaces past experiments, cumulative impact tracking across the full experiment program, and insights dashboards that make win rates and metric performance visible at the program level.

The goal is to make the tenth experiment in a personalization domain meaningfully informed by the first nine, rather than starting from scratch each time.

Taken together, these four primitives — flag-linked model versioning, adaptive traffic allocation, warehouse-native analysis, and institutional knowledge capture — form the infrastructure layer that makes continuous AI personalization testing viable. None of them is sufficient alone.

A bandit without reproducible analysis produces fast results you can't trust. Warehouse-native analysis without institutional capture produces auditable results you'll forget. The stack only works as a system.

What valid AI personalization experiments actually require

The through-line of this article is a single, uncomfortable truth: the standard experimentation playbook was built for a class of system that AI personalization is not.

When the treatment is a distribution of outputs rather than a fixed stimulus, when the model is routing users based on signals that correlate with user quality, when the system is learning during the experiment window (the SUTVA violation covered in the measurement section above) — the numbers you get from a naive A/B test are not wrong in an obvious way. They're wrong in a way that looks credible, which is worse.

The non-negotiable foundations: randomization, measurement, and bias detection

Three things have to be right before anything else matters. Randomization must happen upstream of the model's routing logic — not alongside it, not after it.

Lift measurement requires filtering to users who actually received a differentiated experience, applying pre-experiment variance reduction, and evaluating against pre-specified guardrails. Bias detection cannot be retrofitted — it has to be built into the experiment design from the start, because aggregate lift numbers will never surface differential harm on their own.

Infrastructure decisions that determine whether your experiment results are trustworthy

If you're early in building a personalization system, the most important infrastructure decision is keeping your experiment layer structurally separate from your personalization layer — and making sure feature flags are the mechanism that links model versions to experiment assignments. GrowthBook feature flags control which users are exposed to which model variant, enable gradual rollouts with guardrail metrics, and provide an instant kill switch without requiring a deploy.

If you're further along and running multiple model variants in parallel, warehouse-native analysis becomes the non-negotiable: you need to be able to audit your calculations, slice by cohort, and add guardrail metrics after launch without rebuilding your analysis pipeline. GrowthBook's warehouse-native architecture supports all of this without pulling your experiment data into a black box.

Start with the holdout: the one experiment that surfaces every structural problem

The best first experiment is usually the simplest one: a holdout test that answers whether your personalization system is generating any lift at all over a non-personalized baseline. Not a model comparison. Not a multi-variant test. Just: does the model add value?

That question is harder to answer than it sounds, and getting a clean answer to it will surface most of the structural issues — selection bias, SUTVA violations, missing activation criteria — before you're running at full scale.

This article was written to give you a complete picture of what valid AI personalization experiments actually require, and to make the path from diagnosis to execution as clear as possible. The problems are real, but they're solvable with the right design choices.

What to do next: Start by auditing your current experiment setup against the randomization question: does your bucket assignment happen before or after the model makes routing decisions? If you can't answer that with certainty, that's your first fix — everything downstream of a contaminated randomization is unreliable. If your randomization is clean, move to measurement: do you have activation criteria defined, and are your guardrail metrics pre-specified? If both are in place, run a holdout experiment against a non-personalized baseline before you run any model comparison. That sequence — randomization, measurement hygiene, holdout baseline — will give you a foundation you can actually build on.

Related insights

Sign up for free

Take Growthbook for a spin, no credit card required.

Create my account

Example H2

See All Articles

Experiments

Feature Flags

CLI vs MCP: TLDR, it doesn’t matter as much as you think

Oct 21, 2026

min read

Your agent should know how to do the job whichever interface it uses.

Your coding agent can already run terminal commands. Your product manager's assistant can connect to remote tools. Both need to inspect the same experiment, understand the same metric, and prepare changes to the same feature flag.

That creates a familiar question: should you give them a CLI or an MCP server?

The usual answers mix several concerns. A CLI is easy to compose with scripts. MCP gives compatible clients a standard way to discover and invoke tools. Skills can supply the instructions that make either route useful. None of those statements tells you whether the agent knows your release process or can distinguish a draft from a live change.

For GrowthBook, the choice has become smaller. We've built the agent layer around a REST API and reusable workflow skills, then made those available through different interfaces. Your choice of CLI or MCP no longer needs to determine which product workflow your agent can understand.

It still determines how the agent connects, executes requests, and handles credentials. This article explains that distinction, shows the same disabled-flag operation through both routes, and gives you a way to evaluate the integration you actually intend to use.

The debate combines three different questions

Start with a specific job: prepare a release control for a new checkout flow. The agent needs to know which project owns checkout, which environments exist, what the default behavior should be, and whether the proposed flag key already exists.

Choosing an interface answers only part of that job.

How can the agent reach the product?

A command-line interface lets an agent invoke a program in an environment where it has shell access. That program can make authenticated API requests and return data. You can also run the same commands yourself, put them in scripts, and preserve output for inspection.

The Model Context Protocol architecture connects a host application to servers through clients. An MCP server exposes capabilities that a compatible host can discover and call. The host might be a coding environment, a desktop assistant, or another agent application.

These categories overlap. A terminal-based agent can also be an MCP client. A local MCP server can be a process launched by that client. A remote MCP connection can work without the host giving the model a general-purpose shell.

So “terminal agent” doesn't automatically mean “use the CLI,” and “MCP” doesn't automatically mean “remote service.” Ask what access the runtime provides before choosing the adapter.

What procedure should the agent follow?

An API can expose a create operation without teaching an agent when to use it. A syntactically valid feature flag might still have the wrong project, an ambiguous key, or a default value that doesn't match the application.

That's the job of a skill: reusable instructions for a recognizable task. The Agent Skills format gives those instructions a portable structure, including a skill entry point and supporting references. A workflow can describe the context to inspect, the sequence to follow, and the evidence to return.

For the checkout example, useful guidance says to resolve environments, check the permanent key, choose a value type, and create the flag disabled. Merely exposing a create command leaves those decisions to the agent's general knowledge.

Skills are also useful when the right answer is to take no action yet. “Create a flag” and “design an experiment” are related requests, but they can require different objects and sequencing. An agent needs enough product guidance to make that distinction.

What context makes the procedure relevant?

Even a good playbook needs the current product state. The agent should inspect the objects in your GrowthBook organization and, when it is changing application code, the repository's SDK initialization and tests.

Those are different sources of context. GrowthBook supplies flags, experiments, metric definitions, and other authorized product resources. Your coding runtime supplies the application files it can access. An MCP connection doesn't by itself grant repository access, and a CLI doesn't by itself explain your metric definitions.

Evaluate the combination: access to the product, a maintained procedure, and enough context to apply that procedure. A comparison that changes all three at once cannot isolate the effect of CLI versus MCP.

GrowthBook puts the durable parts below the interface

We separated the agent layer into responsibilities that can be reused. The product API exposes operations. Skills explain workflows. The interface connects the agent to those two layers.

This is the architectural shift behind GrowthBook's agent experience. Instead of making every client integration carry its own interpretation of experimentation, we can share the interpretation and change how it is delivered.

The API provides the operations

GrowthBook's REST API makes product objects addressable. An agent can inspect a project, retrieve a flag, or perform an authorized operation against those objects.

The rebuilt API described in GrowthBook 4.4 uses shared schemas to support types, validation, and API documentation. The CLI is generated from the API definition. That reduces the amount of separately maintained command logic needed to expose product operations.

The OpenAPI specification explains the underlying principle: a machine-readable description can represent an HTTP API's paths, operations, inputs, and responses. Generation is useful because it derives another interface from that contract.

Generation doesn't mean any installed binary knows every future endpoint. The generated client still has a version, and your GrowthBook server still has a version. A self-hosted instance can lag behind the public documentation. Treat API compatibility as a deployment fact you verify.

Skills provide the workflow guidance

GrowthBook's feature-flags skill routes requests to more specific workflows. Creating a flag, inspecting dependencies, changing targeting, requesting review, and publishing a revision are separate procedures.

That structure lets the agent load the guidance relevant to the current job. The skill authoring guidance on progressive disclosure supports this approach: keep the entry point focused and place detail in references that are loaded as needed.

The benefit is maintainability as well as context management. A correction to a flag workflow can be made in the maintained skill rather than repeated across a series of tool descriptions and client-specific prompts.

There are two shell concepts to keep distinct. The generated growthbook CLI is a terminal interface to the product API. The skills repository also includes a small gb-call helper for making REST requests. Installing a skill doesn't make that helper a globally available command; its location depends on the installation. Both can reach the API, but their configuration and invocation are different.

MCP provides a thin bridge

The current GrowthBook MCP implementation exposes four tools: growthbook_list_skills, growthbook_read_skill, growthbook_api_read, and growthbook_api_write.

An agent discovers a domain, reads the relevant workflow, then makes API calls. It doesn't need a dedicated MCP tool for every product endpoint. Calls described as gb-call GET in a skill map to the read tool; mutating methods map to the write tool with the same path and body.

The bridge does not run the shell helper. It forwards authenticated requests. Product-side permissions and validation remain important because a small tool surface can still reach many operations.

Shared guidance also has a delivery boundary: the MCP server bundles skills when it is built, using a pinned source revision. A newly edited skill in the repository needs to be included in a subsequent server build before that server supplies it. “Shared source” is a maintainability claim, not a promise of instant synchronization.

Explore the shared flag workflows

Open the feature-flags skill to see the procedures that guide creation, targeting, reviews, and publishing. Bring the same workflow knowledge to the agent interface your team uses.

View the Flag Skill

The same disabled flag can use either route

The practical question is whether the interface changes the job. Let's create a Boolean flag called checkout-redesign, with a false default and every environment disabled.

This is an API example for a sandbox project, not an application integration tutorial. It creates a control object; your application still needs a correctly configured GrowthBook SDK to evaluate it. The feature flag documentation covers the product concepts behind that integration.

Connect and verify before preparing the write

For the terminal route, install the current GrowthBook CLI, configure a Personal Access Token through its interactive setup, and inspect the available command syntax:

npm install -g growthbook
growthbook configure
growthbook whoami
growthbook features create --help
growthbook features get --help

Check that the active server and identity are the ones you intend to use. Prefer a tested, pinned CLI version in repeatable automation. Don't include a live token in a command you plan to share.

For an MCP route, the GrowthBook Cloud setup uses the hosted endpoint and browser OAuth. In a client using the documented mcpServers configuration shape, such as Cursor, add:

{
  "mcpServers": {
    "growthbook": {
      "url": "https://mcp.growthbook.io/mcp"
    }
  }
}

Complete the browser authorization and confirm tool discovery. Other clients can use a different configuration shape. Self-hosted GrowthBook users should follow the local stdio or self-hosted HTTP instructions rather than point a private instance at the Cloud service.

Next, let the connected agent discover the flag-creation workflow. These are tool-call parameters, shown separately in the order to invoke them:

{"name":"growthbook_list_skills","arguments":{}}

{"name":"growthbook_read_skill","arguments":{"name":"feature-flags"}}

{"name":"growthbook_read_skill","arguments":{"name":"feature-flags/references/flag-create"}}

The returned guidance should describe the prerequisites for creating the flag. If the workflow isn't present, resolve the server's bundled skill version before substituting instructions from an older integration.

Resolve real IDs and construct one payload

The flag-creation workflow checks existing keys, lists projects, and resolves environments. In the MCP client, invoke the read tool with each of these argument objects:

For the CLI route, perform that discovery with the corresponding command groups documented in the CLI command catalog:

growthbook features list-keys --output-format json
growthbook projects list --output-format json
growthbook environments list --output-format json

Inspect each command's help if your installed version differs. The returned keys, project IDs, and environment IDs are the inputs to the payload below. In MCP, the equivalent read-tool arguments are:

{"path":"/api/v2/feature-keys"}

{"path":"/api/v1/projects"}

{"path":"/api/v1/environments"}

Verify that checkout-redesign isn't taken, identify the sandbox project's ID, and enumerate every actual environment. These read responses determine the payload; don't treat example environment names as a complete inventory of your organization.

Save the following as flag.json, replacing <PROJECT_ID> and the environment keys with the discovered values. This example assumes the only environments are staging and production:

{
  "id": "checkout-redesign",
  "valueType": "boolean",
  "defaultValue": "false",
  "description": "Control exposure to the redesigned checkout",
  "project": "<PROJECT_ID>",
  "environments": {
    "staging": { "enabled": false },
    "production": { "enabled": false }
  }
}

The API represents defaultValue as a string, even for a Boolean flag. Explicitly disabling each environment avoids relying on the organization's default state for newly created flags. Use a PAT for this example so the caller has a user identity for attribution.

Review the permanent key, project, value, and disabled states before submitting. If the intended job is an experiment, route to experiment design first instead of creating an unrelated flag and hoping to connect it later.

Submit once, then read the object back

With the CLI, the create command accepts a JSON body. In a Bash-compatible shell, inspect the request with dry run before submitting:

growthbook features create --body "$(cat flag.json)" --dry-run
growthbook features create --body "$(cat flag.json)" --output-format json

The first command previews a request; it doesn't prove the server will accept it. Run the second only after checking the preview and approving this creation. In PowerShell, use that shell's file-reading syntax rather than paste the Bash substitution unchanged.

The PowerShell equivalent, using the same reviewed file, is:

$flagPayload = Get-Content -LiteralPath .\flag.json -Raw
growthbook features create --body $flagPayload --dry-run
growthbook features create --body $flagPayload --output-format json

The same distinction applies: preview first, approve the specific creation, then submit. Neither command changes the application's deployed code.

Through MCP, call growthbook_api_write with the same payload serialized into its body string. Substitute the same resolved project and environment names:

{
  "method": "POST",
  "path": "/api/v2/features",
  "body": "{\"id\":\"checkout-redesign\",\"valueType\":\"boolean\",\"defaultValue\":\"false\",\"description\":\"Control exposure to the redesigned checkout\",\"project\":\"<PROJECT_ID>\",\"environments\":{\"staging\":{\"enabled\":false},\"production\":{\"enabled\":false}}}"
}

Choose one creation route. Don't run both against the same key; they target the same product object, and the second creation should encounter an existing key.

Verify through the CLI get command:

growthbook features get --id checkout-redesign --output-format json

Or invoke growthbook_api_read with:

{"path":"/api/v2/features/checkout-redesign"}

Check the returned key, project, value type, default value, disabled state of every environment, and absence of unintended rules. Report those facts rather than “success.” No targeting or exposure change is included in this example.

Choose the route that fits the runtime

Once the procedure and API operation are shared, the remaining choice is operational. Where does the agent run? What can it execute? How does it authenticate? What does your team need to inspect afterward?

Shell access favors terminal composition

A shell-capable agent can run the CLI alongside repository tools, save structured output, and combine product inspection with local checks. That is useful when the job includes code changes, generated files, or a reproducible script.

For example, a flag audit can produce an inventory file while an engineer separately checks code references. The agent should preserve the association between the GrowthBook key and each repository reference. The final artifact can include both the product state and the proposed code diff.

The shell makes composition available; it doesn't make a workflow safe by default. A script can select the wrong profile or swallow an error. Decide which failures stop the workflow, where outputs are stored, and which steps need a reviewable artifact.

Remote tool access favors MCP clients

MCP is useful when the host already provides a tool connection but doesn't expose a terminal. A PM can inspect an experiment through a compatible assistant without installing a product CLI inside that assistant's runtime.

The MCP authorization specification defines an authorization framework for HTTP transports. GrowthBook Cloud uses browser OAuth, while local stdio configurations use credentials supplied to the process. Those are distinct deployment paths.

MCP also gives hosts a structured description of tools. The tool specification includes annotations such as read-only and destructive hints. Hosts can use those signals in their interaction design, but the signals are not an access-control boundary. The product must still enforce the caller's actual permissions.

Use a small decision table

Your immediate requirement	Route to consider	What to verify
Combine product operations with local files and scripts	CLI plus maintained skills	Shell access, profile, installed version, structured output
Connect a compatible assistant without a shell	Hosted MCP	HTTP/OAuth support, identity, tools, bundled workflow
Keep requests inside a self-hosted deployment	CLI or self-hosted MCP	Network reachability, server version, credentials, trusted app origin
Reuse a procedure across different team clients	Shared skills through either route	Workflow revision, API compatibility, expected review artifact

You can support more than one row. An engineer's CLI and a PM's MCP connection can operate on the same objects with different identities and permissions. Standardizing the workflow is often more useful than standardizing everyone's client.

Compare actual outcomes, not tool counts

Four MCP tools can address a large API. A large CLI command catalog can expose the same operations. Counting entries tells you little about whether an agent completed the intended job correctly.

Likewise, there is no universal token or speed result implied by the architecture. The client, model, instructions, response size, pagination, and number of requests all affect a real run. Measure the work you need instead of importing a result from an unrelated integration.

Keep the evaluation task constant

Use one sandbox project and one bounded task. For a read test, ask each route to find a named flag and identify its enabled environments, current revision, and relevant dependencies. For a write test, use separate temporary keys with the same reviewed disabled-flag requirements.

Give both runs the same expected output. Record whether each identified the correct objects, loaded the relevant workflow, handled missing data, and preserved the boundary between creation and exposure. Measure elapsed time and context consumption only alongside those correctness checks.

If one run gets rich workflow guidance and the other gets only a command name, you're testing the guidance as well as the interface. That can still be a useful product evaluation, but describe what changed.

Test failure behavior deliberately

Try a nonexistent object, an existing key, and a credential without the required permission. The agent should identify the failure and stop the dependent action. It should not invent an ID, silently pick another environment, or reinterpret a permission error as permission to retry with a broader credential.

The revision workflow adds another important test: multiple open drafts. When a chain of changes belongs in one revision, the agent must preserve its version rather than repeatedly ask for whichever draft is latest.

A creation receipt and a publication receipt are different artifacts. If your evaluation only checks that a request returned without error, it can miss the point where a proposed change became live or where a draft failed to include the intended edits.

Record the versions behind the result

Capture the CLI version, server version when available, client configuration, and the skill text or revision used. With MCP, inspect the guidance actually returned by the connected server. With installed skills, inspect the local instructions actually loaded.

That record makes a later regression diagnosable. A changed result may come from new guidance, a client update, a changed API, or different product state. “MCP became worse” is too broad to help you fix it.

Build workflows that survive the next client

The most useful consequence of GrowthBook's design is organizational. Engineers, PMs, and analysts can choose the agent surface that fits their work while referring to the same flags, experiments, and metrics.

An engineer can prepare a disabled flag from a terminal. A reviewer can inspect its draft in the app. An assistant connected through MCP can retrieve the same object and explain its state. The handoff should carry an ID, a revision where applicable, the proposed behavior, and the decision still required.

This is where the CLI-versus-MCP question loses much of its importance. Your release procedure doesn't need to be rewritten around each client. The product holds state; the API exposes operations; skills explain the work; the chosen interface delivers access.

Start with one inspection or sandbox creation. Require the agent to return a concrete object and its verified state. Then add the next workflow only when the current one is reliable enough for your team to review.

GrowthBook's feature flag platform gives that work a common place to live. The durable choice is how you connect release control and measurement to your team's process. CLI and MCP are ways to carry that process into the tools people already use.

Start with a common foundation

Set up GrowthBook for the flags, experiments, and metrics your agents will share. Then choose the CLI or MCP connection that fits each team member's work.

Get Started With GrowthBook

Experiments

Analytics

Standard deviation vs variance: Key differences for A/B testers

Oct 21, 2026

min read

A metric can have wide user-to-user variation and still yield a precise experiment estimate.

That is why confusing standard deviation with standard error creates bad A/B testing decisions. A dashboard may show that users differ substantially while the average effect is estimated closely enough to guide a release. Those statements can both be true.

Variance and standard deviation describe spread. Variance works on a squared scale; standard deviation takes its square root to return to the metric's original units. Neither is automatically the uncertainty around an experiment result.

For A/B testers, the useful distinction is practical: use standard deviation to communicate outcome variability, use variance in the calculations that combine uncertainty, and inspect the standard error or interval for the treatment effect. Start by making sure all three describe the correct unit of analysis.

Understand the difference in units

Variance uses squared distances

Outcomes above and below a mean have deviations with opposite signs. Simply averaging those signed deviations gives zero. Variance avoids that cancellation by squaring each deviation before combining them.

The sample variance formula is s² = Σ(xᵢ − x̄)² / (n − 1), where x̄ is the sample mean and n is the number of observations. The symbol Σ means to add the terms across observations.

If the outcome is measured in seconds, variance is measured in seconds squared. That is mathematically useful but less intuitive for explaining a product experience. “Variance is 4 seconds squared” does not mean users differ by 4 seconds.

Standard deviation returns to the original scale

Standard deviation is s = √s². A variance of 4 seconds squared corresponds to a standard deviation of 2 seconds. Both describe the same dispersion, expressed on different scales.

Do not define standard deviation as the average absolute distance from the mean. That is a different measure. Squaring deviations gives large deviations more influence, and taking the square root afterward does not undo that weighting.

Quantity	What it describes	Units for task time
Variance	Squared dispersion in outcomes	Seconds squared
Standard deviation	Outcome dispersion on the original scale	Seconds
Standard error of the mean	Sampling variability of an estimated mean	Seconds

Neither variance nor standard deviation requires a normally distributed population merely to be calculated. Normality matters for particular interpretations and inferential procedures, not for the existence of these summaries when the required moments are finite.

Calculate both from the same observations

Work through a small dataset

Use four synthetic task times: 2, 4, 4, and 6 seconds. This tiny dataset is for arithmetic, not evidence about a real product or a basis for confident inference.

The mean is (2 + 4 + 4 + 6) / 4 = 4 seconds. Deviations from the mean are −2, 0, 0, and 2 seconds. Their squares are 4, 0, 0, and 4 seconds squared, totaling 8.

Treating these observations as a sample, the usual sample variance is 8 / (4 − 1) = 8/3, or about 2.667 seconds squared. The sample standard deviation is √(8/3), or about 1.633 seconds.

This is a useful check on a report. If someone describes the same sample's variance as 1.633, they have probably substituted the standard deviation. If the units are missing, the mistake is much harder to spot.

Choose sample or population formulas deliberately

If those four observations constitute the entire finite population you want to describe, population variance divides by 4: 8/4 = 2 seconds squared. Population standard deviation is √2, or about 1.414 seconds.

The population and sample distinction depends on what you are estimating. Having every recorded event from an experiment does not necessarily make those events the full population of future users or future conditions you care about.

The n − 1 denominator makes the usual sample variance an unbiased estimator of population variance under independent, identically distributed sampling with finite variance. It does not make the square root exactly unbiased for population standard deviation. Nor does it correct biased sampling or dependence between observations.

Verify the calculation with explicit function names

Python's statistics functions distinguish sample calculations from population calculations. With Python 3 installed, this standalone example requires no external packages or data:

from statistics import variance, stdev, pvariance, pstdev

times = [2, 4, 4, 6]
print(round(variance(times), 3), round(stdev(times), 3))
print(round(pvariance(times), 3), round(pstdev(times), 3))

The first line of output is 2.667 1.633; the second is 2 1.414. The different denominators explain the difference. Before comparing statistics from two tools, check their sample/population defaults and handling of missing values.

Find the noise you can reduce

Explore practical variance reduction methods, including metric design and CUPED, and the conditions that make each approach useful.

Read the Variance Reduction Guide

Use standard errors for experiment uncertainty

Distinguish users from estimated means

Standard deviation describes how users' outcomes vary. Standard error describes how an estimator would vary across repeated samples. For an independent sample, the estimated standard error of its mean is s / √n.

Suppose a user-level task-time metric has a sample standard deviation of 20 seconds among 10,000 independent users. The estimated standard error of the mean is 20/√10,000 = 0.2 seconds. Large differences between users coexist with a much smaller uncertainty around their average.

Collecting four times as many independent users would halve this standard error if the outcome variance stayed similar. It would not mechanically halve user-level standard deviation. The individual experience remains variable even as the estimated mean becomes more precise.

Combine arm variances before taking the square root

For independent treatment and control groups, a simple unadjusted difference in means has estimated variance s²ₜ/nₜ + s²꜀/n꜀. Its standard error is the square root of that sum. You do not add the two arm standard deviations and call the result the experiment's uncertainty.

Take a separate synthetic summary with 10,000 independent users in each arm and a 20-second standard deviation in both. The variance of the estimated difference is 400/10,000 + 400/10,000 = 0.08 seconds squared. Its standard error is √0.08, about 0.283 seconds.

If the observed treatment-minus-control difference is −1 second, an illustrative large-sample, unadjusted 95% normal interval is −1 ± 1.96 × 0.283, approximately −1.554 to −0.446 seconds. Negative values mean faster completion under this metric definition.

This example assumes independent groups and an appropriate large-sample approximation. It is not the exact output of GrowthBook's relative-lift, sequential, covariate-adjusted, or ratio-metric methods. GrowthBook's statistical details describe how the platform estimates effects and their uncertainty.

Avoid interpreting intervals as outcome ranges

That interval concerns the mean treatment effect. It does not say that 95% of individual users improved by between 0.446 and 1.554 seconds. An individual user's causal effect is a different quantity, and the experiment does not observe both potential outcomes for the same person.

Likewise, mean ± one standard deviation is not a universal statement about where 68% of users fall. That familiar interpretation depends on an approximately normal distribution. Skewed task times or revenue can look very different.

The frequentist confidence level describes the repeated-sampling coverage of the interval procedure under its assumptions. It is not a posterior probability assigned to a fixed realized interval.

Check what your metric actually measures

Match the variance to the randomization unit

If users are randomized and each contributes many requests, request rows are not automatically independent experimental units. Treating 100 requests from one person as 100 unrelated users can make uncertainty look smaller than it should.

Define the outcome at the intended unit or use a method that accounts for clustering. GrowthBook's aggregate data requirements are relevant when supplying precomputed summaries: the sample size, sum, and dispersion must correspond to the statistic and analysis method.

Two teams can report different standard deviations without either making an arithmetic mistake. One may summarize per-request latency while the other summarizes each user's average latency. They are describing different outcome distributions. Clarify the grain before comparing their numbers.

Paired measurements need another distinction. If the same users provide before-and-after outcomes, the measurements within each pair can be correlated. Analyze each user's difference or use an appropriate paired method; do not apply the independent-arm formula automatically. The paired-means framework treats those differences as the observations of interest. Pairing also does not remove time trends or establish causality by itself; the design still determines which comparison is defensible.

Inspect tails instead of deleting them casually

Large observations influence both variance and standard deviation. A few unusually long tasks can dominate a time metric; a few large purchasers can dominate revenue. Determine whether those values reflect valid behavior, instrumentation defects, retries, or unit errors.

A valid expensive user is not automatically an outlier to discard. Removing high values after seeing an experiment result can change the estimand and introduce selective analysis. Decide justified exclusions or transformations before interpreting the test.

Report complementary summaries when they answer useful questions: a histogram, median, or a relevant tail percentile can show what a single spread measure hides. Those summaries do not replace the mean effect if the mean remains the decision metric.

Keep units consistent across pipelines

Converting seconds to milliseconds multiplies every value by 1,000. Standard deviation also multiplies by 1,000, but variance multiplies by 1,000,000. A dramatic numerical variance increase can therefore be a unit conversion rather than a product regression.

For the four-value example, sample standard deviation becomes approximately 1,633 milliseconds and variance becomes approximately 2,666,667 milliseconds squared. The underlying task times have not changed. Store units with metric definitions and inspect them when comparing dashboards.

A lower variance caused solely by rescaling a metric does not create more statistical information. The effect size rescales too. Separate a numerical change in units from an actual improvement in the precision of your estimate.

Also avoid averaging standard deviations from daily reports and labeling the result a weekly standard deviation. The complete-period spread depends on both variation within days and differences between daily means. Keep the underlying observations or sufficient summaries that support the intended calculation. A simple average of displayed daily values generally loses information needed to reconstruct the full distribution.

Turn spread into a better testing plan

Define the outcome before planning the sample

Start with the metric definition: population, identity, aggregation, window, units, exclusions, and desired effect. Estimate variability from representative historical data at that same grain.

Historical variance is an input, not a guarantee. New traffic, a different user mix, or a changed measurement window can alter it. Explore plausible variance and effect-size assumptions rather than treating one historical number as exact.

Keep the two arm variances separate when appropriate. A treatment can change variability as well as its mean. The simple equal-standard-deviation illustration above is a teaching assumption, not a requirement that production groups have identical spread.

Reduce estimation noise without hiding behavior

CUPED and post-stratification use suitable pre-experiment information and covariates to improve effect estimation. CUPED stands for Controlled-experiment Using Pre-Experiment Data. Its value depends on useful predictive information and a valid implementation.

Adjustment can reduce uncertainty in the treatment effect without making real users' outcomes less variable. That distinction prevents a reporting error: a narrower adjusted interval is not evidence that customers now experience a more consistent product.

Also separate missing data from genuine zeros. A user with no purchase may correctly contribute zero revenue; a missing instrumentation event might represent an unknown outcome. Treating both identically can distort the mean and its variance before any statistical engine sees the data.

Report the right quantity for the decision

Reader's question	Useful quantity
How much do individual outcomes differ?	Standard deviation, with distribution context
What enters this uncertainty calculation?	Variance at the correct analysis unit
How precisely is the effect estimated?	Standard error and an appropriate interval
Is the measured difference worth acting on?	Effect size, uncertainty, guardrails, and decision context

For a clear experiment readout, show the metric's unit and analysis grain, the estimated effect, and its appropriate uncertainty interval. Add outcome spread when it helps readers understand the population or diagnose a noisy metric.

GrowthBook's experimentation platform brings defined metrics and statistical analysis together. A trustworthy interpretation still starts with your measurement choices: describe spread with standard deviation, calculate with variance where required, and judge precision using the estimator's uncertainty.

Build a clearer experiment readout

Connect your metrics to GrowthBook and evaluate effects with the analysis method and measurement definitions your team has chosen.

Get Started With Experimentation

Experiments

Analytics

How to calculate true positive rate (TPR)

Oct 21, 2026

min read

Catching 80 defects means little until you know how many defects existed.

Suppose a detector flags 125 suspicious software changes. Engineers inspect them and confirm 80 real defects. That tells you something about alert quality, but it does not tell you how many defects the detector missed. To calculate true positive rate, you need the actual positives outside the alert queue too.

True positive rate, or TPR, measures the share of actual positive cases that a system correctly identifies. It is also called recall or sensitivity. The formula is TP / (TP + FN), where TP means true positives and FN means false negatives.

The arithmetic is simple. Choosing the right population, labels, threshold, and denominator is the difficult part. This guide works through an engineering example, distinguishes neighboring metrics, and explains what changes when the “test” is an A/B experiment rather than an item classifier.

Start with actual positives, not alerts

Define the positive class

“Positive” means the condition you want to detect. It does not necessarily mean a good outcome. In a defect detector, positive means a real defect. In a spam filter, it means spam. Write that definition before calculating anything.

A true positive is an item that is actually positive and predicted positive. A false negative is actually positive but predicted negative. Those two groups together form the denominator: all actual positives in the evaluation sample.

The recall definition is therefore conditional on actual class membership. TPR asks, “Among the real defects, what proportion did we catch?” It does not ask, “Among the alerts, what proportion were real?”

Fix the unit and observation window

Choose a consistent evaluation unit. A code change, an individual finding, and a repository are different units. If one change generates 12 duplicate alerts, counting alerts in the numerator and changes in the denominator produces a meaningless rate.

For the example, each unit is one code change, evaluated once by one fixed detector version at one fixed threshold. An independent review process eventually labels each change as defective or not defective. The observation window is long enough for those labels to mature.

This resembles the discipline needed when defining experiment metrics: the event, identity, time window, and denominator must describe the same question. A correct formula applied to incompatible counts still gives the wrong answer.

Calculate TPR from the confusion matrix

Put every evaluated item in one cell

Consider an original synthetic evaluation of 1,000 code changes. Reviewers establish that 100 contain a defect and 900 do not. The detector catches 80 defects, misses 20, and incorrectly flags 45 nondefective changes.

Actual label	Predicted positive	Predicted negative	Total
Defective	80 true positives	20 false negatives	100
Not defective	45 false positives	855 true negatives	900
Total	125	875	1,000

Read the labels rather than relying on cell position. Libraries and reports can arrange axes differently. The scikit-learn confusion matrix convention uses actual classes on rows and predicted classes on columns, with class order also affecting where each value appears.

Check the totals before calculating rates. The four cells sum to 1,000. True positives plus false negatives sum to 100 actual defects. Predicted positives total 125, which is a different denominator.

Divide detected positives by all actual positives

The calculation is:

TPR = TP / (TP + FN) = 80 / (80 + 20) = 80 / 100 = 0.80 = 80%.

Interpret it in words: the detector caught 80% of the actual defects in this evaluation sample. It missed 20%, so the false negative rate is 20%. For a binary task with complete labels, TPR and false negative rate sum to 100%.

Do not divide 80 by 1,000. That would measure true positives as a share of all evaluated changes, not recall. Do not divide 80 by 125 either. That is precision, which answers the alert-quality question.

The result describes this sample and threshold. It does not establish that every future workload will have the same recall, or that all defect categories are equally detectable. Keep the counts beside the percentage so readers can see the support behind it.

Handle zero positive support explicitly

If the sample contains no actual defects, TP + FN equals zero. Sample TPR is undefined. Returning 0% would imply the detector missed known defects; returning 100% would imply it successfully found them. Neither interpretation is supported.

Software libraries need a practical zero-division convention. That convention can return a placeholder or warning, but it does not create evidence. Report “TPR unavailable: zero actual positives” and preserve the support count. A pipeline can then distinguish an unevaluable slice from measured poor performance.

Check the experiment error risks

See how power, repeated checks, and multiple comparisons affect the reliability of experimental decisions beyond a single classifier score.

Read the False Positives Guide

Compare TPR with precision and false positives

Keep the denominators visible

For the same 1,000 changes, the other common metrics tell different stories:

Metric	Calculation	Result
True positive rate / recall	80 / 100 actual positives	80%
Precision	80 / 125 predicted positives	64%
False positive rate	45 / 900 actual negatives	5%
Specificity	855 / 900 actual negatives	95%
Accuracy	(80 + 855) / 1,000 changes	93.5%

The classification metric definitions differ because they condition on different populations. Here, 36% of alerts are false, but the false positive rate is 5%. Calling both numbers “the false positive rate” hides the operational distinction.

Accuracy can also look reassuring in an imbalanced population. A detector that labels all 1,000 changes nondefective would be 90% accurate while detecting none of the 100 defects. TPR exposes that failure, though it still needs the false-positive side of the picture.

Choose a threshold for the decision

Suppose a stricter threshold, evaluated on the same labeled changes, catches 60 defects and incorrectly flags 10 nondefective changes. Its TPR is 60%, its precision is about 85.7%, and its false positive rate is about 1.11%.

This threshold reduces the review queue from 125 changes to 70. It also misses 40 defects instead of 20. Whether that tradeoff is acceptable depends on the consequences of a missed defect, the review team's capacity, and what action follows an alert.

A ROC curve plots TPR against false positive rate across thresholds. It helps compare operating points. It does not pick the operational threshold for you, and an area-under-curve summary does not specify the queue size at the threshold you intend to deploy.

If you tune thresholds using the same labels you later report as a final evaluation, the score can be optimistic. Use separate validation and held-out evaluation data, or another defensible evaluation design, and freeze the decision rule before the final assessment.

Specify the action at each threshold too. A low-confidence finding might create a suggestion, while a high-confidence finding might block a merge. Those are different interventions with different error costs. One aggregate recall figure should not imply that every detected item received the same treatment.

Make sure the labels can support the claim

Audit predicted negatives too

If engineers review only alerts, you can estimate precision within the reviewed alert population. You cannot directly count missed defects among unreviewed negatives. Assuming those changes are clean makes FN artificially small and TPR artificially high.

An evaluation may need independent review of a representative sample of predicted negatives, delayed incident labels, or a curated benchmark with known defects. Each approach has limits. Incident labels miss undetected failures; curated examples can differ from ordinary production work.

If the evaluation oversamples suspicious changes or certain repositories, report that design. Use appropriate weighting when estimating performance for the real workload. A simple unweighted confusion matrix describes the sampled dataset, which may not represent the deployed population.

Preserve uncertainty and segment support

An 80% estimate based on 4 detected defects out of 5 is much less precise than one based on 800 out of 1,000. The important sample size for recall is the count of actual positives, not just the total number of changes evaluated.

Report positive support by important slices, such as language, defect category, or repository type. A high pooled TPR can hide weak performance on a rare but expensive failure mode. At the same time, avoid declaring tiny slices definitively better or worse from a few examples.

Counts alone do not make observations independent. Many similar changes from one repository can share a common pattern. Use uncertainty methods that fit the evaluation design rather than assuming every row is an unrelated trial.

Separate label delay from label absence

A recently deployed change might appear nondefective because nobody has had time to find the bug. Treating it as a confirmed negative gives the newest cohort a different labeling standard from older cohorts.

Define when an item becomes eligible for evaluation and track unresolved labels separately. Keep model version, threshold, label version, and observation dates with the result. That makes a later score change interpretable: you can tell whether the detector changed, the workload changed, or the labels matured.

For a warehouse-native measurement workflow, these definitions belong in the underlying data model. Joining model decisions to review outcomes still requires identity and time alignment; a queryable warehouse does not automatically resolve ambiguous ground truth.

Keep comparable populations together

When comparing detector versions, evaluate them on the same held-out cases where possible. Otherwise, an apparent recall improvement could come from an easier mix of defects. Preserve a breakdown of new, removed, and unchanged cases so reviewers can see what changed between evaluations.

When combining reports, add the underlying TP and FN counts for nonoverlapping, consistently defined populations, then calculate the pooled rate. An unweighted average of repository percentages answers a different question because it gives a tiny repository the same influence as a large one. Either summary can be useful, but label the weighting explicitly.

If the same change appears in several reports, deduplicate or model that repeated observation before pooling. Repeated scans do not create additional independent defects. Keep an audit trail from the final counts back to the evaluated item identifiers so a suspicious rate can be investigated.

Connect detection quality to product decisions

Distinguish classifier recall from statistical power

In hypothesis testing, statistical power is the probability that a testing procedure rejects the null when a specified alternative is true. It is a repeated-test detection probability, depending on assumptions such as effect size, variance, sample size, and decision rule.

That is related to the idea of detecting a real signal, but it is not the same dataset as a labeled-item confusion matrix. In an ordinary A/B program, you do not observe the true causal effect of every experiment with certainty. Dividing declared winners by all experiments does not reveal a ground-truth TPR.

Power planning asks how often your procedure would detect a particular real effect under its assumptions. A classifier evaluation asks how many labeled positives were detected in the evaluated sample. Keep those questions separate when discussing GrowthBook's statistical methods.

Evaluate the intervention as well as the detector

An improved offline detector can still create a worse product workflow. More alerts might overwhelm engineers, delay releases, or catch defects too late to matter. Conversely, a modest recall change might be valuable if it catches the failures with the highest operational cost.

When appropriate, use randomized experiments to evaluate the downstream intervention: which review experience helps teams resolve defects, with what delay and cost? Keep detector recall, review workload, and product outcomes as separate measures.

GrowthBook's experimentation platform can analyze defined outcomes from such tests. Your team supplies reliable assignment, exposure, labels, and metric definitions. Neither a high TPR nor a significant product result eliminates the need to inspect the other evidence.

Use a repeatable reporting checklist

Before sharing a TPR number, state the positive class, evaluation unit, detector version, threshold, and label process. Show TP and FN beside the rate. Include precision or false positive rate so readers can assess the workload created by detection.

Then ask whether predicted negatives were evaluated, whether labels had time to mature, and whether the sample reflects the population where you will act. Mark zero-support slices unavailable and explain material gaps in coverage.

The useful result is a statement someone can audit: “At this threshold, the detector found 80 of 100 labeled defects in these 1,000 evaluated changes, while producing 45 false alerts.” That is a clearer basis for a decision than “our model is 80% accurate.”

Measure what the change delivers

Connect your data and defined metrics to GrowthBook to evaluate how a product or workflow change affects the outcomes your team cares about.

Start Measuring With GrowthBook

Ready to ship faster?

No credit card required. Start with feature flags, experimentation, and product analytics—free.

Get Started

Book a Demo

Simplified white illustration of a right angle ruler or carpenter's square tool.

White checkmark symbol with a scattered pixelated effect around its edges on a transparent background.

Standard A/B testing breaks when the treatment is never the same twice.

Why traditional A/B testing breaks down for AI personalization

The fixed-treatment assumption standard A/B testing actually requires

How AI personalization violates that assumption by design

What this means for experiment validity

Separating user-level effects from model-level effects in AI personalization experiments

What selection bias actually looks like in AI systems

Randomization unit design — why user-level hashing is the foundation

Holdout groups for isolating model-level effects

Auditing for residual confounding

Lift numbers lie when every user receives a different AI-generated treatment

Why average treatment effects fall short for heterogeneous AI outputs

SUTVA violations and the evolving treatment problem

CUPED and regression adjustment for pre-experiment normalization

Activation metrics and guardrail metrics

Avoiding bias and fairness pitfalls in AI personalization experiments

How AI personalization systems encode and amplify historical bias

Why aggregate lift metrics hide differential impact

Metric slicing and cohort-level guardrails

The infrastructure gap that makes continuous AI personalization testing fail

Linking feature flags to model versions

Bandit-style traffic allocation for adaptive learning

Warehouse-native analysis as the source of truth

Capturing institutional knowledge to compound personalization learnings

What valid AI personalization experiments actually require

The non-negotiable foundations: randomization, measurement, and bias detection

Infrastructure decisions that determine whether your experiment results are trustworthy

Start with the holdout: the one experiment that surfaces every structural problem

Related insights

Sign up for free

Table of Contents

Related Articles

CLI vs MCP: TLDR, it doesn’t matter as much as you think

Your agent should know how to do the job whichever interface it uses.

The debate combines three different questions

How can the agent reach the product?

What procedure should the agent follow?

What context makes the procedure relevant?

GrowthBook puts the durable parts below the interface

The API provides the operations

Skills provide the workflow guidance

MCP provides a thin bridge

Explore the shared flag workflows

The same disabled flag can use either route

Connect and verify before preparing the write

Resolve real IDs and construct one payload

Submit once, then read the object back

Choose the route that fits the runtime

Shell access favors terminal composition

Remote tool access favors MCP clients

Use a small decision table

Compare actual outcomes, not tool counts

Keep the evaluation task constant

Test failure behavior deliberately

Record the versions behind the result

Build workflows that survive the next client

Start with a common foundation

Standard deviation vs variance: Key differences for A/B testers

A metric can have wide user-to-user variation and still yield a precise experiment estimate.

Understand the difference in units

Variance uses squared distances

Standard deviation returns to the original scale

Calculate both from the same observations

Work through a small dataset

Choose sample or population formulas deliberately

Verify the calculation with explicit function names

Find the noise you can reduce

Use standard errors for experiment uncertainty

Distinguish users from estimated means

Combine arm variances before taking the square root

Avoid interpreting intervals as outcome ranges

Check what your metric actually measures

Match the variance to the randomization unit

Inspect tails instead of deleting them casually

Keep units consistent across pipelines

Turn spread into a better testing plan

Define the outcome before planning the sample

Reduce estimation noise without hiding behavior

Report the right quantity for the decision

Build a clearer experiment readout