BigQuery Export (GA4)
AnalyticsAlso: GA4 BigQuery Export · GA4 Raw Data Export
Quick definition
BigQuery Export is a native Google Analytics 4 (GA4) feature that continuously copies your raw event data into Google BigQuery, Google's cloud data warehouse. It gives analysts direct SQL access to unsampled, hit-level data that the GA4 interface cannot surface on its own.
How it varies across Australia
BigQuery Export adoption among Australian businesses is growing but still concentrated in larger organisations with dedicated analytics or data engineering resources. Most small-to-mid-market businesses with GA4 have not enabled the export, which means they are relying entirely on the sampled, aggregated interface and losing access to the raw signal underneath.
See data and tracking maturity across Australian industries →What it actually means
GA4 collects every user interaction as an event. When someone views a page, scrolls past 90%, clicks a button or completes a purchase, GA4 records that as a row of data with a timestamp, device, session ID and a set of parameters. The GA4 interface shows you aggregated summaries of those rows.
BigQuery Export copies those rows, in full, to your own Google Cloud project. Every event. Unsampled. Queryable with SQL.
This matters because GA4's built-in reporting applies sampling once your data volumes get large, applies attribution logic you cannot override, and has no memory of how the interface defined a metric last month. Once you query BigQuery directly, you define the logic yourself.
For attribution modelling, cohort analysis, cross-device path analysis or any reporting that needs to join GA4 data to a CRM or revenue feed, BigQuery Export is the only path that does not involve manually exporting CSVs.
The data arrives in a nested JSON structure inside BigQuery. That structure is not friendly to analysts who expect flat tables. Understanding how GA4 packs event parameters into repeated records is the learning curve most teams underestimate.
Once the schema is understood, it pairs well with tools like Looker Studio, dbt and Hex for building dashboards and data models that sit closer to how the business actually thinks about conversion rate, customer acquisition cost and lifetime value.
The GA4 interface is the summary. BigQuery Export is the spreadsheet behind it.
How it shows up
BigQuery Export shows up in three places. First, in Google Cloud Console as a dataset named after your GA4 property ID, with one table per day named events_YYYYMMDD. Second, in the billing dashboard when your query volume or streaming volume generates charges. Third, in the quality of analysis your team can produce: once you have the raw events, segmentation, funnel reconstruction and session-level attribution become possible without relying on GA4's pre-built reports.
Common queries teams run against the export include rebuilding funnels with custom session definitions, calculating conversion rate on specific user segments the GA4 interface cannot filter, and joining event data to order data from a separate warehouse to reconcile GA4 revenue figures against actual revenue.
The Australian context
Australian businesses operating under the Privacy Act and the Australian Privacy Principles need to confirm their Google Cloud project and BigQuery dataset region is set to store data in Australia or a compliant region before enabling streaming export. The default region may not satisfy data residency requirements for businesses in regulated industries like finance or health. Checking this before enabling the export is easier than migrating a populated dataset later.
Where people get this wrong
Related terms
Common questions
Is BigQuery Export free?
The daily batch export is free. Streaming export, which sends data in near-real-time rather than waiting for the daily batch, incurs Google Cloud charges. Storage and query charges also apply once your data grows or query volumes increase. For most small-to-mid businesses the costs are modest, but they are not zero.
How long does it take for data to appear in BigQuery?
Daily batch export typically lands within 24 hours of the event date, often by mid-morning the following day. Streaming export appears within minutes but costs more. For most reporting use cases, the daily batch is sufficient.
Do I need a developer to set up BigQuery Export?
Setup is done inside GA4's admin panel and requires a Google Cloud project with billing enabled. It does not require code changes. However, making the exported data useful typically requires an analyst or developer who understands SQL and the GA4 schema structure.
What can I do with BigQuery Export that I cannot do in GA4?
Query unsampled data at full hit-level detail, build custom session and funnel definitions in SQL, join GA4 events to CRM or transaction data from other sources, and create data models that define conversion rate and attribution in ways the GA4 interface does not support. It is the difference between reading a summary and reading the original.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →