Skip to content
accs-net.com

Press Esc to close

Configuration

Why Power BI Numbers Don’t Match GA4 (and How to Fix It)

ga4 to power bi

Power BI numbers rarely match GA4 exactly, because the two tools often read different versions of your data, at different times, under different rules.

Most gaps come from eight causes: summed metrics, trimmed date ranges, unfinished processing, sampling, thresholds, the (other) row, time zones and attribution.

Some gaps are expected and harmless. Others mean your report is wrong. This guide shows how to tell them apart and fix each one.

If you still need to set up the connection itself, start with our Power BI guide with connector and BigQuery steps.

Quick Answer: Why Power BI and GA4 Show Different Numbers

Cause Typical symptom Fix
Summed users or sessions Power BI total is higher than GA4 Query totals separately, never sum unique counts
Trimmed date range Long periods come in lower, single days match Pull shorter ranges and append them
Unfinished processing Yesterday is low, older days match Refresh again after 48 hours
Sampling Explorations differ from reports Shorten the range or use BigQuery
Data thresholds Rows missing with demographics Drop those dimensions or widen the range
(other) row Long lists lose their tail Fewer dimensions, cleaner values or BigQuery
Time zones Daily totals shift between days Use the property’s reporting time zone
Attribution scope Channels disagree, totals match Compare session scope with session scope

1. Users and Sessions Are Summed in Power BI

This is the most common cause, and it isn’t a GA4 problem at all.

Users and sessions are unique counts. One person who visits three pages counts once in total, but once on each page row.

When Power BI shows a total under a table of pages, it simply adds the rows together.

The result counts the same person three times, so your Power BI total runs well above the GA4 figure.

Event counts and revenue add up safely. Users, active users, sessions and engaged sessions don’t.

  • Import site totals in a separate query without the page or source dimension.
  • Turn off totals for unique-count columns in table visuals.
  • On BigQuery data, count users with DISTINCTCOUNT on the raw ID instead of summing.

The same logic explains why one query with more dimensions returns different user counts than a narrower query.

2. Wide Date Ranges Return Only Part of the Data

Microsoft documents this for the Google Analytics connector: very large date ranges return only a subset of values.

Nothing errors out. The refresh succeeds, the visual renders, and the totals are simply too low.

The fix is to stop asking for a year in one call. Add a date column, filter it, and append several shorter queries:

#"Filtered Rows" = Table.SelectRows(#"Added Items",
    each [Date] >= #date(2026, 1, 1) and [Date] <= #date(2026, 3, 31))

Repeat the same query for each quarter, then append the results into one table.

Query Diagnostics in Power Query shows the exact request sent to Google, so you can confirm which dates were asked for.

3. GA4 Hasn’t Finished Processing the Day

Google says data processing can take 24 to 48 hours, and report numbers may change during that time.

A morning refresh for yesterday often catches an incomplete day. GA4 fills it in later, while Power BI keeps the early numbers.

Leave a two-day lag in your reports, or refresh the last three days again on every run.

4. Sampling in Explorations and Large Queries

Standard GA4 reports usually show unsampled data. Explorations can switch to a sample when a query is too big.

For standard properties, Google sets the exploration limit at 10 million events per query.

Google’s reporting surfaces guide says sampling is also possible in reports and the Data API when a query exceeds the quota.

So if someone compares your Power BI table with a large exploration, the exploration may be the one that’s off.

Shorter date ranges reduce the risk, and the BigQuery export is never sampled at all.

5. Data Thresholds Hide Rows

GA4 withholds some rows to protect user privacy. Google calls this applying data thresholds.

Thresholds can apply when a report or API call includes demographic data or search queries with too few users.

Google’s quota reference names the Data API dimensions involved: userAgeBracket, userGender, brandingInterest, audienceId and audienceName.

Thresholds are system defined, so you can’t switch them off. You can only make them less likely:

  • Remove demographic dimensions from queries that don’t need them.
  • Widen the date range so each row has more users.
  • Check the data quality icon in the GA4 report you compare against.

6. The (other) Row Folds Long Lists

When a table has more rows than its limit allows, GA4 keeps the most common values and folds the rest into (other).

Google treats any dimension with more than 500 values as high-cardinality. Page paths with query strings and product SKUs are typical offenders.

How a high-cardinality GA4 dimension exceeds the table row limit and folds into one (other) row, while the BigQuery export keeps every value
The total stays correct while the per-value breakdown quietly loses its tail.

The Data API reads the same aggregate tables as the interface, so moving your report from the UI to the API doesn’t help.

You can shrink the problem by cleaning values upstream and pulling fewer dimensions per query. Only BigQuery removes it.

