Attribution export to BigQuery
GA4's BigQuery export delivers raw, event-level data — every event with its parameters and user/session identifiers — enabling teams to compute attribution outside the platform's built-in models. With the full path available as rows, analysts can implement custom rules, Markov or Shapley models, or reconcile against CRM and spend data, rather than accepting only the models the reporting UI offers. It is the foundation for bespoke, auditable attribution.
Why export changes what is possible
The GA4 reporting UI offers a fixed set of attribution models. The BigQuery export instead provides raw event rows — event name, parameters, timestamp, session and (where available) user identifiers — so the full sequence of touches is queryable.
With paths as data, analysts can implement any model: custom rules, position weights, Markov chains, Shapley values, or hybrids, and audit exactly how each conversion was credited.
Reconciliation and governance
Event-level data also lets you join GA4 with cost, CRM, and offline-conversion tables to build closed-loop and blended views the UI cannot produce. That makes the warehouse the place to reconcile platform claims against one consistent dataset.
Governance matters: exported rows may carry identifiers, so apply access controls, retention limits, and consent-aware filtering. The benefit is transparency — every attribution number traces back to inspectable events.
- Raw event rows expose full paths, not just summaries
- Build custom, algorithmic, or hybrid models on the data
- Join cost/CRM/offline tables; govern identifiers carefully
How it appears in analytics and logs
If reporting-UI models cannot answer a question, the event-level export usually can — it exposes the underlying paths the UI only summarizes.
Diagnostic use case
Build a custom or algorithmic attribution model on raw event-level paths, beyond the fixed models available in the GA4 interface.
What WebmasterID can help detect
WebmasterID's first-party events can sit alongside exported GA4 data in a warehouse, giving an independent event stream to reconcile attribution against.
Common mistakes
- Assuming UI models are the only attribution options.
- Exporting identifier-bearing data without access controls.
- Skipping reconciliation against a single source of truth.
Privacy and accuracy notes
Exported event data can contain identifiers, so access and retention must follow consent and minimization. Educational, not legal advice.
Related pages
- Custom attribution models: power and rope
A custom attribution model lets you define your own credit rules — adjusting weights, lookback, and channel treatment beyond the presets. The flexibility can fit a real, unusual journey, but it just as easily encodes the answer you wanted. A custom model is only as honest as the assumptions you can defend.
- Markov chain attribution
Markov chain attribution models customer journeys as a probabilistic graph of transitions between channel states, ending in conversion or null. Each channel's credit is derived from its 'removal effect' — how much the overall conversion probability falls if that channel (and its transitions) are removed from the graph. It is a leading algorithmic alternative to Shapley-based attribution.
- GA4 model comparison report
The GA4 model comparison report (under Advertising > Attribution) places two attribution models next to each other for the same conversion events, exposing how much credit each channel gains or loses when you change the rule. It does not change billing or optimization — it is a diagnostic to understand model sensitivity before acting.
- MCP analytics
Query first-party events alongside warehouse data.
Sources and verification notes
- GA4 — BigQuery Export (developers.google.com)Documents the GA4 event-level BigQuery export schema.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.