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

No pixel means no install queue before peak

In the run-up to peak, an install-based tool needs a developer, a QA pass and weeks of collection. An export-based read needs a file. That gap decides what is possible.

Share
Quick Answer·3 min read

No pixel means no install queue before peak: In the run-up to peak, an install-based tool needs a developer, a QA pass and weeks of collection. An export-based read needs a file. That gap decides what is possible.

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

An install-based measurement tool has three prerequisites you do not have in the weeks before peak: a developer, a QA pass on checkout, and a collection period long enough to produce data. An export-based read has one: a file you can already produce.

That difference decides what is actually achievable this side of the window, and it is worth being concrete about rather than optimistic.

What each path needs, honestly

Install-based toolExport-based read
Developer timeYes, and in a freeze periodNone
Checkout QAYes, and nobody wants to touch checkout in NovemberNone
Collection period before first answerWeeksNone, the data exists
Realistic first answerAfter peakToday

The checkout QA row is the one that quietly kills these projects. Most brands operate a change freeze in the run-up, and a tag in the purchase path is precisely the change a freeze exists to prevent. The install does not get refused, it gets scheduled for December.

What is still worth doing

Get a baseline read on an ordinary trading month now. Peak numbers without a normal-month comparison are close to uninterpretable, because peak is strong for reasons that have nothing to do with your channel mix. The baseline is the thing that makes the post-window read mean something.

Freeze your channel grouping and lookback definition before the window opens. Changing either mid-season makes the before and after incomparable, which is the one mistake that cannot be repaired afterwards.

Then plan the post-window read, and check your analytics retention setting covers the period you will want. That setting expires quietly and takes the granular data with it, which is set out in the retention trap. The full calendar is in Black Friday measurement deadlines.

What is genuinely too late

A geo holdout is too late once the window is close, because holdouts need a pre-period and weeks of running. Starting one now measures the window rather than the channel. The last day to start a holdout puts a date on it.

Switching measurement method mid-window is also too late, for the simple reason that you will not be able to separate a change in the numbers from a change in the instrument.

The read that is still available

A €99 one-time read on a Google Analytics export needs no install, no developer and no collection period, because the data already exists in your account. It returns a per-channel estimate with its interval and coverage, and it is refundable if it does not move a budget decision. The interactive demo shows the output shape first, with no signup.

The point about urgency

None of this is urgent because a countdown says so. It is urgent because retention windows close, holdouts need lead time, and definitions changed mid-season cannot be compared afterwards. Those are calendar facts. Everything else about peak-season measurement can wait until January, and mostly should.

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.