What a pixel tells you that a GA4 export does not
We sell an export-based read, so here is the uncomfortable list: five things a pixel genuinely gives you that an export does not, and what each one is worth.
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 Joris van Huët, Founder & CEOUpdated 3 min read
A pixel gives you five things an export does not, and being straight about them matters more than defending a position.
We sell the export-based read, so treat the following as a list written against our own interest.
The five
| What a pixel gives | Does it change a budget decision? |
|---|---|
| Real-time firing | Rarely. Causal estimates need a window to stabilise |
| Individual journey sequence | Sometimes, and less often than the slide suggests |
| Cross-domain stitching | Sometimes, if you genuinely run multiple domains |
| Event granularity below purchase | Rarely, for allocation questions |
| Platform-side optimisation signal | Yes, and this one is not a measurement question at all |
The last row is the important honest note. A conversion pixel is doing two jobs: it measures, and it feeds the ad platform's optimisation. If you remove it, the platform optimises worse. That is a real operational cost and it has nothing to do with which measurement method is more accurate.
Where each one genuinely matters
Sequencing matters when your channels play distinct roles in a long consideration cycle and you are deciding whether to fund an upper-funnel channel at all. Even then, sequence data tells you what order things happened in, not what caused what, which is a distinction covered in the correlation versus causation problem.
Cross-domain stitching matters if you actually run separate domains for content and commerce.
What the export gives that the pixel does not
The reverse list is shorter and worth stating. An export is unaffected by consent refusal, ad blocking and browser policy in a way session collection is not, so its coverage does not silently erode over time.
And it produces an answer without a collection period, because it reads history that already exists rather than starting to gather from today. That is the difference between measuring last quarter and measuring next quarter.
The framing that resolves it
These are different instruments for different questions, not competing versions of the same one. If your question is "which channel should get the next euro", an aggregate causal read answers it. If your question is "what did this specific person do", only session collection answers it.
Where teams go wrong is buying session collection for the first question because the vendor implied the extra detail produces a better answer. It produces more data. Whether it produces a better causal estimate is a separate question and usually not.
Where we sit
Causality Engine reads a Google Analytics CSV export and shows what each channel caused next to what last-click gave it, with a data-health score and a next step, with no tag installed anywhere. First read is €99 once, refundable within 30 days, no questions asked. Keep your conversion pixels for platform optimisation; that is what they are good at, and nothing here suggests removing them.
The comparison against tools that need the install is in attribution without a pixel or engineering.
Related answers
Frequently asked questions
Should I remove my Meta or Google conversion pixel?
No. Those pixels feed platform optimisation as well as reporting, and removing them degrades how the platform spends your budget.Does session-level data produce a better causal estimate?
Not automatically. It produces more data, which is not the same thing. For an aggregate question like which channel caused revenue, the limiting factor is usually the design of the comparison rather than the granularity of the underlying records.What does an export-based read handle better than a pixel?
Coverage stability. Export-based reads are unaffected by consent refusal, ad blocking and browser policy changes, so their reach does not erode quietly over time.
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
- AnalyticsAnalytics is the systematic computational analysis of data. It reveals customer behavior and measures campaign performance.
- AttributionAttribution identifies user actions that contribute to a desired outcome and assigns value to each. It reveals which marketing touchpoints drive conversions.
- CausalityCausality is the relationship where one event directly causes another, essential for identifying specific actions that drive desired outcomes in marketing.
- CausationCausation is the relationship where a change in one variable directly causes a change in another.
- ConversionConversion is a specific, desired action a user takes in response to a marketing message, such as a purchase or a sign-up.
- CorrelationCorrelation is a statistical measure showing a relationship between variables; it does not imply causation.
- Google AnalyticsGoogle Analytics is a web analytics service that tracks and reports website traffic.
- SessionA Session is a group of user interactions with your website within a given timeframe. It can include multiple page views, events, and transactions.