How to Connect GA4 to Looker Studio

The native GA4 connector in Looker Studio is free and built by Google. To use it: in Looker Studio, click Create → Data Source → Google Analytics, select your account, property, and data stream, then click Connect. The connector becomes a data source you can reference in any number of dashboards.

One data source can be used across multiple reports. You don't need to create a new data source per dashboard — create one per GA4 property and reuse it.

The connector connects at the property level, not the data stream level. If you select a specific web data stream, you get web-only data. If you connect at the property level, you get cross-platform data blended across web and app streams. For most web-only businesses, connecting at the data stream level produces cleaner, more predictable results.

What Works Well

The native connector is well-suited for a specific category of dashboards — regular business reporting where data freshness of 24–48 hours is acceptable and the date ranges are moderate (under 6 months of data at a time).

What Breaks or Underperforms

Sampling on large date ranges

The GA4 connector queries GA4's API, which applies sampling above certain data volume thresholds. For properties with high traffic volumes, date ranges longer than 3 months often return sampled data — the API picks a representative subset rather than processing all events. Looker Studio doesn't always surface this clearly, so reports may show subtly wrong numbers without warning.

The workaround: keep dashboard date ranges to 90 days or less when working with high-traffic properties, or use BigQuery as the data source for longer date ranges where sampling would be applied.

Missing metrics from the native connector

Not every GA4 metric available in the GA4 interface is exposed through the Looker Studio connector. Custom metrics, some engagement metrics, and certain ecommerce fields have historically been unavailable or named differently in the connector. If you need a specific metric and can't find it in the field list, check Google's connector documentation for the current state — the available field set changes with connector updates.

Dimension and metric cardinality limits

GA4 aggregates high-cardinality dimensions — page paths, event names with many unique values, product names in large catalogues — into an "other" bucket when the number of distinct values exceeds the API's row limit. In Looker Studio, this appears as an "(other)" row that can account for a significant chunk of data. It's the same behaviour as in GA4's standard reports, but it's more noticeable when building tables sorted by a dimension with thousands of unique values.

Data freshness lag

GA4 data in Looker Studio is typically 24–48 hours behind real time for most metrics. The connector doesn't show intraday data — if you need to see today's sessions, GA4's own interface (or the Realtime report) is more current. For daily or weekly reporting this lag is irrelevant; for intraday monitoring dashboards, the native connector isn't the right tool.

Blended data sources

Looker Studio lets you blend GA4 data with other data sources (Google Ads, Search Console, BigQuery tables). Blending by a shared key — date, campaign name — works for simple cases but produces incorrect numbers easily when the join key doesn't match precisely. Test blended sources carefully against the raw data from each source before sharing the dashboard.

Dashboards Worth Building in Looker Studio

Weekly acquisition summary

Sessions, new users, conversions, and conversion rate by channel group, with week-over-week comparison. Add a date range control and a channel filter so stakeholders can self-serve. This is the highest-value dashboard for most businesses and takes under an hour to build.

Landing page performance report

Page path as the primary dimension, with sessions, engagement rate, average engagement time, and conversions. Add a source/medium filter to isolate performance by channel. Useful for SEO and content teams comparing page performance across a manageable date range.

Campaign performance overview

Campaign name, source, medium, sessions, conversions, and cost (if cost data import is configured). Connects paid media spend to GA4 conversion data in one view without requiring platform-specific login access for stakeholders.

Conversion funnel summary

Event counts at each funnel step (product_view → add_to_cart → begin_checkout → purchase) with step-over-step drop-off rates. Simpler than GA4's Funnel Exploration and shareable with stakeholders who don't have GA4 access. Requires clean, consistently fired events at each step.

Don't build Looker Studio dashboards before auditing your GA4 data. A dashboard built on misconfigured events, inflated sessions, or broken attribution gives stakeholders a polished view of wrong numbers. Run a data quality check on your GA4 property before investing in dashboard infrastructure built on top of it.

When to Use BigQuery Instead

The native Looker Studio connector is the right choice for regular business reporting. It becomes the wrong choice when:

In those cases, the GA4 BigQuery export is the better foundation — Looker Studio connects to BigQuery too, and the BigQuery data source doesn't have the same sampling limitations. The tradeoff is infrastructure cost and the SQL knowledge required to build the queries.

GA4 Health Check verifies your property's data quality so that what you build in Looker Studio reflects accurate underlying data. Run a 60-second audit before you build your next client dashboard.

Travis Gunn
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.