Rename, start, stop or delete a check
What each button on an impact check does, and which ones can't be undone.
An impact check is a record your team revisits. Give it a clear name and a short description of what changed and why, so the result still makes sense in six months.
On an impact check's page you can rename it, describe it, start it, stop it and delete it. Some of these can't be undone, so it helps to know which before you click.
Think of a notebook
Renaming an impact check is like fixing a title written in pencil: easy to change again. Stopping is like closing the notebook for good. Deleting is tearing the pages out.
Only Owners and Editors see these buttons. Viewers can look but not change anything (roles). In the demo project, nothing can be changed.
Rename an impact check
- 1Point at the impact check's name at the top of its page. A pencil appears.
- 2Click the pencil and type the new name.
- 3Press Save, or Cancel to keep the old one.
A good name says what you changed: “Shorter signup form”, not “Test 3”. Renaming changes nothing on your site.
Add a description
- 1Under the two cards, click + Add a description: what changed and why.
- 2Write what you changed, and why you think it will help.
- 3Press Save. Later, open About and press Edit to change it.
In six months, nobody will remember why you ran this impact check. The description remembers for you.
Start a draft
A new impact check stays a Draft until you start it. A draft measures nothing and changes nothing on your site.
- 1Optional, for a visual split test: press Preview A and Preview B to see both versions on your site. Only you see them, and nothing is counted.
- 2Press Start.
- 3Read the box: it says what share of visitors will see the new version. Press Start now.
- 4If Needlr asks, type the code from your authenticator app (why). Needlr publishes what isn't live yet to your Tag Manager, then starts counting.
If the publish doesn't go through, the impact check stays a draft and Needlr says why. If the project already has 100 impact checks measuring, Needlr says so too (plans).
Stop an impact check
Stop ends a running impact check. Before it does, a box tells you exactly what will happen.
- Everyone sees the current version (A) again. Needlr publishes this to your Tag Manager.
- The results so far are kept.
- A stopped impact check can't be restarted. If it stopped before a verdict, Run it again makes a fresh draft with the same change and KPI.
- Stopping changes your live site, so it needs your authenticator code. (A before vs after impact check that counts with Google Analytics doesn't.)
- Stopping an Adoption impact check ends it without a verdict. Nothing changes on your site.
Delete an impact check
Delete shows up once an impact check isn't running. It removes the impact check, its visitor assignments and its results, forever. The audit log keeps a record that it existed.
- A running impact check: press Stop first.
- A shipped impact check: press Show version A to everyone again first (more).
- A draft: nothing is lost. It never started.
- Your KPIs stay. They belong to the project, not to the impact check.
Common mistakes
- Stopping because day 2 looks great (or awful). Early numbers swing (why). Let it finish.
- Deleting old impact checks to tidy up. They are your proof of what worked. Keep them.
- Vague names. “Test 3” means nothing next quarter.
What the video says
An impact check is a record your team revisits. Give it a clear name and a short description of what changed and why, so the result still makes sense in six months.
A draft measures nothing yet. Press Start and Needlr first publishes the measurement to your Tag Manager, then begins splitting traffic. Live changes need your authenticator code.
Stop ends the impact check for good. Everyone goes back to the current version and results so far are kept. Once stopped, it can't be restarted, only run again as a fresh copy.
Stopping before the verdict throws away the answer your traffic was buying. If the needle leans one way after three days, that's noise. Let the impact check finish.
Delete removes an impact check that is not running: its visitor assignments and results are gone permanently. Only the audit log keeps a record. Stop a running impact check first.
Rule of thumb: rename and describe freely, stop deliberately, delete rarely. Your history of impact checks is the evidence behind every product decision you defend.