Why Looker Studio shows different numbers than GA4

Looker Studio reads its data straight from GA4, so it feels like they should match exactly. When they do not, it is almost always a configuration difference in the report, not a bug, and a handful of causes explain nearly all of it.

The usual causes

• Date range mismatch: the Looker report and the GA4 view are set to different ranges, or Looker uses a comparison period.
• Sampling: large or complex queries in Looker can be sampled, giving an estimate rather than the exact figure.
• Thresholding: GA4's data thresholding can hide small numbers differently depending on the dimensions in the report.
• Different metrics: "users" in Looker may be total users while GA4 shows active users, or the dimensions do not line up.
• Filters applied at the chart, page or data-source level that you have forgotten about.

How to track it down

Match the date ranges first, that fixes most cases. Then check for chart and page filters, confirm you are comparing the same metric (active vs total users), and look for a sampling indicator on the chart. Rebuild a single scorecard with no filters to sanity-check against the GA4 UI.

The bigger point

Looker is a presentation layer over GA4; it inherits GA4's quirks and adds report-level config on top. When numbers differ, suspect the report settings before you suspect the data. This is the same family of problem as GA4 vs BigQuery: same source, different processing.

Datahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · How to connect GA4 to Looker Studio