GA4 + Looker Studio: Build Dashboards That Actually Work

GA4's built-in reports are powerful but brittle. You can't share them easily, can't blend multiple data sources in one view, and can't schedule automated delivery to a client or exec team. Looker Studio (formerly Google Data Studio) solves all three problems.

The catch is that most people connect the two tools and end up with a cluttered page of charts that nobody reads. Getting real value from a GA4-powered Looker Studio dashboard takes more than dragging in a few metrics.

This guide covers how to connect GA4 to Looker Studio correctly, which charts to build first, common mistakes that corrupt your data, and how to structure dashboards that stakeholders actually use.

Why Looker Studio Over GA4's Native Reports?

GA4's standard interface is built for exploration, not communication. If you want to show a client their month-over-month traffic trend alongside their top landing pages and conversion rates, you're copying numbers into a spreadsheet or taking screenshots. That's not a workflow.

Looker Studio gives you a persistent, shareable URL that pulls live data every time someone opens it. You can combine GA4 with Google Search Console, Google Ads, BigQuery, or a spreadsheet in the same report. And you can schedule email delivery so reports land in inboxes automatically.

The free tier covers everything most teams need. There's no seat limit, no export cap, and no paywall on the connector for GA4.

Connecting GA4 to Looker Studio

Start at lookerstudio.google.com. Create a new report, select “Add data,” and choose the Google Analytics connector. You'll be prompted to pick your GA4 property.

One thing to understand: Looker Studio connects to GA4 through the same API that powers GA4's interface. That means the same sampling thresholds apply. If your property processes more than 10 million events per day on free GA4, you may see sampled data in complex reports. Blended data sources and date-range comparisons with high-cardinality dimensions are the most common triggers.

For most sites, this isn't a practical issue. If it is, connecting through BigQuery instead of the standard connector eliminates sampling entirely. GA4's BigQuery export is free to enable, though BigQuery storage and query costs apply.

Setting Up Your Date Range Control

Every dashboard needs a date range control placed prominently at the top. Without it, viewers are stuck with whatever default you set when building the report. Add a Date Range control from the toolbar, set a default range (last 28 days works for most teams), and enable the comparison period if you want period-over-period context built in.

Avoid the temptation to hard-code date ranges in individual charts. It makes the dashboard inflexible and creates confusion when someone filters to a different period and only some charts respond.

The Five Charts That Belong in Every GA4 Dashboard

Before building anything fancy, get these five elements right. They answer the questions every stakeholder asks first.

1. Sessions Over Time (Line Chart)

Use a time series chart with Sessions as the metric and Date as the dimension. Set the comparison period to the previous period. This gives anyone who opens the report an immediate read on trend direction - up, down, or flat - without having to interpret a table.

2. Channel Breakdown (Bar Chart)

A horizontal bar chart with Session Default Channel Group as the dimension and Sessions, Engaged Sessions, and Conversions as metrics gives a fast channel performance snapshot. If your GA4 channel groupings are misconfigured, this chart will expose it immediately - you'll see unusually large Direct or Unassigned buckets.

3. Top Landing Pages (Table)

A sortable table with Landing Page as the dimension and Sessions, Engagement Rate, and Conversions as metrics. Add a bar sparkline to the Sessions column so relative volume is visible without sorting. This is the chart that generates the most client questions - keep it simple and let the data speak.

4. Conversion Summary (Scorecard Row)

A row of scorecards showing Total Users, Engaged Sessions, Conversion Rate, and Conversions with period comparison enabled. Scorecards load fast, they're scannable, and they answer “how are we doing?” in under three seconds. Put them at the very top of the report, above everything else.

5. Device Category Split (Pie or Bar)

Mobile vs. desktop vs. tablet, broken out by sessions and conversion rate side by side. If mobile drives 70% of sessions but only 40% of conversions, that's your UX problem in one chart. You'd never notice it in the GA4 standard reports without drilling deliberately.

Blending GA4 with Google Search Console

One of Looker Studio's most underused features is data blending - combining two sources on the same chart using a shared dimension. For SEO work, blending GA4 sessions data with GSC clicks and impressions data gives you the full picture: how much search visibility you're earning and how much of it converts to site traffic.

The shared dimension is Landing Page (GA4) and Page (GSC). They need to match exactly - which means you need GSC set up to report full URLs, not relative paths, or you need a calculated field to strip the domain from GA4's landing page field.

Once blended, you can build a table showing GSC Clicks, GSC Impressions, GSC CTR, GA4 Sessions, and GA4 Conversions in a single row per page. That's the kind of analysis that usually requires manually linking GSC to GA4 and cross-referencing reports - Looker Studio does it in one view.

Calculated Fields: The Feature Most Builders Skip

Looker Studio lets you create calculated fields that don't exist in your raw GA4 data. These are formulas you define once and then use as dimensions or metrics anywhere in the report.

A few calculated fields that genuinely useful:

Revenue per session: Divide Purchase Revenue by Sessions. GA4 shows you total revenue and total sessions separately. Revenue per session tells you which channels are actually efficient, not just high-volume.

Engaged session rate: GA4 reports Engagement Rate natively, but if you want to apply it as a calculated field in a blend, you build it yourself: Engaged Sessions divided by Sessions. This is the metric that replaced bounce rate in GA4, and understanding it starts here. The GA4 engagement rate guide covers the logic in more depth.