7. Time Zones Shift Daily Totals

Every GA4 report uses the property’s reporting time zone to decide where a day starts and ends.

In the BigQuery export, event_date follows that time zone, but event_timestamp is stored in UTC.

Build your Power BI dates from the timestamp without converting it, and late-evening events slide into the next day.

Google lists mismatched time zones among the main reasons why BigQuery data and GA4 reports disagree.

  • Use event_date for daily totals.
  • Convert timestamps to the property time zone before grouping by hour or day.
  • Check that nobody changed the property time zone in the middle of your comparison period.

8. Attribution Scope Doesn’t Match

GA4 offers several source dimensions, and each one answers a different question about where a visit came from.

  • First user source is the channel that first brought the user.
  • Session source is the channel that started each session.
  • Source on key events follows the property’s reporting attribution model.

Google says changing the reporting attribution model affects key event reports, while session-scoped dimensions like Session source stay the same.

That change also applies to historical data, so last month’s channel split can look different after someone edits the setting.

In BigQuery, traffic_source holds first user acquisition, and session_traffic_source_last_click holds last-click session data.

Data-driven attribution isn’t exported to BigQuery, so raw events can’t reproduce a data-driven channel report.

Compare like with like: session source with session source, first user with first user.

BigQuery vs the Data API: Two Different Datasets

The Google Analytics connector reads the same processed tables as GA4 reports. The BigQuery export holds raw events before that processing.

Feature Connector and Data API BigQuery export
Sampling Possible on large queries No
(other) row Yes, on long lists No
Behavioral modeling for consent mode Included Not included
Data-driven attribution Yes No
User and session counts Estimated with HyperLogLog++, as in GA4 reports Exact, counted by you
Reporting identity As set in the property Device ID only

Google says a 2 to 5 percent gap in total event count between GA4 and BigQuery is expected.

Its own example shows 1,463 sessions in reports against 1,501 in BigQuery for the same week.

Modeling can also show fewer active users in reports than in BigQuery, so neither side is broken.

Pick one source as the reference for each report and say so in the report. Don’t reconcile the two to the last digit.

A Failed Refresh Can Look Like a Mismatch

When a refresh fails, Power BI keeps showing the last good data. Someone compares it with live GA4 and sees a gap.

Data API quotas are a common reason. A standard property gets 200,000 core tokens per day, shared by every tool.

GA4 Data API token quota shared across Power BI, Looker Studio and third-party tools, with standard property and Analytics 360 ceilings compared
Quota is metered per property. Your Power BI refresh competes with every other tool querying the same GA4 property.
Data API quota Standard property Analytics 360
Core tokens per property per day 200,000 2,000,000
Core tokens per property per hour 40,000 400,000
Core tokens per project per property per hour 14,000 140,000
Concurrent requests per property 10 50

Check the refresh history in the Power BI service before you debug numbers. A failed run explains the gap at once.

How to Find Which Cause You Have

  1. Pick one finished day at least three days old and one metric, such as event count.
  2. Compare that day in Power BI and in a standard GA4 report, not an exploration.
  3. If the day matches but the full period doesn’t, you have date range trimming.
  4. If totals match but rows differ, look for an (other) row or thresholds.
  5. If Power BI is higher on users or sessions, check for summed rows.
  6. If channel numbers differ, compare the scope of the source dimensions.
  7. If BigQuery is your source, check time zones and allow a 2 to 5 percent gap.

Most disputes end at step three or five. The rest usually come down to comparing two different datasets.

Frequently Asked Questions

Why is my Power BI total higher than GA4?

Usually because Power BI adds unique counts across rows. Users and sessions can’t be summed, so query totals separately.

Why is my Power BI total lower than GA4?

The most likely causes are a wide date range that returned a subset of values, or a refresh that ran before processing finished.

Is GA4 data in Power BI sampled?

Standard report data usually isn’t. Large queries can be sampled when they exceed a quota, and the BigQuery export is never sampled.

Should GA4 and BigQuery numbers match exactly?

No. Google says a 2 to 5 percent gap in event counts is expected, and user counts differ because reports use estimation and modeling.

Which number should I report to stakeholders?

Pick one source per report and label it. Use GA4 reports for marketing trends and BigQuery for event-level or joined business data.

Clean numbers start before the connector. Our GA4 tracking QA checklist helps you catch broken events before they reach any dashboard.

Tom Martin
Written by

Tom Martin

Web analytics specialist with deep expertise in Google Analytics, Tag Manager, and e-commerce tracking. Helping businesses understand their data without the noise — practical guides, honest reviews, and real-world implementation experience.