Building Dashboards That Matter

What Looker Studio actually is

Looker Studio (formerly Google Data Studio) is a free tool that connects to GA4, Search Console, Google Ads, and dozens of other sources, and lets you build a report or dashboard from them without any coding. Conceptually, it does three things: it pulls data from a connected source, lets you display it as a chart, table, or single "scorecard" number, and lets you arrange several of those on one page that refreshes automatically as the underlying data updates.

The value of Looker Studio over just opening GA4 directly is not more data — it is less. GA4's own interface is built to let you explore anything; a Looker Studio dashboard is built to show exactly the handful of things you decided matter, laid out the way you want to see them, with nothing else competing for attention. That difference — a tool built for exploration versus a tool built for a fixed, recurring view — is the entire reason dashboards exist as a separate step from the analytics platform itself, and it is why building one is worth the modest upfront effort even though all the same underlying data is technically already visible inside GA4.

You do not need to learn Looker Studio's more advanced features — calculated fields, blended data sources, custom date parameters — to get real value from it. A dashboard built entirely from a handful of scorecards and one or two charts, pointed directly at GA4 and Search Console with no further customisation, already clears the bar of "better than opening five different reports every time."

Choosing 5–8 metrics tied to actual decisions

The single biggest failure mode in dashboard building is including too much. A wall of thirty tiles and charts, most of them never referenced, is not more informative than five well-chosen ones — it is just harder to scan, and it makes the important numbers easier to miss among the unimportant ones. This usually happens gradually rather than all at once: a metric gets added because it seemed interesting at the time, nobody ever removes anything, and eighteen months later the dashboard has grown well past the point anyone can take it in at a glance.

Apply the same test from Chapter 1 to every candidate metric: if it moved 20% in either direction, would that change a decision? If yes, it belongs on the dashboard. If the honest answer is "not really, it's just interesting to know," leave it off — or park it in a secondary, less prominent view rather than the main one. For most small businesses, a workable starting set looks something like: total conversions, conversions by channel, top-performing landing pages, organic clicks and average position (pulled from Search Console), and month-over-month trend on the primary conversion metric. That is five to six numbers — enough to answer "is the site working" and "where is it working" without requiring analysis to interpret.

It is worth resisting the temptation to add a metric just because a client or stakeholder once asked about it in passing. If a number genuinely matters to someone's decision-making, it belongs on the dashboard permanently; if it was a one-off curiosity, answering it once in a report is enough, and it does not need a permanent home on the page everyone opens every month.

Exec-summary vs. detailed views

Not everyone looking at the dashboard needs the same depth. It is worth deliberately separating two views inside the same report:

• An exec-summary page. Four to six large scorecards and one trend chart, readable in under a minute, answering "how are we doing" at a glance — this is what a busy owner or manager should see first, and it should never require them to interpret a table or cross-reference two numbers to get the headline answer.
• A detailed page (or pages). Channel breakdowns, page-level performance, campaign-level detail — for whoever is actually responsible for acting on the numbers day to day, and for digging into a specific question the summary page raised.

Looker Studio supports this directly through multiple pages within one report, with simple navigation between them. Building both from the start avoids the common trap of a single page trying to serve two different audiences and satisfying neither — a page dense enough to be useful for day-to-day channel management is usually too dense for a thirty-second glance, and a page simple enough for a thirty-second glance rarely has enough detail to actually diagnose a problem.

Building your first dashboard

A practical order of operations: connect your GA4 property and Search Console property as data sources first. Build the exec-summary page using scorecards for your chosen key numbers and one time-series chart showing the primary conversion metric over the last three to six months — trends over a longer window are far more informative than any single period, and a single month of data on its own rarely shows a pattern worth acting on. Add a detailed page with a table breaking conversions down by channel, and another showing top landing pages by traffic and conversions. Set the default date range to something sensible for how often you will actually check it — typically "last 28 days" or "last 3 months" rather than a single week, which is too short a window to see a meaningful trend.

Once built, the report link can be shared with anyone who needs visibility — a business partner, a client, or your future self — without giving them login access to the underlying GA4 or Search Console accounts, which is a useful separation of "who can see the numbers" from "who can change the tracking setup." It is also worth revisiting the dashboard itself every few months, the same way you would revisit the key event list — as the business changes, the five to eight numbers that mattered most a year ago are not guaranteed to be the same ones that matter most now.

The right set of metrics is not identical for every business, and it is worth resisting the temptation to copy someone else's dashboard wholesale. A business built on repeat purchases will want to see returning-customer conversions alongside new ones; a project-based service business cares more about enquiry quality and close rate than raw volume; a business running a single dominant paid channel will want that channel's cost data blended in alongside GA4's conversion numbers, so cost and outcome sit on the same page rather than in two separate tools. Start from the generic five-to-six-metric template above, then adjust it once you have used it for a month or two and have a clearer sense of what you actually reach for.