# End a test and deploy the winner until your site is updated

You'll end an A/B test, keep the version you choose, and keep showing an Original page winner until your website has the changes, then undeploy it.

Available on the Scale and Pro plans.

When a test has an answer, or you've decided you've waited long enough, end it and keep the version you want. On an Original page test, RightMessage can keep showing the winner to everyone until your developer puts the change on your website, then step aside. Ending, Deploy, and Undeploy don't need Pro.

Tests never end on their own. The card tells you when a test is **Ready to end**, and Needs attention shows "A/B test ready to end".

## 1. End the test

1. Open the campaign's **Testing** tab and choose **End test** on the test's card. You can also choose **End test** from the test's row in the campaign editor.
2. Pick the version to keep. Each version shows its verdict, such as "Beat Control at the week 7 check" or "Not proven better than Control yet". A proven winner is preselected and tagged **Winner**.
3. On an audience test, that's it: the audience sees the version you chose from now on.
4. Confirm with **End test and show {version}** or **End test and keep Control**.

![End A/B test dialog asking which version the Customer audience should see, with Control selected and End test and keep Control](https://rightmessage.com/help/screens/testing-end-dialog.light.webp)

If you pick a version that hasn't been proven, the dialog warns that its difference so far could be chance. You can still keep it.

Ending is a draft change. The card reads **Ends on Publish**, and visitors stay in the test until you [publish](https://rightmessage.com/help/publishing-your-changes). Changed your mind? **Undo end** puts the test back.

## 2. Choose how visitors get an Original page winner

When you keep a variant of the Original page, the dialog asks **How should visitors get it?**

| If…                                           | Choose                                       | What happens after you publish                                                                                                  |
| --------------------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Your website doesn't show the winner yet      | **Show it now, until my website is updated** | RightMessage shows the winner to everyone who sees the Original page. Matching audiences still win on the elements they change. |
| You've already put the winner on your website | **My website already shows {version}**       | RightMessage stops changing the page. "After you publish, visitors see your website as it is."                                  |

A proven winner preselects the first option. An unproven pick preselects nothing, so you choose deliberately.

## 3. Hand the changes to your developer

The dialog and the deployed card list **Changes to make on your website**: each page, element, and the new text or visibility. Choose **Copy as checklist** to copy a brief for your developer or agency.

After you publish, the card reads **Deployed · {n} days**: "Everyone who sees the Original page now sees {version}." RightMessage keeps showing it until your website has these changes.

![Original page test deployed for 69 days, with Undeploy, the changes to make on your website, Copy as checklist and the website check](https://rightmessage.com/help/screens/testing-deployed-card.light.webp)

## 4. Let RightMessage check your website

RightMessage checks recent page views to see whether your website shows the changes. The deployed card shows the result:

- "Not on your website yet. {matched} of {n} recent page views show these changes (last 14 days)."
- "Your website now shows these changes on {n} recent page views."

You don't need to run the check yourself. It updates as visitors load the page.

## 5. Undeploy

Once your website shows the changes, Needs attention says "Ready to undeploy: your website shows {version}".

1. Choose **Undeploy** on the deployed card, or from the **Original page** menu in the editor.
2. Read the confirmation. If the website check hasn't seen the changes on every recent page view, it warns you that visitors will see the old version after you publish.
3. Confirm with **Undeploy**, then publish.

After publishing, visitors see your website as it is, which now includes the winner. You can then start a new Original page test. While a winner is deployed, **A/B test the original page** is unavailable: "Undeploy first so a new test compares against your updated website."

## The two deploy alerts

| Alert                                                                         | What to do                                                                                                                     |
| ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| "Ready to undeploy: your website shows {version}"                             | Undeploy and publish.                                                                                                          |
| "{version} has been deployed for {n} days. Your website doesn't show it yet." | Shown after 30 or more days. Send the checklist to your developer again, or undeploy if you've decided not to make the change. |

See the [Needs attention reference](https://rightmessage.com/help/needs-attention-reference) for the other alerts.

## After the test

The finished test's results stay on the card, frozen, under **Test results · ran {n} weeks**. To test again, add a new test in the editor. See [run an A/B test on a page or audience](https://rightmessage.com/help/run-an-ab-test-on-a-page-or-audience).