Skip to content

For GA4 usersFrustrated with GA4 attribution? Upload your GA4 export, see causal insights in 5–10 minutes for €99 pay-per-use.

ROAS & Incrementality

3 min read

Automate attribution before the Black Friday window

During peak, a report that takes a person two hours to assemble does not get assembled. What to automate beforehand, and what to accept you will read late.

Share
Quick Answer·3 min read

Automate attribution before the Black Friday window: During peak, a report that takes a person two hours to assemble does not get assembled. What to automate beforehand, and what to accept you will read late.

Read the full article below for detailed insights and actionable strategies.

The attribution problem

One sale. Four channels. 400% credit claimed.

100
1 sale
Meta
100%
claimed
Google
100%
claimed
TikTok
100%
claimed
Klaviyo
100%
claimed

Reported revenue: 400 · Actual revenue: 100 · Gap: €300

Everything you want running during peak has to be running before peak, because the week the reporting matters most is the week nobody has two hours to assemble it by hand. The useful question in the run-up is not what to build, it is what to cut.

Peak compresses decisions that normally take a fortnight into an afternoon. That changes what a report is for. Outside the window a report informs planning. Inside it, a report either changes today's spend or it is a historical document.

Before, during, after

PhaseWhat a report can still changeWhat to have ready
Four weeks beforeBudget split, creative, the test you runA read on a normal window, as the baseline
The window itselfToday's allocation, nothing structuralA scheduled read with a fixed definition
The two weeks afterNext year, and what you cut in JanuaryThe post-window read, before retention rolls

The third row has a deadline attached that surprises people. Google Analytics retention settings can be short enough that the granular data behind your peak read expires while you are still recovering from peak, which we covered in the two-month retention trap.

What is worth automating before the window

Freeze the channel grouping and the lookback definition now, not in November. Changing either mid-window makes the before and after incomparable, and the comparison is the entire point of measuring peak.

Get one baseline read on an ordinary trading month, so you have something to hold the peak read against. Without a baseline, a strong peak number tells you almost nothing, because peak is strong for reasons that have little to do with your channel mix.

Then schedule the read. On Causality Engine that means the Pro tier at €299 a month, which carries developer API keys, the MCP server, unlimited uploads and the direct integrations. The €99 one-time read is the right instrument for the baseline itself, and it comes with a full refund if it does not move a decision.

What is too late once the window opens

A geo holdout test is too late. Holdouts need a pre-period and weeks of running, and starting one in the window measures the window rather than the channel. We put a date on this in the last day to start a holdout before Black Friday.

Changing your attribution method mid-window is also too late, for the plainer reason that you will not be able to tell whether a movement in the numbers came from the market or from the switch.

The one thing worth doing late

If you have done nothing, do the post-window read. It is the highest-value single report of the year, because it is the only one taken on a period where budget moved enough to actually separate the channels. The post-mortem window sets out what to pull and when, and the measurement deadlines has the calendar.

The honest framing

None of this is urgent because a vendor says so. It is urgent because retention windows expire, holdouts need lead time, and definitions frozen mid-window produce numbers nobody can compare. Those are calendar facts, and they are the only reason peak deserves a deadline in your reporting plan.

Get attribution insights in your inbox

One email per week. No spam. Unsubscribe anytime.

Key Terms in This Article

Related Articles

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

Ready to see your real numbers?

Own the budget? Upload your GA4 export and see which channels drive incremental sales, with confidence intervals, in minutes. Have to defend it? Start with the live demo and take the read to your CFO.

Full refund if you don't see value.

Stay ahead of the attribution curve

Weekly insights on marketing attribution, incrementality testing, and data-driven growth. Written for the person who owns the budget and the person who has to defend it.

Which one are you? Optional.

No spam. Unsubscribe anytime. We respect your data.

Related reports

Real reports on this topic.

Anonymised reports from the Attribution Report Library tagged with roas & incrementality.

Browse all related reports

Find your wasted ad spend in 5–10 minutes.

Watch the model work on a sample store first, no signup. Then upload your last 40–90 days of GA4 sessions and get incremental ROAS with confidence intervals. No pixel, no SDK. €99 per read.

Prefer to talk it through? Book a 20-min call, or read how it works.

Last-click guesses.We run the math.

Causal attribution for ecommerce brands. Watch the model work on a sample store first, then upload your GA4 export and see which channels really drove revenue in 5–10 minutes. €99, pay-per-use. Pro at €299/mo when you want it continuous.

No signup for the demo. Book a 20-min call or compare plans.