Skip to content
Confidence
  • Documentation
  • Blog
  • Bootcamp
  • Status
  • Confidence Bootcamp
    • My learning
    • Intro to experimentation
      • Introduction
      • Lesson 1: Why you should experiment
      • Lesson 2: Experiment hypothesis
      • Lesson 3: Success and guardrail metrics
      • Lesson 4: Success metrics
      • Lesson 5: Set up your experiment
      • Lesson 6: Calculation frequency
      • Lesson 7: Target audience
      • Lesson 8: Sample size
      • Lesson 9: Quality assurance
      • Lesson 10: Run your experiment
      • Lesson 11: Evaluate your experiment and make a decision
      • Lesson 12: A/B tests and rollouts
      • Course wrap up
    • Intro to metrics
      • Introduction
      • Lesson 1: What is a metric?
      • Lesson 2: Metric roles
      • Lesson 3: Time considerations
      • Lesson 4: Capturing behavior
      • Lesson 5: Strategic metrics
      • Lesson 6: Interpretability
      • Lesson 7: Feasibility and sensitivity
      • Lesson 8: Variance reduction and metric selection
      • Lesson 9: Select metrics
      • Lesson 10: Segment-level analysis
      • Course wrap up
    • Scientific product development
      • Introduction
      • Lesson 1: Why you should experiment
      • Lesson 2: The scientific method
      • Lesson 3: Randomized controlled trials
      • Lesson 4: Experiment hypothesis
      • Lesson 5: Case study
        • Case study
        • Answers to case study
      • Lesson 6: Why do we need statistics?
      • Lesson 7: Success metrics
      • Lesson 8: Detectable effects and sample size
      • Lesson 9: Make a decision
      • Course wrap up
    • A primer on hypothesis testing
      • Introduction
      • Lesson 1: Introduction to hypothesis testing
      • Lesson 2: True vs estimated effects
      • Lesson 3: Sampling distribution of the difference-in-means estimator
      • Lesson 4: Z-tests and how to reject the null hypothesis
      • Lesson 5: False postive rate and alpha
      • Lesson 6: True positive rate, MDE, and power
      • Course wrap up
    • Intro to Feature Flags
      • Introduction
      • Lesson 1: What is a feature flag?
      • Lesson 2: Lifecycle of a feature flag
      • Lesson 3: Clients
      • Lesson 4: Evaluation context and targeting
    • Sample size calculation - I
      • Introduction
      • Lesson 1: What is the required sample size?
      • Lesson 2: Alpha and power
      • Lesson 3: Baseline mean and variance
      • Lesson 4: Sample size playground - I
    • Sample size calculation - II
      • Introduction
      • Lesson 1: Multi-metric decision making
      • Lesson 2: Number of success metrics
      • Lesson 3: Number of guardrail metrics
      • Lesson 4: Number of comparisons
      • Lesson 5: Sample size playground - II
    • Sample size calculation - III
      • Introduction
      • Lesson 1: Binary metrics
      • Lesson 2: Treatment group proportions
      • Lesson 3: Variance reduction
      • Lesson 4: Sequential testing and sample size
      • Lesson 5: Sample size playground - III
    • Advance your experimentation
      • Introduction
      • Lesson 1: Guardrail metrics with non-inferiority margins
      • Lesson 2: Choose evaluation frequency
      • Lesson 3: Metrics' roles in experiments
      • Lesson 4: Cumulative holdback evaluations
    • Experimentation culture
      • Introduction
      • Lesson 1: Onboarding into experimentation
      • Lesson 2: Empowering experimentation champions
      • Lesson 3: Sustaining the experimentation culture
    • Videos

Lesson 2: Choose evaluation strategy: Sequential or non-sequential tests

Summary

What evaluation frequency you choose determines if your experiment uses a sequential or a non-sequential test. Optimize your experimentation by choosing the test that fits your needs.

  • Sequential tests let you look at your results and make decisions during the experiment but have lower power than non-sequential tests.
  • Non-sequential tests only let you look at the results and make decisions once the experiment has ended but has higher power than sequential tests.

In this lesson you learn how to select evaluation frequency and the various trade-offs to consider when making this choice.

This video gives a 2 minutes and 10 seconds overview of the evaluation frequency topic.

The evaluation frequency determines the statistical test

