How often should I re-read attribution after changing budget?

Wait until the change has run long enough to appear in a full lookback window, then read. Reading sooner mostly measures the pre-change period with a small tail of new data attached to it.

Why does my attribution estimate not move after a budget change?

Usually because the change was too small relative to the noise, the window was too short, or the channel sits below the spend level at which its effect can be separated from everything else. All three are honest outcomes and all three point at the design of the change rather than the tool.

Can I test two channels at once?

You can, but the next read will give you the combined effect rather than either one separately. If you need to attribute the result to a specific channel, move one at a time and hold the rest, even though that makes the cycle slower.

The attribution loop: change spend, then re-read

The point of automating the read is that you can afford to re-read. That only pays off if each cycle carries one deliberate change rather than five simultaneous ones.

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 Joris van Huët, Founder & CEOUpdated 2026-10-063 min read

Automating an attribution read is worth doing because it makes re-reading cheap, and re-reading is only informative if each cycle carries one deliberate change. Five changes at once produce a report you cannot interpret, no matter how often it arrives.

This is the part teams skip. They automate the report, keep changing spend the way they always did, and then find the automated report no more useful than the manual one. The report was never the constraint. The experimental hygiene was.

One change per cycle

Cycle shape	What the next read can tell you
One channel moved, everything else held	Whether that move helped, within the interval
Two channels moved in the same direction	Whether the pair helped, not which one
Budget and creative changed together	Almost nothing attributable to either
Everything moved	The report describes a different business

The discipline is unglamorous and it is the whole method. If you move Meta and cut Google in the same week, the next read gives you a joint effect. That is a real answer to a question nobody asked.

Structuring a cycle

Pick the channel with the most budget at stake, because that is where a wrong answer costs the most and where the estimate will be tightest. Change it by an amount large enough to show up above the noise.

Then hold everything else. Then re-read. Then write down what you expected before you look, because a prediction you record is evidence and a prediction you remember is a story.

The incremental ROAS guide covers how large a move needs to be for the estimate to separate, and how to measure incremental lift covers the same question from the test-design side.

When the loop says nothing

Sometimes the interval after a change still straddles break-even. That is a result, not a failure. It usually means one of three things: the change was too small, the window was too short, or the channel sits below the spend level at which any method can separate its effect from noise. The third case is the measurability floor, and the honest response is to name the channel as unmeasured rather than to report a number the data cannot support.

A vendor that always returns a confident number for every channel, regardless of spend, is telling you something about its willingness to say "we do not know" rather than something about your business.

What the API adds

Manually, a cycle costs a person an hour and therefore happens monthly.

If you want the loop without the automation, run it manually for a quarter.

The honest limit

A read on observed variation cannot tell you what would have happened under a change you never made. For that you need a holdout test, which costs the revenue forgone in the held-out group and takes weeks. The loop described here is the cheaper instrument, and knowing which questions it cannot answer is part of using it well.

Frequently asked questions

How often should I re-read attribution after changing budget?
Wait until the change has run long enough to appear in a full lookback window, then read. Reading sooner mostly measures the pre-change period with a small tail of new data attached to it.
Why does my attribution estimate not move after a budget change?
Usually because the change was too small relative to the noise, the window was too short, or the channel sits below the spend level at which its effect can be separated from everything else. All three are honest outcomes and all three point at the design of the change rather than the tool.
Can I test two channels at once?
You can, but the next read will give you the combined effect rather than either one separately. If you need to attribute the result to a specific channel, move one at a time and hold the rest, even though that makes the cycle slower.

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