Skip to content

Attribution that adds nothing to your storefront

There are two ways to measure a channel: collect more data about shoppers, or work harder on the data you already have. Only one of them adds code to your checkout.

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 , Founder & CEOUpdated 4 min read

There are two ways to measure which marketing causes revenue: collect more data about individual shoppers, or work harder on the data you already collect. Only the first one puts a new script on your storefront.

The industry defaulted to the first for a decade because it was easier to sell. More collection produces more rows, more rows look like more rigour, and the install becomes a switching cost that keeps the customer. That the extra rows rarely improve the answer is not something the install is designed to surface.

What each approach actually needs from you

Script-based measurementExport-based measurement
On your siteA tag on every page, often in checkoutNothing
Who installs itA developer, or you and a tag managerNobody
Time before first answerThe install queue, then a collection periodThe length of the export
What it observesIndividual sessions it can seeAggregate variation already recorded
What it adds to consentAnother vendor in your bannerNone of its own

The last row is the one that has changed most since the EU tightened enforcement. Every additional script is another entry in your consent disclosure, another sub-processor, and another thing to explain when someone asks what happens to their data.

The honest trade

Export-based measurement gives something up. It cannot see an individual journey, it cannot fire in real time, and it cannot follow a person across domains. If your question genuinely requires session-level detail, an export will not answer it.

What it is good at is the question most brands actually have, which is not "what did this person do" but "did this channel cause revenue". That is an aggregate question, and aggregate questions are answerable from aggregate data. We wrote the longer version in attribution without a pixel or engineering.

Why "cookieless" is a muddier word than it looks

A tool can be cookieless and still require an install, because server-side collection is still collection. A tool can also require no install of its own while reading data from a system that does use cookies, which is our position and worth stating plainly rather than marketing around.

Causality Engine reads a Google Analytics CSV export. GA4 collects with cookies where consent allows. We add nothing to that: no tag, no script, no additional identifier, and no new entry in your banner. The precise claim is that we do not extend your collection, not that your analytics stopped using cookies.

The wider landscape of what changes when third-party identifiers go away is covered in cookieless tracking for ecommerce.

What this makes possible

The practical consequence is that measurement stops being a project. There is no install ticket, no QA on checkout, and no waiting for a collection period before the first read. You export a window that already exists and you get an answer in minutes.

The €99 one-time read exists precisely because that shape is possible: a single export, what each channel caused next to last-click with a data-health score for how far to trust it, and a full refund within 30 days, no questions asked.

The principle underneath

Collecting less is not a compromise you accept to be compliant. A method that needs to watch individuals to work is a method with a fragile future, because the direction of both regulation and browser policy has been consistent for years and shows no sign of reversing.

Frequently asked questions

  • Can you measure marketing attribution without a tracking pixel?
    Yes, for aggregate questions. A causal read on an analytics export can estimate whether a channel caused revenue without observing individual sessions. What it cannot do is reconstruct a specific person's journey, which is a different question that does require session-level collection.
  • Is Causality Engine cookieless?
    Causality Engine adds no cookie, tag or identifier of its own. It reads a CSV export from Google Analytics, which collects with cookies where consent allows. The accurate claim is that we do not extend your collection, not that your existing analytics stops using cookies.
  • What do I give up by not using a pixel?
    Session-level detail, real-time firing, and cross-domain journey stitching. If your question needs any of those, an export-based read will not answer it. For per-channel budget decisions, which are aggregate by nature, the export is sufficient.

Go deeper: Incrementality testing, 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

Your platforms guess.
We run the math.

Upload a GA4 export and see what each channel caused, next to last-click, in 1–2 minutes. The read is yours to keep.

The free finding runs in your browser. Your file never leaves it. The full read is €99, refundable within 30 days, no questions asked. Prices exclude VAT.