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.

Attribution

4 min read

What an attribution API returns that dashboards hide

Dashboards are edited. The API response is not. Four fields that tend to exist in the payload and never make it onto the screen, and what each one tells you.

Share
Quick Answer·4 min read

What an attribution API returns that dashboards hide: Dashboards are edited. The API response is not. Four fields that tend to exist in the payload and never make it onto the screen, and what each one tells you.

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

A dashboard is an edited view, and the edit usually removes the fields that would have made you cautious. Reading the raw response is the cheapest way to find out what a tool knows and does not show.

This is not an accusation of bad faith. Interfaces are designed to be legible, and legibility means dropping columns. The problem is that the columns dropped first are almost always the ones that qualify the headline.

Four fields worth looking for

FieldTypical dashboard treatmentWhat it tells you
Interval widthHidden, or shown as a faint bandWhether the estimate can support a decision
CoverageAbsentWhat share of real orders the read explains
Design labelAbsentHow this evidence ranks against a test
Declined channelsSilently dropped or imputedWhich channels the method could not measure

The fourth row is the interesting one. When a channel has too little spend for its effect to be separated from noise, a well-built method declines to score it. A dashboard that shows a tidy ranked list of every channel has either measured them all or quietly filled the gaps. Those are very different products and the interface looks identical.

How to check without building anything

You do not need an integration to find this out. Ask the vendor for a sample response payload for one account and one window. A vendor confident in its method will send one. Compare the fields in the payload against the fields on the screen, and ask about anything present in one and absent from the other.

We think this is a reasonable thing to ask of anyone, including us, and set out the wider case in why attribution vendors should explain methodology openly. The buying-side version is the checklist for vetting an attribution vendor.

The interval is the field that changes behaviour

Of the four, interval width is the one that most often changes what a team does. A channel with an estimate of 1.8 and an interval from 1.6 to 2.0 supports a decision. The same 1.8 with an interval from 0.4 to 3.2 does not, and the dashboard renders both as 1.8.

The practical consequence is that teams scale channels on estimates that were never resolved, then conclude attribution does not work when the scaling does not pay. It worked fine. The width was hidden. Attribution tools that report confidence intervals covers who publishes them.

Coverage is the field that changes the framing

Coverage answers a question nobody thinks to ask: of the orders you actually took in this window, what share does this read explain? If it is high, the channel estimates describe your business. If it is low, they describe a slice of it, and the rest is sitting in unassigned traffic doing something the model cannot see. That is a normal condition and it is worth knowing before you reallocate.

What we return

Causality Engine returns the estimate, the interval, the coverage and the design label per channel, and names the channels below the measurable floor rather than scoring them. The output is visible without a signup on the interactive demo, and the method is written out on how it works. Developer API keys and the MCP server sit on Pro at €299 a month; the €99 one-time read produces the same fields from a manual upload.

The question to carry into any demo

Ask what the model does with a channel it cannot measure. The answer separates tools that are honest about their floor from tools that have no floor at all, and it takes about ten seconds to ask.

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 attribution.

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.