How to Enable Google Analytics 4 BigQuery Export

The standard Google Analytics 4 interface is powerful, but it comes with limitations like data sampling, 14-month retention limits, and a fixed set of reporting tools. The free native BigQuery export in GA4 is your key to unlocking your raw event data and moving past those restrictions. This article will guide you through the entire process, step-by-step, showing you how to enable the export and what to do once your data starts arriving.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Why Set Up the GA4 BigQuery Export?

Connecting Google Analytics 4 to BigQuery might sound overly technical, but the benefits are massive for anyone serious about growing their business with data. It transforms your analytics from a simple reporting tool into a sophisticated analysis engine you completely control.

Say Goodbye to Data Sampling

If you've ever run a complex report in the GA4 "Explore" section and seen a green checkmark icon, you've encountered data sampling. To speed up reports, GA4 analyzes a subset of your data and then extrapolates the results to represent the whole. For quick trend analysis, this is fine. For critical business decisions, it’s not ideal.

The BigQuery export sends every single raw event that’s collected, giving you a complete, unsampled dataset. Every click, every page view, every scroll - it’s all there. This means your analysis is 100% accurate, allowing you to trust the numbers you're basing your strategy on, whether it's for conversion rate optimization, budget allocation, or customer-level analysis.

Gain Full Data Ownership and Control

By default, GA4 only holds onto your detailed, user-level event data for a maximum of 14 months. After that, it’s gone forever. While aggregated reports remain, you lose the ability to analyze older user-level behavior or perform long-term cohort analysis.

When you export your data to BigQuery, it resides in your own Google Cloud project. You own it. You can keep it indefinitely, build a complete historical archive of customer behavior, and ensure you have the data you need for multi-year trend analysis without worrying about Google’s retention policies.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Unlock Advanced, Custom Analysis

The real power of having raw event data in BigQuery is the ability to analyze it however you want. You are no longer constrained by the pre-built reports in the GA4 interface. By writing SQL queries, you can:

• Combine Online and Offline Data: Join your GA4 user data with data from your CRM (like Salesforce or HubSpot), payment processor (like Stripe), or a customer support platform. This lets you connect a user’s website journey to their lifetime value, support tickets, and sales cycle.
• Build Custom Attribution Models: Go beyond GA4’s standard attribution models by creating your own weighted models in SQL to better understand how different channels contribute to conversions.
• Perform Deeper Funnel Analysis: Analyze complex user journeys and identify specific drop-off points in your funnels with far more granularity than what’s possible in GA4.
• Enrich Data for Machine Learning: Use your clean, raw event data to build predictive models, like customer churn prediction or lifetime value projections.

Connect to Advanced BI and Visualization Tools

While GA4 is great for many things, its dashboarding capabilities can be limiting. Once your data is in BigQuery, you have a direct, high-performance connection to professional business intelligence tools like Tableau, Power BI, and Looker Studio. This allows you to build comprehensive, interactive dashboards that blend GA4 data with information from all your other business tools, creating a single source of truth for your team.

Before You Start: Prerequisites

Before you get into the setup process, you'll need to make sure you have the right permissions and accounts in place. It will save you a lot of time to have these ready ahead of time. Here's what you need:

• A Google Analytics 4 Property: This guide assumes you already have a working GA4 property collecting data. If you’re still on Universal Analytics, you’ll need to migrate first.
• Editor Role for the GA4 Property: You - or the person performing the setup - must have "Editor" level permissions on the Google Analytics account. "Viewer" or "Analyst" roles will not be sufficient to link new products.
• A Google Cloud Platform (GCP) Account: BigQuery is a part of Google Cloud. If you don’t have one already, you’ll need to create a GCP account connected with a billing account. Don’t worry, the export itself is largely free, but Google requires a billing account on file for all projects. New GCP users often get free starting credits.
• Owner/Editor Role on the GCP Project: You need adequate permissions on the Google Cloud project where you plan to send the data. Ideally, you should be the "Owner," but "Editor" also typically works.
• BigQuery API Enabled: The BigQuery API needs to be enabled for your selected Google Cloud project. It's usually enabled by default when you create a new project, but it’s worth checking. You can do this by searching for "BigQuery API" in the GCP console search bar and making sure it’s enabled for your project.

Step-by-Step Guide to Linking GA4 and BigQuery

Once you have all the prerequisites sorted, the actual linking process is surprisingly straightforward and only takes a few minutes inside the Google Analytics admin panel.

Step 1: Navigate to the BigQuery Links Section

Log in to your Google Analytics 4 account and go to the Admin screen by clicking the gear icon in the bottom-left corner. In the center “Property” column, find the section called “Product Links” and click on BigQuery Links.

