How Do You Create a KPI Dashboard in Google Analytics?

How Do You Create a KPI Dashboard in Google Analytics?

Somebody asks for "a KPI dashboard in Google Analytics" and you open GA4 looking for the dashboard builder.

There isn't one. Not in the sense people mean when they say the word.

Universal Analytics had a Dashboards menu with draggable widgets. GA4 removed it, and the thing that replaced it has a different name, lives somewhere unexpected, and behaves differently enough that most people never find it.

The replacement is the report Library. It is genuinely good once you know what it is, and it is free. This guide shows you how to build a KPI dashboard with it, what the hard limits are, and when you should stop and use something else instead.

The Short Answer

You build a KPI dashboard in GA4 by creating a collection in the report Library, filling it with topics, and giving each topic an overview report whose summary cards are your KPIs.

Google's own help documentation describes the Library plainly: "Report library lets you manage and customize the reports and navigation in the Reports section of your Google Analytics property."

The overview report is the dashboard. The collection is how it reaches the left-hand navigation so your team can actually find it.

You need the Editor or Administrator role. Google states that "Editors and administrators can access the report library from the bottom left of the Reports section." Viewers cannot build one.

Your analytics tells you what happened. Does it tell you why? A free SEO audit shows which pages search and AI assistants actually surface for your site. Get a free audit.

What the GA4 Report Library Actually Is

The Library is a navigation editor. That framing clears up most of the confusion.

In GA4, the left-hand menu under Reports is not fixed. The groups you see there — Life cycle, User, and anything else — are collections, and collections are editable objects.

Collections, Topics and Reports

Three nested levels make up the structure, and they map onto the dashboard idea cleanly once you see them.

A collection is a menu group in the left navigation. Google's documentation describes it as the layer that "enables you to choose the reports that appear on the left."

A topic is a section within that collection. Each topic groups related reports under one heading.

A report is the actual page of data. There are two kinds, and the difference matters more than anything else here.

Overview Reports vs Detail Reports

A detail report is a conventional table with a chart on top. One dimension, several metrics, rows you can sort and filter.

An overview report is the dashboard. Google describes it as a surface where "the overview report in each topic provides a set of cards that summarize information for that business objective."

Those summary cards are your KPIs. Each one shows a single headline number with a small trend, which is precisely the format a KPI dashboard needs.

Each topic can hold only one overview report. That constraint shapes the whole design, so plan around it rather than fighting it.

How to Build It, Step by Step

The build itself takes about twenty minutes. Deciding what belongs on it takes longer, which is the usual ratio.

1. Open the Library. Go to Reports, then scroll to the very bottom of the left navigation. The Library link sits below everything else, which is why people miss it.
2. Create the collection. Click the create button and choose either a blank collection or a template. Blank gives you full control; a template gives you a starting structure you then edit.
3. Name it for the audience, not the data. "Executive weekly" or "Content performance" tells people whether to open it. "KPI dashboard v2" does not.
4. Add your topics. Each topic is one section of the dashboard. Three or four is usually right. One topic per question the audience actually asks.
5. Build the overview report for each topic. This is the dashboard page. Choose the summary cards that correspond to your KPIs, and remove the ones Google added by default that nobody asked for.
6. Drag the reports into place. Google's instructions are to "drag a detail report and an overview report under each topic." The overview report is the landing page; the detail reports are where people go to dig in.
7. Save, then publish. A saved collection is not visible to anyone else until you publish it. Open the collection's More menu and select Publish.

That last step catches people out constantly. You build the thing, you walk away, and nobody else can see it because it was only ever saved.

Dashboards show you traffic. Audits show you why it is not growing. Get a prioritised list of fixes for your site, free. Request yours.

Which KPIs Belong on It

A dashboard with twenty numbers on it is a report. A dashboard has four to six.

The discipline is simple: every card has to be a number somebody would change their behaviour over. If nobody would act differently at 4% than at 6%, it is context, not a KPI.

For most sites the top row looks something like this.

• Sessions by default channel group — where the traffic actually comes from, not just how much of it there is
• Engagement rate — GA4's quality signal, and the metric that replaced bounce rate as the default
• Key events — formerly conversions, and the only number tied to business outcome
• Key event rate — the efficiency number that stops a traffic spike from reading as a win
• Average engagement time — the depth signal that catches thin content

Resist the urge to add revenue if you do not have ecommerce tracking configured properly. A revenue card that reads zero teaches your audience to distrust the whole dashboard.

Pick a Comparison, Not Just a Number

