Pixel-free attribution keeps your storefront yours

Every vendor script on your storefront is a dependency you did not have the week before, and the switching friction it creates is usually a feature of the vendor's business model rather than an accident. That is worth saying out loud before the fourth one goes on.

This is not a claim that any particular vendor is acting badly. It is a structural observation: a tool that requires an install is a tool that is harder to leave, and every product team knows it.

The three costs of an install

The first is measurable today. The third is the one people underestimate, because the cost is not the removal itself but the history: uninstall the script and the historical collection stops making sense, so the comparison against your own past disappears.

The history problem

A vendor holding two years of collection about your customers holds something you cannot reproduce. You can export a summary, but you cannot re-run last year through a different method, because the raw collection was theirs and it stops when the contract does.

An export-based read has the opposite property. The source is your own Google Analytics account, so any window you can still export you can read again through any method you like, this year or in three years. Your history stays where your history was. We made the general argument in you do not own your attribution data.

What the storefront cost actually is

Page weight is the cost people quote and it is real but usually modest per script. The compounding version is what matters: four analytics scripts, two personalisation scripts and a chat widget, each individually defensible, together adding measurable delay to the checkout path where delay is most expensive.

Nobody makes the decision to slow checkout. It happens one reasonable install at a time.

The consent surface

Each vendor that collects is a sub-processor and belongs in your disclosure. That is administratively dull until someone asks a specific question, at which point being able to answer precisely matters. A measurement tool that adds no collection of its own does not appear in that list at all, which is the simplest possible answer to give.

Our own position, stated plainly: Causality Engine reads a CSV export you produce, adds no tag, no cookie and no identifier to your site, and is registered in the Netherlands with the data handling set out in the privacy policy rather than in a sales call. The EU-specific questions are covered in GDPR-compliant attribution for European ecommerce.

The test before the next install

Before adding any script, ask what question it answers that you cannot answer from data you already hold, and what happens to that answer the day you remove it. If the answer to the first is vague and the answer to the second is "we lose the history", the install is buying you a dependency more than an insight.

What you keep

No install means nothing to remove, no QA on checkout, and no history stranded behind a cancellation. The €99 one-time read is deliberately shaped that way: one export, one answer, a full refund within 30 days, no questions asked, and nothing left behind on your site either way.

Related answers

• Explaining pixel-free attribution to your developer
• What a pixel tells you that a GA4 export does not
• Attribution that adds nothing to your storefront
• Your Shopify order data is the lift evidence
• What you keep when you take the refund