Content category: A CASE statement on Landing Page that groups URLs into categories. Something like: if Landing Page contains “/blog/” then “Blog,” if it contains “/products/” then “Products,” else “Other.” This lets you see performance by site section without setting up custom dimensions in GA4 itself.

Common Mistakes That Break GA4 Dashboards

Using the Wrong Session Metric

GA4 has multiple session-related metrics: Sessions, Engaged Sessions, and New Users, among others. In Looker Studio, these all appear in the metric picker with similar names. The most common error is accidentally using “User Sessions” (a user-scoped metric) instead of “Sessions” (a session-scoped metric). They produce different numbers and the difference isn't obvious until someone notices the totals don't match GA4's own reports.

Always double-check metric scope. In Looker Studio, hover over any metric in the chart configuration panel to see its description and scope before adding it.

Mixing Incompatible Dimensions and Metrics

GA4 enforces dimension-metric compatibility. Some combinations simply don't work - mixing a user-scoped dimension with a session-scoped metric produces unexpected zeros or errors. Looker Studio will sometimes display these charts with blank data rather than an error message, which is worse because you don't know something's wrong.

When a chart shows less data than expected, check dimension-metric compatibility first. The GA4 dimensions and metrics explorer (available in Google's developer documentation) lists every valid combination.

Not Setting a Default Property Filter

If your Google account has access to multiple GA4 properties, the Looker Studio connector will pull from whichever property was selected during setup. If someone else on your team opens the report editor and accidentally changes the data source, every chart in the report breaks silently. Always document which property the report connects to, and consider locking the data source if the report is shared widely.

Multi-Page Reports: When to Use Them

A single-page overview dashboard serves most stakeholders. But if you're building a report for an agency client or a large internal team, multiple pages with focused scope work better than cramming everything onto one canvas.

A sensible page structure for a marketing report might be:

Page 1 - Executive Overview: Scorecards, trend line, channel split. One minute to read, answers “are we up or down?”

Page 2 - Acquisition Deep Dive: Channel breakdown with conversion rates, source/medium table, new vs. returning user split. Connects to the detail behind the overview. The GA4 acquisition report guide covers the underlying logic these charts should reflect.

Page 3 - Content Performance: Landing page table with GSC blend, top exit pages, engagement by content category. For SEO teams.

Page 4 - Conversions: Conversion events breakdown, conversion rate by channel, conversion rate by device. For marketing and product teams.

Keep navigation tabs clearly labeled. Looker Studio's page navigation appears at the top of the report by default - rename each page to reflect what's on it, not just “Page 1,” “Page 2.”

Scheduling and Sharing

Looker Studio reports can be shared as live links (anyone with the link sees current data) or as scheduled email deliveries (PDFs sent automatically on a schedule). For client reporting, scheduled PDFs remove the friction of expecting clients to log in and navigate to a URL.

To schedule delivery, open the report and select Schedule delivery from the Share menu. You can set daily, weekly, or monthly cadence, choose specific recipients, and customize the email subject. The PDF captures a snapshot at the time of delivery, so it serves as a historical record as well as a current report.

For internal teams, sharing the live link is usually better - it keeps everyone looking at the same real-time data rather than last week's PDF.

Connecting GA4 Attribution Data

Looker Studio reflects whichever attribution model GA4 is set to by default. If your GA4 property uses data-driven attribution, that's what Looker Studio reports. If you've switched to last-click for comparison purposes, that changes the numbers your dashboard shows.

This matters for channel-level reports. A channel that looks strong under data-driven attribution may look weaker under last-click, and vice versa. Understanding the GA4 attribution model behind your data is a prerequisite for interpreting channel performance correctly in any dashboard.

There's no way to switch attribution models inside Looker Studio itself. The model selection lives in GA4's property settings under Advertising - Attribution settings. Whatever you set there flows through to Looker Studio automatically.

Template Reports: Shortcut or Trap?

Looker Studio has a gallery of pre-built report templates, including several GA4-specific ones. They're useful for getting a first dashboard live quickly, but most need significant modification before they're actually useful.

The biggest issue with templates is that they're built around generic business assumptions. A template built for an e-commerce site will have purchase funnels and revenue charts that mean nothing to a SaaS company tracking trial signups. Using a template without adapting it to your conversion events often produces dashboards full of zero-value metrics.

Start with a template if you're under time pressure, but audit every chart against your actual business objectives before sharing it with anyone.

The Real Value: Automated Reporting That Doesn't Require You

The reason to invest time in building a strong Looker Studio dashboard is automation. Once it's built correctly, it updates itself, delivers itself, and answers the recurring questions that used to require manual report pulls every week or month.

That time compounds. An hour building a dashboard saves 30 minutes of manual reporting every week - that's 26 hours a year, and that's conservative if you're reporting to multiple stakeholders.

Combined with a platform that surfaces anomalies and recommendations automatically, like automated analytics reporting, you're not just replacing manual work - you're catching problems faster than any weekly review cycle would allow.

The GA4 and Looker Studio combination isn't a luxury for large teams. It's the minimum infrastructure for anyone who needs to track performance consistently without rebuilding the same spreadsheet every reporting cycle.