Looker Studio discrepancies
A Looker Studio dashboard can show different figures from the GA4 property it draws on. The causes sit in the reporting layer: the connector may trigger sampling, default date ranges and filters differ, blended data sources fan out rows on joins, and cached results lag the source. This page explains why a dashboard and its source disagree and how to make a report trustworthy.
Where the reporting layer changes numbers
Looker Studio queries a source through a connector, and that query can hit the source's sampling thresholds even when the native UI report did not, because the dimensions and date span requested differ. Default date ranges, control filters, and page-level filters in a report may not match what you compared against in GA4.
Thresholding in the source can also carry through, so low-volume segments are suppressed in the dashboard exactly as they are at source.
- Connector queries can trigger source sampling
- Different default date ranges and applied filters
- Source thresholding suppresses low-volume rows downstream
Blends and caching
Blended data sources join on shared keys; a one-to-many join fans out rows and can multiply metrics if the join key is not unique, inflating totals. Looker Studio also caches results to stay fast, so a chart can lag the live source until the cache refreshes.
Reconcile by matching date ranges and filters exactly, checking for sampling indicators, verifying blend join keys are unique, and refreshing the cache before comparing.
How it appears in analytics and logs
A dashboard that disagrees with its source usually reflects connector sampling, mismatched date ranges or filters, or a blend fanning out rows — not corrupted data.
Diagnostic use case
Diagnose why a Looker Studio chart disagrees with the underlying GA4 report before blaming the data, by checking sampling, dates, joins, and caching.
What WebmasterID can help detect
WebmasterID exposes first-party events you can chart directly, so a dashboard reflects raw counts rather than a re-aggregated, possibly sampled extract.
Common mistakes
- Comparing a dashboard and source over different date ranges.
- Blending on a non-unique key and multiplying metrics.
- Reading a cached chart as live and current.
Privacy and accuracy notes
Dashboards inherit the source's privacy posture; thresholding and sampling carry through. Keep shared reports free of any field that could expose individuals.
Related pages
- Analytics sampling: when reports estimate
Sampling is when an analytics tool computes a report from a fraction of the data and extrapolates. It keeps big queries fast, but it adds estimation error — worst for small segments and rare events, where a few sampled sessions get scaled into a confident-looking number. Knowing when a report is sampled is the first defence.
- BigQuery vs UI discrepancies
When GA4's BigQuery export and the reporting interface show different totals, it is usually not a bug. The UI applies sampling, data thresholds, (other) aggregation, and behavioral/conversion modeling on top of the raw event stream; BigQuery exports the unmodeled, unsampled events. Knowing which transformations the UI adds explains most gaps.
- Data thresholding in GA4
Data thresholding is a GA4 privacy mechanism: when a report could let someone infer the identity of individual users from low-volume rows (especially with Google Signals or demographics enabled), GA4 hides some data. The result is missing rows and report totals that do not reconcile. This page explains when thresholding applies and how to recognize it.
- Agency analytics
Dashboards built on raw first-party counts.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.