Google Analytics Finally Has Dashboards Again

Google Analytics has launched Dashboards, confirmed in Google's own "What's new in Analytics" log with a date of September 9, 2026. Google describes them as "a highly flexible way to help businesses view their KPIs on a single report," with "enhanced UI capabilities, such as intuitive data visualization creation, drag-and-drop functionality, and new report visualizations."

For anyone who has been building GA4 reporting since 2020, the word "Dashboards" carries some history.

What you actually get

It's a grid-based canvas. You position, resize and align visualisations by hand, and you build charts by dragging dimensions and metrics straight onto the canvas rather than configuring a report definition first.

Six chart types are available: scorecards for headline KPIs, tables for detail, line charts for trends, bar charts for comparison, donut charts for breakdowns, and funnel charts for conversion steps and drop-off.

There's a hard ceiling on size — 15 cards per dashboard on a standard property, 30 on a premium one. Once published, a dashboard is shared with the property, and anyone with property access sees it in the Reports navigation. There's no per-dashboard permissioning described: publish it and everyone who can see the property can see it.

Why this matters more than a feature release usually does

The interesting question isn't what Dashboards do. It's what they displace.

A very large amount of client reporting currently lives in Looker Studio for one reason: GA4's native reporting was too rigid to answer "just show me these eight numbers on one screen." Looker Studio solved that, at the cost of a second tool, a connector, a refresh model and a whole category of problems where the dashboard disagrees with the interface it's pulling from.

A 15-card native dashboard doesn't replace a client-facing Looker Studio build with blended sources and branding. But it very plausibly replaces the internal one — the scrappy dashboard someone made so the team could stop clicking through four reports every morning. That's a real chunk of Looker Studio usage.

The funnel chart is the sharper detail. Funnel exploration has lived in the Explore section, which is where GA4 reporting goes to be powerful and impossible to hand to a client. A funnel visualisation on a shareable dashboard is a meaningfully different object.

The limits worth planning around

15 cards is a real constraint. It's enough for a focused view and not enough for the everything-dashboard people tend to build. That's arguably good design, but if your current reporting is a 40-widget Looker Studio page, this is not a port — it's a rewrite with an editorial decision attached.

Publishing is property-wide. If your property has stakeholders who should see different things, a shared canvas everyone can see is a consideration, not a feature.

Nothing here changes the data. Sampling, thresholding, attribution and the reporting identity settings all behave exactly as they did. A nicer chart of a thresholded number is still a thresholded number.

What I'd do

Rebuild one existing internal dashboard natively and compare. Not a client deliverable — pick the internal view your team actually opens, and see whether 15 cards covers it.

If it does, you've removed a connector and a sync from your stack, and the numbers now come from the same place people go to argue about them. If it doesn't, you've learned where the ceiling is for about twenty minutes of work.

Either way, don't migrate client reporting on day one. Native GA features arrive incrementally, and the version of this that exists in six months will be a different product to the one that launched last Tuesday.

Sources

• Google Analytics Help: What's new in Google Analytics