Show version A again
Take a shipped winner back: every visitor sees the original again, and the result stays as it was decided.
You shipped version B to everyone through Needlr. Then something changes: a complaint, a new priority, a brand refresh. You need the original back today, without a developer.
Shipped a winner, and now you want the old page back? One button shows version A, the original, to every visitor again. No developer needed.
Think of a shop window
A shop tries a new window display, and sales go up. Later, the owner wants the old display back for a while. Putting it back doesn't change how much the new display sold. Those sales stay in the books.
Showing version A again works the same way. Your site changes back. The result of the test stays exactly as it was.
When you can do it
- A split test whose version B you shipped through Needlr (how).
- Any time its row in Shipped changes is still on the way to your site's code: Shipped via Needlr, Ready to move to code, Verifying, Verification failed, Needs a manual check or Verified: works without Needlr.
- Moved to code: your site shows B on its own now, so Needlr can't take it back. Ask your developer to undo it.
- Before vs after and Adoption checks: Needlr didn't change your site, so there's nothing to take back.
- A split test you stopped without shipping: everyone already sees version A.
You need to be an Owner or Editor, and your Tag Manager must still be connected.
How to do it
- 1Open the check's page. In the green box that says Shipped, press Show version A to everyone again. Or press the same button on the check's row in your project's Shipped changes tab.
- 2Read the box. It says every visitor gets the original version again, and that this publishes to your Tag Manager.
- 3Type the 6-digit code from your authenticator app (why). If you typed one in the last 20 minutes, just press Show version A.
- 4Needlr publishes to your Tag Manager. From the next page they open, visitors see version A.
What happens
- Every visitor sees version A, the original.
- The check's status becomes Stopped. Nobody is split or counted, so it doesn't use your plan.
- The verdict, the lift and its range stay exactly as they were decided. Later visitors don't change them.
- In Shipped changes, the row says Back to version A, with who did it and when.
- On your project's Timeline, the check no longer has the Shipped badge.
- If publishing fails, nothing changes: visitors keep getting version B, and Needlr says why.
Changed your mind again?
The win is still there. Open the check: the green box says Version B won. Ship it to everyone again. Press Ship version B and confirm with your code.
Common mistakes
- Using it as a pause. Visitors get version A right away, and keep getting it until you ship B again.
- Expecting a new result. Taking a change back doesn't test anything again. To compare A and B again, start a new split test.
- Removing the change from Tag Manager by hand. Use the button, so Needlr knows and its records stay right.
- Deleting a shipped check. Needlr won't delete a check while its change is live. Show version A first.
What the video says
You shipped version B to everyone through Needlr. Then something changes: a complaint, a new priority, a brand refresh. You need the original back today, without a developer.
On the check page, or in Shipped changes, press Show version A to everyone again. Confirm with Show version A and the code from your authenticator app.
Needlr publishes to your Tag Manager, and from the next page load every visitor gets version A. If the publish fails, nothing changes and B stays live.
The evidence doesn't move. The verdict, the lift and its range stay exactly as they were decided. Taking it back is a business call, not a new result.
The row in Shipped changes now reads Back to version A, with who did it and when. The check is stopped, so nobody is split and it doesn't use your plan.
Change your mind again? The win is still there: ship version B from the same page whenever you're ready. Reversible decisions are cheap, so make them fast.