Skip to content

The fastest lift read before a budget call

An hour before a budget call with no measurement in place. What you can honestly produce, how to caveat it, and the three claims that will collapse under questioning.

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.

With an hour before a budget call and no measurement in place, you can produce two things honestly: a claim ratio and an observational per-channel read. You cannot produce a lift test, and claiming otherwise is the fastest way to lose the room.

What fits in an hour

OutputTimeWhat it supports
Observational read10 minutes plus the export"Here is a per-channel estimate and how sure it is"
A named list of unmeasured channelsFalls out of the read"These three we cannot resolve at current spend"

Total your store revenue for the window, sum what each ad platform claims for the same window, divide. A ratio above one quantifies the overlap in your reporting, and the method is in the claim ratio walkthrough.

The observational read

Before you walk in, look at the intervals rather than the ranking, and be ready to name the widest one yourself.

The three claims that will collapse

Do not say "we tested this". You did not; you read observed variation. Do not say "this channel is definitively unprofitable" when the interval spans break-even.

What to actually ask for in the meeting

Not a verdict. Ask for two things: permission to hold the largest channel steady for a fortnight so a proper read is possible, and agreement on the threshold that would justify a cut. That converts a defensive meeting into a plan, and it is a much easier ask than a budget change.

If the meeting is genuinely about cutting something today, the defensible version of that argument is set out in the attribution report that tells you which channels to cut.

The part worth remembering

An hour of honest work beats a week of confident work, because the honest version survives the second meeting.

Frequently asked questions

  • What can I produce in an hour with no attribution set up?
    A claim ratio, which needs only your store revenue and each platform's claimed revenue for the same window, and an observational per-channel read from an analytics export. Both are honest. A lift test is not achievable in an hour under any method.
  • How do I present a fast attribution read credibly?
    Lead with its limits. Name the design as observational, show the confidence intervals rather than a ranking, and volunteer the widest interval yourself. Disclosing the weakest part of your evidence is what makes the rest of it believable.
  • What should I ask for in the budget meeting?
    Permission to hold your largest channel steady for a fortnight so a proper read is possible, and agreement on the threshold that would justify a cut. Both are easier asks than a budget change and both make the next meeting shorter.

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.