Quri

GA4 BigQuery export

Last updated 2026-06-14

Definition

GA4 BigQuery export pulls your raw, per-event GA4 data into Atlas through BigQuery. The standard GA4 API hands back sampled, aggregated reports. The BigQuery export gives Quri one row per event, so the journey graph is built on what actually happened rather than GA4’s rounded-off summary of it.

How to do this in Quri

  1. Enable GA4’s BigQuery export in your Google Analytics admin.
  2. Connect the BigQuery export to Quri in your Atlas source settings.
  3. Let Quri pull per-event rows into the journey graph.
  4. Open /app/atlas to confirm GA4 events now appear at full per-event detail.

Frequently asked

Why use the BigQuery export instead of the GA4 API?
The GA4 reporting API can sample and aggregate, which blurs individual journeys. The BigQuery export gives one row per event, so Quri stitches real per-user behaviour instead of a summarised approximation.
Does GA4 still miss data even with the export?
Yes. GA4 is client-side, so events blocked by consent banners, ad blockers, or pre-consent loads never reach it — and what GA4 never recorded, the export cannot supply.

Related terms