BigQuery · Tools · Comparison
BigQuery vs Supermetrics for GA4:
When to Use Each
Supermetrics and BigQuery are both commonly used to get GA4 data out of GA4's interface and into somewhere more useful. But they're not competing tools — they solve fundamentally different problems, suit different situations, and fail in different ways. This is an honest comparison of what each does well, what each costs, and how to decide which one belongs in your setup.
11 min readUpdated April 2026
The comparison between Supermetrics and BigQuery comes up constantly in analytics conversations, and it's usually framed as a question of budget — Supermetrics costs money every month, BigQuery might seem like the more "serious" or technical alternative. That framing misses what actually matters: the two tools do different things, and choosing between them based on price or technical prestige rather than what your analysis actually requires leads to the wrong choice in both directions.
Some teams pay for Supermetrics and use it for things BigQuery would do better. Some teams build BigQuery pipelines for reporting that Supermetrics would deliver in a fraction of the time. The right question isn't "which is better" — it's "what do I actually need to do with this data?"
The single most important difference: Supermetrics queries the GA4 Data API — the same interface GA4's own reports use, subject to the same sampling. BigQuery contains the raw exported events — unsampled, at row level, queryable with full SQL. If sampling is affecting your analysis, Supermetrics cannot solve it. Only BigQuery can.
The sampling problem — why it matters more than most people realise
GA4 applies data sampling when queries exceed a certain threshold of events — typically when you're looking at large date ranges, high-traffic properties, or complex segmentation. When sampling kicks in, GA4 analyses a subset of your data and extrapolates the results. The reported numbers are estimates, not exact counts.
Supermetrics queries the GA4 Data API. The GA4 Data API is subject to the same sampling as GA4's interface. Using Supermetrics does not give you unsampled data — it gives you the same sampled data that GA4 shows, delivered into a different interface.
BigQuery contains the raw exported events — every single event, exported before any sampling or aggregation occurs. Queries against BigQuery data are never sampled. If the exact number matters — conversion counts for paid media reporting, revenue figures for finance, session counts for client-facing dashboards — BigQuery is the only path to numbers you can fully trust.
When to check whether sampling is affecting you: in GA4's standard reports, look for the shield icon in the top right of any report. A yellow shield means partial data (light sampling). A red shield means heavily sampled data. If you're regularly seeing these warnings on your standard reports, any Supermetrics data pulling from those same date ranges will have the same problem.
When Supermetrics is the right choice
Pulling GA4 sessions and conversions alongside Google Ads spend, Meta impressions, and LinkedIn clicks into a single Looker Studio dashboard is exactly what Supermetrics is built for. The connector handles all the API authentication, rate limiting, and data normalisation. Setting this up in BigQuery would require separate exports or API calls for each platform — significantly more infrastructure for something Supermetrics delivers in an afternoon.
For a site with under 500k sessions per month, GA4 API sampling is unlikely to be a significant issue for standard reporting metrics. Supermetrics delivers sessions, users, conversions, and revenue into a formatted report quickly and reliably. The cost is justified by the time saved compared to building and maintaining a BigQuery pipeline for the same output.
Supermetrics makes GA4 data accessible to analysts who work in spreadsheets but don't write SQL. If the analysis your team needs to do can be expressed through GA4's dimensions and metrics — and sampling isn't a problem — Supermetrics is the right tool. Forcing a team to learn BigQuery SQL for reporting that Supermetrics handles well is the wrong trade-off.
When BigQuery is the right choice
For properties processing millions of events per day, GA4 API sampling is not a minor rounding issue — it can materially affect reported conversion counts and revenue figures. If you're regularly seeing sampling warnings in GA4, the numbers you're reporting and making decisions from are estimates. BigQuery exports raw events before any sampling occurs. For high-stakes reporting where accuracy matters, there is no alternative.
GA4 data alone can tell you how many sessions came from organic search. GA4 data joined with your CRM can tell you which organic sessions converted to qualified leads, which leads closed, and what the revenue value was per acquisition channel. Supermetrics can pull GA4 data into a spreadsheet. It cannot join it to a CRM export, a product database, or a fulfilment system. Any analysis that requires combining GA4 with data that doesn't live in a marketing platform needs BigQuery.
GA4 allows up to 50 custom dimensions, but only a subset of event parameters are exposed through the Data API. The BigQuery export contains every event parameter on every event — including custom ones your developers added that never appear in the GA4 interface. If your analysis depends on event parameters that GA4's reporting doesn't surface, BigQuery is the only path.
GA4's maximum data retention for user-level data is 14 months. After that, it's gone from GA4's interface — and from the Data API. BigQuery retains data for as long as you keep it. If you export data from the beginning of your GA4 property's life, you have that data in BigQuery indefinitely. Year-over-year comparisons beyond the 14-month window, multi-year trend analysis, and cohort studies over extended periods are only possible in BigQuery.
The tools aren't mutually exclusive. A common setup: Supermetrics for pulling ad platform data (Google Ads, Meta, LinkedIn) into Looker Studio, and BigQuery for the GA4 data that needs to be unsampled or joined with other sources. Both feed into the same Looker Studio dashboard via blended data sources. You use each tool for what it's genuinely good at.
Cost comparison
Supermetrics
$99+/mo
Starter plan from ~$99/month for Looker Studio. Higher tiers for more destinations (Sheets, Excel, data warehouses) and more connectors. Pricing has increased significantly in recent years — check current pricing on their site as it changes frequently.
BigQuery
~$0–50/mo
GA4 BigQuery export is free. BigQuery charges for storage ($0.02/GB/month) and queries ($5 per TB scanned, with 1TB free per month). For most GA4 setups with sensible partition filtering, monthly costs are very low — often under $5. Scales with data volume and query frequency.
The cost comparison is not as straightforward as it appears. Supermetrics has a predictable monthly cost. BigQuery has variable costs that depend on how much data you store and how efficiently you write your queries. For most GA4 properties, BigQuery costs are very low — but without partition filtering on queries, costs can escalate quickly on high-volume properties.
Always filter BigQuery queries by date partition. Querying the GA4 events table without a _TABLE_SUFFIX or event_date filter scans all historical data every time — which at high volumes can result in significant charges. Every query against the events table should include a date range filter that limits how much data is scanned.
The decision framework
| If your situation is... |
Use |
| Standard performance reporting, multiple ad platforms, low-medium traffic |
Supermetrics |
| Team works in Sheets/Excel, no SQL capability |
Supermetrics |
| Need GA4 + ad platform data combined quickly |
Supermetrics |
| Seeing sampling warnings in GA4 on important reports |
BigQuery |
| Need to join GA4 with CRM, product, or financial data |
BigQuery |
| Analysis of custom event parameters not in GA4 UI |
BigQuery |
| Historical analysis beyond 14 months |
BigQuery |
| Multiple GA4 properties needing combined analysis |
BigQuery |
| Multi-platform reporting + some unsampled GA4 data needed |
Both |
| Complex SQL analysis + standard ad platform reporting |
Both |
The honest answer for most growing businesses is that you'll start with Supermetrics because it's fast and accessible, and add BigQuery when one of the BigQuery scenarios above becomes relevant — usually when sampling starts affecting accuracy, when you need to join data sources, or when you outgrow the 14-month retention window.
The mistake to avoid is treating BigQuery as a status upgrade from Supermetrics. It's not. It's a different tool that becomes the right choice when the problems it solves are the problems you actually have.
Before either tool: both Supermetrics and BigQuery are only as reliable as the GA4 data they're pulling from. Sampling, zombie conversion events, staging traffic contamination, and attribution problems all flow through to whatever tool you use downstream. Getting the GA4 property right first is the highest-leverage thing you can do before investing in any reporting infrastructure on top of it.
Is your GA4 data reliable enough to build on? GA4 Health Check audits your property in 60 seconds — 47 checks across 7 modules. Know what you're working with before you build reporting infrastructure on top of it.
Run the audit — $79 →
Founder of GA4 Health Check. Working with Google Analytics since 2013, with over 250 clients audited across almost every industry vertical. 100% Job Success on Upwork for over a decade.