What a privacy-first attribution standard looks like: Privacy-first is either a property of the method or a sticker on the marketing site. Four tests that tell you which one you are being sold.
Read the full article below for detailed insights and actionable strategies.
The attribution problem
One sale. Four channels. 400% credit claimed.
Reported revenue: €400 · Actual revenue: €100 · Gap: €300
Privacy-first is a property of what a method needs, not a claim on a marketing page. A tool that requires individual-level journeys and then anonymises them is minimising after the fact. A tool that never needed them is a different design.
The distinction matters because minimisation can be reversed by a product decision and a design cannot.
Four tests
| Test | Privacy-first answer | Minimised-afterwards answer |
|---|---|---|
| What is the smallest unit it needs? | Aggregate counts by channel and period | An individual journey |
| Does it work if consent drops to half? | Yes, with wider intervals | Coverage collapses |
| What does it add to your site? | Nothing | A tag, sometimes in checkout |
| Where does the data sit? | Named region, in the policy | "Global infrastructure" |
The second test is the practical one. Multi-touch attribution needs to observe a sequence of touches for a single person. If half your visitors refuse consent, half the sequences are unobservable, and the model runs on the consenting half while reporting as though it described everyone.
That is not a compliance failure. It is a validity failure that compliance happens to cause.
Why aggregates hold up
An aggregate method asks how orders moved when spend moved, across periods and regions. It never needs to know who anyone is. Consent refusal reduces the precision of the underlying counts a little; it does not remove the comparison. Ad blocking has the same limited effect for the same reason.
That robustness is the actual argument for aggregate methods, and it is a measurement argument rather than a legal one. The legal benefit is real and secondary. We laid out the European specifics in GDPR-compliant attribution for European ecommerce.
The honest limits of the aggregate approach
It cannot tell you about sequence, it cannot personalise, and it cannot answer questions about individuals. If your organisation needs those, an aggregate method is the wrong tool and no amount of privacy positioning changes that.
It also produces wider intervals than a well-observed individual-level dataset would in principle produce, which is a real statistical cost. In practice the individual-level dataset is not well observed any more, which is why the comparison has shifted.
What to ask a vendor
Ask what happens to their output when consent rates fall by twenty points. A vendor with an aggregate design will describe wider intervals. A vendor with an individual-level design will describe modelling that fills the gap, and the follow-up question is what that modelling assumes about the people who refused.
The general vendor-questioning framework is in the checklist for vetting an attribution vendor.
Where we stand
Causality Engine estimates per-channel causal effect from a Google Analytics CSV export that you produce. It adds no tag, cookie or identifier to your site, needs no individual journeys, and returns an estimate with its confidence interval, coverage and design label. The company is registered in the Netherlands and the handling is set out in the privacy policy.
First read is €99 once, refundable if it does not move a budget decision. The interactive demo runs the model on a sample store with no signup.
The principle
Design for the data you can defend collecting, then find out what that data can answer. It turns out to be most of the budget question, which is the useful surprise.
Related answers
Get attribution insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Key Terms in This Article
Analytics
Analytics is the systematic computational analysis of data. It reveals customer behavior and measures campaign performance.
Attribution
Attribution identifies user actions that contribute to a desired outcome and assigns value to each. It reveals which marketing touchpoints drive conversions.
Causality
Causality is the relationship where one event directly causes another, essential for identifying specific actions that drive desired outcomes in marketing.
Confidence Interval
Confidence Interval is a statistical range of values that likely contains the true value of a metric. In marketing analytics, it quantifies uncertainty around estimates, indicating the precision of an outcome or causal effect.
Cookie
Cookie is a small piece of data stored on a user's computer by a web browser, used for tracking behavior, personalizing content, and remembering preferences.
Google Analytics
Google Analytics is a web analytics service that tracks and reports website traffic.
Multi-Touch Attribution
Multi-Touch Attribution assigns credit to multiple marketing touchpoints across the customer journey. It provides a comprehensive view of channel impact on conversions.
Privacy Policy
Privacy Policy is a statement disclosing how a website collects, uses, discloses, and manages customer data.
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.
No spam. Unsubscribe anytime. We respect your data.