The evaluation frequency has two options:

  • Continuous: lets you see results during the experiment
  • Upon conclusion: lets you see results only when the experiment has ended

Continuous evaluation uses sequential tests

When you select continuous evaluation, Confidence automatically uses a sequential test behind the scenes. Sequential tests ensure that the repeated testing implied by calculating results continuously throughout the experiment does not inflate the risk of finding a false positive result.

There are two types of sequential tests:

  • Group Sequential Tests: require the experimenter to provide a maximum sample size and must be stopped once this sample size is reached; they have higher power than Always Valid Tests for a given sample size
  • Always Valid Tests: do not require any pre-specified sample size and can keep letting new users into the sample indefinitely; they have lower power than Group Sequential Tests for a given sample size
In Confidence

Confidence automatically chooses the type of sequential test based on whether you provide a maximum sample size or not. If you provide an expected sample size, Confidence uses a Group Sequential Test to maximize power; otherwise it uses an Always Valid Test.

Upon Conclusion evaluation uses non-sequential tests

When you select Upon Conclusion, Confidence automatically uses a fixed horizon test—the classical statistical tests from intro statistics courses.

Fixed horizon tests, such as the z-test, do not allow you to see the results during the experiment, but they have higher power for the given sample size after you stop the experiment and run the analysis as compared to the sequential tests. Although you should run sample size calculations before the experiment, you can view the powered effect at any point during the experiment, which makes it possible to judge when it is time to end it.

A note on quality tests during the experiment

Regardless of your choice of evaluation frequency, a well-designed experimentation platform uses continuous evaluation (sequential tests) on all quality and deterioration checks during the experiment. This means that you will not miss any experiments that deteriorate or have fatal errors, even if you choose Upon Conclusion as your evaluation frequency.

This means the only reason to select continuous evaluation is if you want to make a shipping decision as soon as possible.

In Confidence

When you create an A/B test or rollout in Confidence, you can select the evaluation frequency in the experiment settings.

A note on early stopping to ship a variant

Using sequential testing to detect harm and errors to abort failing experiments early is standard in modern A/B testing. However, stopping early to ship is less straightforward. This is because it is often easier to prove that something is too bad to ship than to prove that it is sufficiently good to ship.

A few things to consider are:

  • Time effects. If there are strong effects of for example weekdays it might be important to run the experiment over a full week to average these out
  • Novelty effects. If there is a strong novelty effect, it might be important to observe users for a longer time to determine the longer time effect of the change
  • Power. Under powered experiments tends to overestimate the treatment effect. If the effect is larger than you expect early in the data collection, you might want run it longer to ensure your experiment is well powered.

How to choose

Selecting evaluation frequency and thereby type of statistical test is a trade-off between various interests. Some general guidelines are:

  • The ability to abort failing experiments should not influence the choice of evaluation frequency. All experiments have sequential checks for deterioration and quality errors, regardless of the result evaluation frequency.
  • If speed of decision making is more important than the quality of the estimates, choose continuous evaluation
  • If you are using continuous evaluation, provide a maximum sample size if you can to use Group Sequential Tests that maximizes the power
  • If you are going to run the experiment for a fixed number of days anyway before making the decision to ship, use Upon Conclusion evaluation

For a guide on how to read and act on results depending on which evaluation strategy your experiment uses, see Lesson 9: Sequential and non-sequential tests in the Interpreting experiment results course.

The recommendation to experimenters at Spotify is to use the upon-conclusion evaluation frequency. This is because Confidence offers continuous deterioration and quality tests regardless of the evaluation frequency, there are many reasons to run tests for at least a fixed time period such as time effects and novelty effects, and upon-conclusion maximizes the chances to detect a true effect (power).

If you are interested in reading more about types of sequential tests and how they compare, checkout this Spotify engineering blog post about choosing a Sequential Testing Framework There is also more details about the tests in the documentation.

Reader exercise

When should you choose continuous evaluation?

Reader exercise

What is true for experiments using upon-conclusion evaluation?

Was this page helpful?

PreviousLesson 1: Guardrail metrics with non-inferiority margins
NextLesson 3: Metrics' roles in experiments

© Copyright 2026. All rights reserved.

Follow us on TwitterFollow us on GitHub

On this page

  1. The evaluation frequency determines the statistical test

  2. A note on quality tests during the experiment

  3. A note on early stopping to ship a variant

  4. How to choose