Skip to content

One lever per window, and why it pays

A staging discipline for agent-driven change: one lever per measurement window, a logged boundary, and a read before the next batch is allowed to start.

Three platforms, three answers, one budget to defend. Your GA4 export already holds the answer, and the first finding is free and never leaves your browser. Get your first finding free

By , Founder & CEOUpdated 2 min read

Run the numbers for your store: the free holdout test planner.

Sequencing costs you a few weeks and buys you the ability to attribute anything at all. Here is the discipline.

The rule

One lever per window. Listings, or ad copy, or creative, or pricing. Not two, and never all four.

A window is long enough for the effect to show and for the noise to average out, which for most DTC catalogues means weeks rather than days.

Why this is not obvious

It feels wasteful. The agent can do all four in an afternoon, and sequencing them looks like deliberately going slower than you have to.

The trade is real, and it is worth making: four changes in one window gives you one number you cannot decompose. Four changes across four windows gives you four numbers you can act on individually. The second is worth more even though it arrives later.

The changelog is half the method

LogWhy it matters
Timestamp of the batchDefines the before and after boundary
What changed, preciselySo the next read knows what it is reading
What deliberately did not changeThe holdout, recorded before results exist
Anything external in the windowPromotions, outages, seasonality, press

An agent can write all four rows itself, at the moment it acts, which is the only moment the information is complete. Retrofitting a changelog a month later produces something that looks like a record and is not one.

Reading between windows

Before the next batch, read the last one. An estimate with a confidence interval that spans break-even means the window did not resolve, and the correct response is usually a longer window rather than a bigger change.

Stacking a second change onto an unresolved first is how a catalogue ends up in a state nobody can explain.

The read

Causality Engine reads one file, the Attribution paths export from GA4, and shows what each channel caused next to what last-click gave it.

Frequently asked questions

  • What does one lever per window mean?
    Change listings, or ad copy, or creative, or pricing in a given measurement window, but not several at once. Four changes in one window produce one number you cannot decompose; four windows produce four you can act on.
  • What should an agent log when it makes changes?
    The batch timestamp, precisely what changed, what was deliberately left unchanged, and anything external in the window such as promotions or outages. It should write these at the moment it acts, which is the only time the record is complete.
  • What if a window does not resolve?
    Extend the window rather than making a bigger change. Stacking a second change onto an unresolved first is how a catalogue reaches a state nobody can explain.

Go deeper: Causal attribution, explained.

Sixty-second versions of these ideas: Causality Engine on YouTube Shorts.

Have an audience of ecommerce operators? Earn 20% recurring commission by recommending the €99 read.

Keep reading

Terms in this article

Browse the full glossary

Your platforms guess.
We run the math.

Upload a GA4 export and see what each channel caused, next to last-click, in 1–2 minutes. The read is yours to keep.

The free finding runs in your browser. Your file never leaves it. The full read is €99, refundable within 30 days, no questions asked. Prices exclude VAT.