Editor workflow

Tests are managed in the Tests group of the Payload admin, which has All tests and Goals. Only people with access.manage see it. The Payload dashboard also shows All tests and Goals cards to them.

Create a testCopy Anchor Link

There are two ways in.

From the content. In Puck, add an Experiment block from the A/B tests category. In a Payload blocks field, use Test a block on this page. The block becomes a small test builder: name, status, a tab per version, and actions to add up to three variants, rename them, copy the Original into a version, remove a version and set the traffic split. These edits are available while the test is a draft or stopped.

From Tests. New test offers three cards:

• A block on a page lists pages edited with Puck or a registered blocks field.
• A whole page walks you through choosing the Original page and a page for each version.
• A setting lists the flag points your developer registered.

Set it upCopy Anchor Link

The test page is a numbered list of sections, with a readiness bar and Start at the bottom:

• What you're testing: the test's name, why you are testing it, and where it is placed.
• Versions: the Original, the variants and an optional holdout, with their shares, content, settings or page addresses. Changing one share balances the others so the total stays at 100%.
• What counts as a win: the main goal, goals that must not get worse (guardrails), and goals to keep an eye on (supporting).
• Who takes part (optional): targeting rules and how many people take part.
• How long: the planned length (28 days by default). Enter roughly how many people see the content per day to get a suggested length; Apply copies it into the form.
• Advanced settings · for developers: analysis settings, layers and other options.

Start stays disabled until the test can start, and the readiness bar names the next step. The readiness checks also list where the test is placed, preview links and recent traffic. Common checks include: the page holding the block is published, every version has content, the main and guardrail click goals appear in every version, and every version page in a page test is published at its own address.

Save before using an action. Unsaved changes block actions so that every action uses the saved test. If someone else saved the test while you were editing, the save is refused with "Someone else changed this test. Reload to see their changes."

PreviewCopy Anchor Link

Each version has a preview link when your developer has wired admin.previewUrl. A preview shows that version without counting it. Edit on page appears when an editor link is configured.

ActionsCopy Anchor Link

Which actions appear depends on the test's status and your permissions.

There is no pause. Stopping is the only way to withdraw a variant.

DecideCopy Anchor Link

Decide opens with the recommended version from the latest results. Choosing the Original means everyone sees the Original. Choosing a variant means everyone sees it, except an existing holdout, which keeps seeing the Original so you can measure the shipped change.

When the results need caution, or you choose against the recommendation, you enter a note and type the chosen version's label to confirm.

Editing content during a testCopy Anchor Link

Changing a tested block or page while the test runs changes what people see mid-test. Puck warns before such edits, and each publish of tested content adds a content-change marker to the results chart so you can see when it happened. While a test runs on a page:

• Saves can be refused with page-busy (another save or start is in progress; retry) or interacting-tests (another test is using the same page; finish it first).
• Pages in a whole-page test cannot be deleted, renamed or unpublished.