The page at a glance#
The Experiment detail (/console/experiments/<id>) is the working page for one experiment. Every action after the brief happens here. From top to bottom:
- Header — identity, the live address and the actions.
- Banner — only when something about the status needs saying.
- Stat strip — four numbers that summarise the test.
- Tabs — one section of work at a time.
Header#
- Breadcrumbs: Experiments / product name.
- Title: the product name in serif, then pills for the status, the test type (Named prospects, Public audience or Experiment 000) and, when flagged, Past decision date.
- Offer: the brief's offer in one line.
- Page address (once published): the live URL, a Copy button, and "Snapshot vN · published
". - Actions on the right:
| Button | Shown when | What it does |
|---|---|---|
| Edit brief | Every experiment except 000 | Opens the Brief editor |
| Publish | Draft | Publishes (below) |
| Pause | Live | Pauses the page (Pause, resume and republish) |
| Resume | Paused | Serves the same snapshot again |
| ··· menu | Published, except 000 | Republish… (live only), Download export bundle, Close test… (live or paused) |
Banner#
| Banner | When | What it says |
|---|---|---|
| Red | Live and flagged past its decision date | The date passed; record a verdict, then close, republish with a revised offer, or keep running |
| Amber | Paused | The page shows "Not available right now"; forms and visits are refused; Resume serves the same snapshot |
| Red | Closing or closed | The page shows "This offer has closed"; the partner link is revoked; when the daily job will mark it closed |
Stat strip#
| Stat | Meaning |
|---|---|
| Decision | Days to the decision date (amber at 5 or fewer), or "Nd over" in red, with the full date |
| Thresholds met | How many of the test type's pass thresholds are met now, e.g. 1 / 3 |
| Offer-test hours | Intake + test hours against the cap, with the hours left or "over cap" (amber past 90%) |
| Feasibility risks | How many are open (amber when any), and how many are recorded |
A draft has no stat strip. Experiment 000 shows its own: studio visits in the last 30 days, applications (and how many in the last three weeks), accepted in three weeks against the target of 3, and recruitment hours.
Tabs#
The tabs are links (?tab=evidence), so each keeps its place on reload. Every action returns you to the tab you acted on, with a toast.
| Experiment | Tabs (the first opens by default) |
|---|---|
| Draft | Publish, Distribution, Activity, Risks |
| Live, paused, closing or closed | Evidence, Distribution, Activity, Risks, Review |
| Experiment 000 | Evidence, Activity, Review |
Badges: the Publish tab shows how many requirements are missing (amber), Risks shows how many are open (amber), and Review shows a red due when the decision date has passed.
Each tab has its own page in this guide: Distribution, Evidence, Activity, hours and feasibility risks and Review and verdict.
The Publish tab#
A draft opens here. The Required to publish card lists the six requirements with a ✓ or a !, and a note for each:
| Requirement | Done when |
|---|---|
| Buyer | The brief has a buyer |
| Offer | The brief has an offer (the page headline) |
| Price hypothesis | The brief has a price |
| Call to action + target | A card is chosen, with its link for Booking or Deposit |
| Decision date in the future | The date is set and has not passed |
| Product name | Not a draft-… placeholder, not reserved, not used by another experiment |
Finish the brief opens the Brief editor. Once all six are done, Publish now appears here too. The card beside it explains what publishing does. Open feasibility risks never block publishing.
Publishing#
- Click Publish (in the header, on the Publish tab, or in the Brief editor).
- The platform stores the page as snapshot version 1 (reason "initial publish", with the template version), sets the status to live and records the publish time. There is no deploy and no DNS step: the page is on its subdomain at once.
- You land on the Evidence tab with a green publish checks panel. The platform visits the new page like a buyer would and shows a ✓ or ✗ for each check:
| Check | What it proves |
|---|---|
| The page responds on its subdomain | The subdomain serves this experiment's page |
| A test lead is stored and deleted | The form works end to end (the test lead is removed afterwards) |
| A test visit is recorded with its prospect ref and deleted | The visit beacon records a personal link's ref (removed afterwards) |
| The privacy link resolves | The privacy notice loads |
The test rows are deleted, so they never count as evidence. A ✗ is something to investigate before sharing links; the experiment stays live either way. Dismiss hides the panel.
Only a draft can be published; changing a live page is Republish. Experiment 000 has no Publish action.