Shipped changes
Every winner shown to everyone through Needlr, and how to move each one into your site's code.
Every winner you ship lands on the Shipped changes page. It's the single list of what still runs through Needlr, so nothing on your live site is a mystery.
Shipped changes lists every winner you showed to everyone through Needlr. It also helps you move each one into your site's code, so it doesn't depend on Needlr any more.
Find it on your project page: the Shipped changes tab.
Think of sticky notes
Imagine you keep new recipes on sticky notes on the fridge until you copy them into the recipe book. This page is the fridge: every note that is still only a note.
Before you throw a note away, you check the recipe book really has it. Needlr does that check for you.
What each row shows
- The name of the impact check. Click it to open its page.
- A status chip (below), and who shipped it and when.
- The change itself, and the KPI with the lift it won, like +18%.
The chip next to the title, like 2 active, counts the changes Needlr still applies.
The statuses
Every visitor gets version B, applied by Needlr.
You pressed Ready for verification. Needlr waits for visitors on the changed page.
Needlr is checking visitors' pages. The row says how many of the 20 it needs are done.
Your site shows version B on its own. You can now stop applying it through Needlr.
Needlr can't check this kind of change by itself. Check it yourself (see below).
Most visits still show the old version. Visitors keep getting B through Needlr while your developer fixes it.
Needlr no longer applies it. For the first 7 days it keeps checking the live site.
After Needlr stopped, most visitors saw the old version. The site's code doesn't have the change.
Someone showed the old version to everyone again.
Your plan ended, and 30 days later Needlr took the change back.
Move a change into your site's code
- 1Press Export for your developer. You get one page (a file that opens in any browser) with every change Needlr still applies: the page, the element, the old and new state, and code to paste.
- 2Your developer adds the change to the site and puts it live.
- 3Back on this page, press Ready for verification, and confirm with your authenticator code (why). Needlr publishes to your Tag Manager.
- 4Wait. Needlr reads visitors' pages as your site sends them, before it applies anything. After 20 checked visits, if more than 9 in 10 already show version B, the row says Verified: works without Needlr.
- 5Press Stop applying through Needlr and confirm with your code. Needlr stops applying it, and keeps checking the live site for 7 more days.
Stop applying through Needlr only works once the change is verified. That way, nothing disappears from your site by mistake.
If something goes wrong
- Verification failed: the row shows what Needlr expected and what it found. Visitors still get version B. Ask your developer to fix the site, then press Verify again.
- Problem after removal: press Apply through Needlr again. Every visitor gets version B again while your developer fixes the site.
- Owners and Editors get an email when either of these happens.
Show the old version again
Press Show version A to everyone again on a row (or on the impact check's page), then Show version A and your code. Every visitor gets the old version. The row says Back to version A. You can ship it again later from the impact check's page (how).
Common mistakes
- Leaving changes here forever. They depend on Needlr and your Tag Manager. Move them into code.
- Pressing Ready for verification before the developer's change is live. Verification fails. Wait until it's live.
- Removing a change from Tag Manager by hand. Use the buttons here, so Needlr knows and keeps checking.
What the video says
Every winner you ship lands on the Shipped changes page. It's the single list of what still runs through Needlr, so nothing on your live site is a mystery.
Each row shows its status. Shipped via Needlr means Needlr applies it. Moved to code means your site does it alone. The lift it won stays beside it.
Press Export for your developer to download one document listing every active change: the page, the element, the old and new state, and code to paste.
Once the developer deploys it, press Ready for verification. Needlr reads the live page before applying anything, and checks that visitors already see version B on their own.
Only after it's verified can you press Stop applying through Needlr. Needlr steps back, then watches the live site for seven more days, in case something slips.
Need the old page? Show version A to everyone again reverses any shipped change. Keep this list short: every row still running through Needlr is a dependency to retire.