Export shipped changes

Download one page with every winner Needlr still applies, so a developer can move them into your site's code.

Export for your developer downloads one page with every winning change Needlr still shows on your site. Your developer uses it to build each change into the site's own code. Then Needlr can stop applying them.

Think of training wheels

Training wheels let a child ride today. But one day they come off. Before that, a parent runs alongside to check the child really rides alone.

Shipping a winner through Needlr is the training wheels: it works today, but it depends on Needlr. The export is the lesson for your developer. Ready for verification is the parent running alongside.

When to use it

How to export

1. 1Open your project and go to the Shipped changes tab.
2. 2Press Export for your developer. The button only shows while at least one change runs through Needlr.
3. 3A file like needlr-changes-acme.html downloads. It opens in any browser. Send it to your developer.

Exporting changes nothing on your site, so it needs no authenticator code. Anyone on the team can download it. The Plan page has the same link while changes run through Needlr.

What's in the file

At the top: your project, your website and the day you exported it. Then one section for each change Needlr still applies, oldest first:

• The name of the impact check, its KPI, what it won by (like won by +18%) and the day it was shipped.
• Page rule: which pages the change is on.
• Element: what was changed, like “Every button or link reading Book a call”.
• Action, Original state and New state: what the change does, before and after.
• Code to paste: JavaScript, CSS or both, with a line saying where it goes. Or a short note when no code is needed.

Different changes, different help

• New text, a new color, a new link or picture: code to paste, or the developer changes the page template.
• A hidden element: CSS that hides it, or simply delete it from the page.
• An element that was hidden from version A: it's already on your site. Nothing to add, just keep it.
• An added button, text or bar: code that adds it, and CSS for its look. Better: add it to the page template.
• A moved element: code that moves it. Better: move it in the page template.
• A redirect: set it up in your server or hosting settings. No page code is needed.
• A developer split test: keep the code of version B, delete version A's, and remove the impact.feature check around them.

After the developer is done

1. 1Wait until the developer's version is live on your site.
2. 2On Shipped changes, press Ready for verification on that row, and confirm with your authenticator code.
3. 3Needlr reads visitors' pages as your site sends them, before it applies anything. After 20 checked visits, if more than 9 in 10 already show the new version, the row says Verified: works without Needlr.
4. 4Press Stop applying through Needlr and confirm. It only works once the change is verified.
5. 5The row says Moved to code. Needlr keeps checking the live site for 7 more days, and emails owners and editors if visitors see the old version.

Some changes Needlr can't check by itself, like added elements or redirects. Their row says Needs a manual check: look at the live page yourself, then press I checked it works without Needlr (more).

Common mistakes

• Pressing Ready for verification too early. If the developer's version isn't live yet, verification fails. Wait until it's live.
• Removing Needlr's tags from Tag Manager by hand. Use the buttons on Shipped changes, so Needlr keeps checking.
• Exporting once and forgetting. The file lists what runs through Needlr on the day you export. Export again after you ship another winner.