Making the winner permanent
What Make it the content does for block, page and flag tests, how failures are reported, and how to finish archiving.
After you decide, the winner is shown to everyone, but it still lives inside the test. Make it the content turns it into ordinary content and archives the test, so the test no longer has to be resolved on every request.
What it does per kind
| Kind | What happens |
|---|---|
| Block | Every Experiment block for this test is replaced with the winning version's content, in the published page and in drafts. |
| Page | The winner keeps serving at the Original's address, with its canonical URL. Losing addresses keep rewriting to the winner while the archived test exists. |
| Flag | The winning settings are saved as the flag point's new defaults. If the flag point has a makeContent callback, it runs so your app can update its own content. |
| Code | Not available. A developer hard-codes the winner; you then confirm that with typed confirmation, which archives the test. |
Content writes use the manager's own access (overrideAccess: false), so a manager who cannot update a page cannot change it this way. The page is published from its live published version, so unpublished draft edits never leak into the published page.
When a page cannot be updated
Each page that could not be updated is listed with a reason and Retry:
| Reason | Meaning |
|---|---|
localized | Localized collections are not supported yet. Update the page by hand. |
locked | Someone is editing the page. Retry when they are done. |
forbidden | You can't read or update the page. Ask someone with access. |
not-found | The page was deleted or moved to trash. |
validation | The updated page did not pass validation. |
update-failed | Any other failure. The details are in the server log. |
You can Dismiss an entry (and Undo it) when you have updated that page by hand or it no longer exists. Finish archiving appears once every page is updated or dismissed. When every page updates on the first try, the test archives itself.
Localized collections are flagged before you decide, so you know in advance that those pages need a hand edit.
Releasing pages after a page test
An archived page test keeps sending its losing addresses to the winner and protects those pages from deletion, renaming and unpublishing. On the results page, Release pages removes that routing and protection so every address shows its own page again. The result stays recorded, along with who released the pages and when.
Keep the winner published at its address while the archived test exists: archived routing still points to it.
Discarding a winner
Discard winner sends everyone back to the Original and archives the test. The decision note is kept. It needs typed confirmation.