Apex

Graduation Pipeline

Graduation is how a winning experiment becomes part of your code. The snippet can keep serving the winner. Graduation removes that runtime dependency.

The old Graduation Pipeline board is gone. /dashboard/graduation-pipeline sends you to Experiments. Automation settings that used to live there now sit on Integrations → GitHub.

What you will see

On Experiments, each test that is linked to a pull request shows that link on the card. A promoted winner that is not yet in the repo is flagged as pending graduation.

The clock

The experiment clock starts on the first recorded visit in Production. Localhost and other Dev traffic do not decide the winner. See Environments.

From the editor

These MCP tools are the same path as the dashboard:

  • link_experiment — bind a pull request to the test
  • gate_experiment_on_merge — the test does not start until that PR merges
  • graduate_experiment — after you promote, get the recipe to put the winner in source

check_live_tests still runs before you edit a page that a live test is on.

After you promote

  1. Promote the winner on the experiment (website card or letter Experiment step).
  2. Call graduate_experiment or follow the recipe on the experiment page.
  3. Ship the code. Apex marks the test graduated when the native page matches the winner.
PreviousRunning experimentsNextBilling