Ship the winner to everyone
When version B wins a split test, show it to every visitor right away, no developer needed.
Your split test called it: version B improved the KPI. Now every visitor still on version A is a conversion you're leaving on the table. Ship the winner.
When a split test says the new version (B) won, you can show it to every visitor right away. No developer needed.
Think of a bakery
You tested two cookie recipes, and the new one sold better. Now you bake only the new one. At first the recipe is on a sticky note on the fridge: quick, but easy to lose. Later you copy it into the recipe book.
Shipping through Needlr is the sticky note: every visitor gets B today. Moving it into your site's code is the recipe book (how).
When you can ship
- A split test with the verdict Improved.
- It can still be running, or already stopped.
- Got worse or No clear effect: there's no winner to ship.
- Before vs after and Adoption impact checks: that change is already live for everyone.
You need to be an Owner or Editor, and your Tag Manager must be connected (how).
How to ship it
- 1Open the impact check. At the top, a green box says Version B won. Ship it to everyone.
- 2Press Ship version B.
- 3Read the box, then type the 6-digit code from your authenticator app (why). It goes through by itself once all 6 digits are in. If you typed a code in the last 20 minutes, just press Ship it.
- 4Needlr publishes to your Tag Manager. From now on, every visitor gets version B.
What happens next
- The impact check's status becomes Shipped. Nobody is split or counted any more, so it doesn't use your plan.
- The result stays exactly as it was decided. Later visitors don't change it.
- The change appears in your project's Shipped changes tab.
- If publishing fails, nothing changes: the impact check stays as it was, and Needlr says why.
Changed your mind?
On the check page, press Show version A to everyone again, then Show version A. Every visitor gets the old version again. This also publishes to your Tag Manager and needs your code. You can ship it again later from the same page.
Prefer your developer to build it now?
Under the needle, the green box has Copy a note for your developer. It copies a short message: what changed, how much it won by, and a request to make it permanent. Paste it into your team chat or ticket.
Common mistakes
- Pressing Stop instead. Stop sends everyone back to the old version (A). To keep the winner, ship it.
- Forgetting it runs through Needlr. Plan the move into code, or it depends on Needlr forever.
- Wanting to ship a lean. Only a finished Improved can be shipped. Leaning up isn't a win yet (why).
What the video says
Your split test called it: version B improved the KPI. Now every visitor still on version A is a conversion you're leaving on the table. Ship the winner.
No developer needed. On the check page, press Ship version B. Needlr publishes it through your Tag Manager, and from that moment every visitor gets the winning version.
Because this changes your live site, Needlr asks for a six digit code from your authenticator app. One code covers twenty minutes, so a stolen password alone can't ship anything.
Shipping ends the measurement. Nobody is counted any more, so it doesn't use your plan's visitors or impact check slots, and the result stays frozen as your evidence.
Changed your mind? Show version A to everyone again reverses it, confirmed with your code. You can ship it again later from the impact check's page.
Shipping through Needlr is instant, but it depends on your Tag Manager. So ship winners the day they win, then move them into your site's code when a developer has time.