A KPI without a comparison is trivia. Set the date range to a period that matches the decision cycle, and turn on the previous-period comparison.

Weekly dashboards compare to the previous week. Monthly ones compare year over year, because seasonality will otherwise read as performance.

One Collection Per Audience

The temptation is to build one dashboard for everyone. It never works, because an executive and a content editor want different numbers at different grain.

Build separate collections. The limits are generous enough to allow it, and a focused collection gets opened far more often than a comprehensive one.

The Limits You Will Hit

GA4's Library has hard ceilings, and they are published. Knowing them before you design saves a rebuild.

• Each property can have up to 7 collections
• A collection can have up to 5 topics
• Each topic can have up to 10 reports
• A topic can have only a single overview report

Those numbers are comfortable for most organisations and tight for agencies managing many stakeholders in one property.

There is also an ordering constraint that surprises people. Collections appear in the left navigation alphabetically by name, and that order cannot be changed.

If you want a specific collection at the top, you name it to sort there. That is the only lever you have.

Your competitors rank for terms you have never checked. A free audit shows the gap in one pass. Start the audit.

Linked and Unlinked Collections

This one is permanent, so read it before you click.

Collections created from a template are linked by default, which means Google keeps updating them — adding or removing reports as the product changes.

Collections created from scratch are unlinked by default. You own them entirely, and nothing changes underneath you.

You can unlink a linked collection. You cannot relink it afterwards. Google's documentation is explicit: "Unlinked objects cannot be linked in the future."

For a KPI dashboard you almost always want unlinked. A dashboard that silently gains a report because Google shipped a feature is not a dashboard anybody can trust.

It Is Not a Blank Canvas

The deeper limitation is conceptual. The Library rearranges GA4's reports; it does not let you draw whatever you like.

You cannot place a card next to a chart at an arbitrary position. You cannot blend GA4 data with a CRM export. You cannot write a custom calculated metric and drop it on the page.

If your definition of a KPI dashboard includes any of those, the Library is the wrong tool and no amount of configuring will change that.

GA4 Library vs the Alternatives

Three surfaces can produce something dashboard-shaped from GA4 data, and they fail in different directions.

The report Library wins on access and cost. It lives inside GA4, so there is no second login, no sharing step, and no data freshness question. Use it when the audience already has GA4 access and the KPIs are standard GA4 metrics. This is the right default for most teams.

Explorations win on depth. Free-form exploration, funnels, path analysis and segment overlap all live here, and none of them are available in the Library. But an Exploration is an analysis surface, not a dashboard — it is built for one person answering one question, and it does not sit in the navigation for a team to check each Monday.

Looker Studio wins on everything the Library cannot do. Arbitrary layout, blended sources, calculated fields, scheduled email delivery, and sharing with people who have no GA4 account at all. The cost is a second tool to maintain and a connector that can break quietly.

The honest rule: start with the Library. Move to Looker Studio the first time you genuinely need to blend GA4 with a second source, and not before.

Which pages actually earn your organic traffic? A free audit ranks them and shows what is holding the rest back. Get a free audit.

When to Skip GA4 Entirely

If your KPI dashboard is mostly about search performance, GA4 is the wrong starting point. It cannot see impressions, average position, or the queries people typed.

That data lives in Search Console, and the integration between the two is the piece most reporting setups are missing.

Frequently Asked Questions

Can I still use the old Universal Analytics dashboards? No. Universal Analytics stopped processing data and its dashboards went with it. The Library is the replacement.

Why can't I see the Library link? You are almost certainly a Viewer. The Library requires the Editor or Administrator role on the property.

Does publishing a collection share it outside my organisation? No. Publishing makes it visible in the left navigation for people who already have access to that GA4 property. It is not a public link.

Can I copy a collection to another property? Not natively. You rebuild it, which is one more argument for keeping the structure simple enough to rebuild quickly.

Final Thoughts

The hardest part of building a KPI dashboard in GA4 is unlearning the expectation of a drag-and-drop canvas. Once you accept that the Library is a navigation editor and the overview report is the dashboard, the build is straightforward and the result holds up.

Keep it to four or five cards. Publish it. Unlink it so Google cannot change it underneath you. Name it so it sorts where you want it.

And if the questions your dashboard is meant to answer are mostly about organic search, pair it with Search Console rather than stretching GA4 to cover ground it cannot see — our guide to building a Google Analytics SEO report walks through that integration in detail.

A dashboard nobody opens is worse than no dashboard, because it creates the impression that someone is watching. Build the small one people actually check.