Step 2: Start a New Link Configuration

On the BigQuery linking page, you’ll see any existing links or a blank space if this is your first time. Click the blue Link button to start the setup process.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Step 3: Choose Your BigQuery Project

Next, you’ll need to tell Google Analytics which Google Cloud project to send the data to. Click on Choose a BigQuery project. A sidebar will open showing a list of all the GCP projects your Google account has access to. Select the one you prepared earlier and click Confirm.

Important Tip: If you don’t see your project listed here, it’s almost always a permissions issue. Go back and double-check that your account has the Owner/Editor role on that specific GCP project.

Step 4: Configure Data Settings

This is where you’ll fine-tune what data gets exported.

• Data Streams: First, you need to select which data streams from your GA4 property to export. Most businesses will only have one "Web" stream, but if you have iOS and Android app streams, you can select those as well.
• Frequency: This is a crucial setting. You have two options:
• Manage Events: You can choose to exclude certain high-volume, low-value events from your export to keep your dataset cleaner and your potential BigQuery costs lower. To do this, click "Configure events to include" and click "Add" to select events you do want. Or, click "Add event to exclude" to specify which event names (e.g., scroll, session_start) should not be sent to BigQuery. For a start, it's often best to just export everything until you know what you don't need.

Step 5: Review and Create the Link

In the final step, you'll see a summary of your configuration: the chosen project, the data streams, and the export frequency. Review it one last time to make sure everything looks correct. If it does, click the Submit button. That's it! The link is now active.

What Happens Next? Verifying Your Data

It's important to know that data will not appear in BigQuery instantly. The linking activates the export for data moving forward - it does not backfill historical GA4 data.

The first full daily export will appear in your BigQuery project within 24-48 hours after you create the link. To check if it’s working, navigate to your Google Cloud project and go to the BigQuery SQL Workspace.

In the left-hand Explorer panel, you should find your project. Under it, you'll see a new dataset named analytics_<property_id>. Click the drop-down arrow next to it. After a day or two, you should see your first table appearing, named according to this convention:

• For Daily exports: events_YYYYMMDD (e.g., events_20240315)
• For Streaming exports: events_intraday_YYYYMMDD (a temporary table that is consolidated at the end of the day)

If you see these tables, your GA4 BigQuery export is successfully set up and running.

Understanding the Costs

While enabling the export link in GA4 is free for all properties (standard and 360), working with the data in BigQuery has its own pricing model. The good news is that there's a very generous free tier.

• Linking GA4: Free.
• Daily Data Export: Free.
• Streaming Data Export: Paid, based on data volume.
• BigQuery Data Storage: The first 10 GB of data stored per month is free. For most small-to-medium websites, you are unlikely to exceed this for a long time.
• BigQuery Data Querying: The first 1 TB (terabyte) of data processed by your queries each month is free. Again, this is a huge amount, and most users stay well within this limit while learning and building reports.

Your main cost will be the streaming export if you choose to enable it. Otherwise, you can perform quite a lot of analysis before ever seeing a bill from Google Cloud.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

First Steps for Querying Your GA4 Data

Now for the fun part: actually using your data. The GA4 schema in BigQuery can be intimidating at first because all the useful information like page URLs, campaign names, and button text is nested inside a field called event_params.

You can use the UNNEST() function in SQL to unpack this data. Here is a simple starter query to count pageviews per page path on a specific day. Replace <your_project_id>, <your_property_id>, and the date with your actual information.

SELECT
  params.value.string_value AS page_path,
  COUNT(params.value.string_value) AS pageview_count
FROM
  `<your_project_id>.analytics_<your_property_id>.events_20240315`,
  UNNEST(event_params) AS params
WHERE
  event_name = 'page_view' AND params.key = 'page_location'
GROUP BY 
  page_path
ORDER BY 
  pageview_count DESC,

This simple query demonstrates the pattern you will use often: select a value from event_params where a specific key is present. Learning some basic SQL is the next step on your journey to mastering your GA4 data.

Final Thoughts

Setting up the GA4 BigQuery export is one of the most impactful things you can do to elevate your digital marketing analytics. It moves your data out of Google's walled garden and into your control, breaking free from sampling and retention limits and opening the door to far deeper, more meaningful analysis than the GA4 interface alone can provide.

Of course, becoming proficient in SQL to wrangle your raw BigQuery data is a steep learning curve. At Graphed, we simplify this process entirely. You can connect your Google Analytics account in seconds, and instead of writing queries, you just ask questions in plain English. Simply say, "Show me a chart of pageviews by page location," and our AI handles all the complex data extraction for you, instantly creating live, interactive dashboards so you can focus on insights, not SQL syntax.