Explaining pixel-free attribution to your developer: The developer review is where measurement tools die. Four questions engineering always asks, the honest answers, and the one objection worth taking seriously.
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
Engineering does not object to measurement, it objects to unbounded collection on a critical path. A tool that collects nothing on your site clears that objection before the conversation starts, which changes the review from a negotiation into a five-minute check.
Here is what gets asked, in the order it gets asked.
The four questions
| Question | The answer for an export-based read |
|---|---|
| What does it put on the site? | Nothing. No tag, no script, no identifier |
| What does it collect? | Nothing directly. It reads a file you export |
| What does it touch in checkout? | Nothing |
| What happens if it breaks? | A report is late. No visitor-facing impact |
The fourth row is the one engineering cares most about and marketing never anticipates. A script in the critical path is a thing that can fail in front of customers. A batch process that reads a file cannot.
The objection that deserves a real answer
The serious version of the pushback is not about collection, it is about validity: "if it never sees a session, how does it know anything?"
That is a fair question and the honest answer is that it does not know anything about a session. It estimates an aggregate effect from variation that already exists in your data across time and channel, and it reports how sure it is. The estimate carries a confidence interval, a coverage share of your orders, and a label saying the design is observational rather than experimental.
An engineer will usually accept that framing quickly, because it is the framing they already use for anything inferred rather than measured. What they react badly to is a vendor claiming certainty the method cannot support, which is a reasonable reaction. The method is written out in plain language on how it works, and the wider argument for publishing it is in attribution vendors that explain their methodology openly.
What to bring to the review
Bring three things. The description of the input, which is a Google Analytics CSV export you produce yourself. The description of the output, which is a per-channel estimate with its interval, coverage and design label. And the privacy policy, because the data handling question will come up and pointing at a document is faster than relaying an answer.
If your engineer wants to see it before agreeing to anything, the interactive demo runs the real model on a sample store without a signup or an account.
What not to claim
Do not tell your engineer it is "cookieless" if what you mean is that it adds no cookie of its own. Analytics still collects the way it collects; we simply do not extend it. Overstating that is the fastest way to lose credibility in a technical review, and the accurate version is a strong enough position without the embellishment.
The reason this matters organisationally
Measurement tools that need engineering time get scheduled, and scheduled means quarterly at best. Removing the install removes the dependency on someone else's roadmap, which is the difference between a marketing team that can read its channels monthly and one that reads them when a ticket clears. That is usually the real unlock, and it is covered from the buying side in attribution without a pixel or engineering.
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.
Google Analytics
Google Analytics is a web analytics service that tracks and reports website traffic.
Privacy Policy
Privacy Policy is a statement disclosing how a website collects, uses, discloses, and manages customer data.
Session
A Session is a group of user interactions with your website within a given timeframe. It can include multiple page views, events, and transactions.
Shopify
Shopify is an ecommerce platform for creating online stores and selling products. Attribution modeling shows which marketing channels drive traffic and conversions within Shopify.
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.