One variable, a budget that can produce an answer, a fixed window, and kill criteria written before launch.
5 min read
Day four. Two ads, same audience, same budget, one variable between them. One has three purchases and the other has none, and the one with none is the one you wrote. Your finger is over the button that turns it off, and the window you agreed to on Sunday still has three days left in it.
A test against a vibe check
+A test
The question is written in one sentence, first.
One variable differs. Metric, window and kill criteria fixed first.
Nothing is edited inside the window.
×A vibe check
Several ads go live because they were finished.
Everything differs, including budget and audience.
The metric is whichever looks best in the report.
A CONFOUNDED TEST LOOKS EXACTLY LIKE A REAL ONE.
which is what makes it worse than no test
01BUDGET IS ARITHMETIC, NOT AMBITION
Roughly fifty optimisation events in seven days, before delivery settles.
Purchases are rare. A handful against a handful is chance dressed as a finding.
A budget that cannot generate fifty of the event you optimise for leaves delivery unstable.
Three options: raise it, consolidate rather than fragment, or optimise further up the funnel.
A test laid out day by day, with the decision points marked.The same spend split across more ad sets starves every one of them.
DECISION WINDOWS
One to three, three to five, five to seven, and what each settles.
What you may conclude, and when
Point
You can conclude
Still premature
Day one
Delivery started, spend pacing, ads approved, link works.
Everything else.
Day three
The upper funnel begins to separate.
Purchase verdicts.
Day seven
A full weekly cycle, and learning has had its window.
Nothing.
scroll the table →
every edit inside the window restarts the clock.
What restarts learning: large budget jumps, a changed optimisation event, edited targeting, swapped creative, a long pause.
Fragmenting across small ad sets starves all of them without resetting anything.
Small steps the delivery survives, beside the one jump that resets it.
Check the winner was not a single-day artefact.
Confirm it against a second audience before building on it.
Scale in steps, or duplicate higher and leave the original up.
Log the losers. The cheaper half of the education.
Kill, hold or scale. The branch was decided before you opened it.
on record
03THE TEST YOU CAN RUN TOMORROW
One divided by your contribution margin. Arithmetic, not a target.
01Write the question in one sentence, and name the variable that moves.
02Write success and kill criteria, with metric and window. Date it.
03Set the spend that window needs, from your break-even cost per purchase.
04Build variants so exactly one thing differs, named to explain themselves.
05Launch identically: same audience, event, placements, start time.
06Edit nothing inside the window.
07Read the upper funnel first, then downstream, then cost per purchase.
08Record the verdict and the reason in one line.
Impressions to purchase, and what a drop at each stage points at.
TAKEAWAYS
A test is a question with one variable that moves and a pre-agreed answer.
Budgets too small to produce enough events inside the window buy noise, not answers.
Day one shows faults, day three the upper funnel, day seven a verdict.
Kill criteria are only useful if they were written before you saw the numbers.
CHECK YOURSELF
Which of these restarts the learning period?
On day one of a test, what can you legitimately conclude?
DO THIS BEFORE THE NEXT MODULE
01Write one test question in a single sentence, naming the variable that moves.
02Write the kill criteria for it, with window and spend ceiling, and date them before you build anything.
03Run that test without editing it inside the window, then log the verdict in one line.