Google Analytics has had its own dashboards since 9 September 2026: a single page of score cards and charts you build by dragging dimensions and metrics onto a grid, published into the left-hand navigation for everyone on the property.
For a lot of small businesses that's the report they always wanted and never had. Here's what it does, where it stops, and when Looker Studio still earns its keep.
What you get.
Six chart types: score cards, with a percentage change when you compare date ranges; tables with shaded bars and paging; line charts by day, week or month; bar charts; donut charts; and funnel charts for a sequence of steps. The canvas is a grid, and cards can be placed, aligned and resized by hand.
Creating one takes an Editor or Administrator role. Anyone with access to the property can view a published dashboard, which appears in the Reports navigation without a trip through the report library.
Where it stops.
Google lists the limits plainly. Fifteen cards per dashboard on a standard property, thirty on Analytics 360. No segments. No comparisons at card level. No API. And every published dashboard is shared with the whole property: there's no private dashboard, and no way to show one to someone who doesn't have access to GA4.
The bigger limit goes unstated: it only shows GA4 data. Google Ads cost is there if the accounts are linked. Meta, LinkedIn and Microsoft spend, the CRM pipeline, and anything that lives in a spreadsheet are not.
When it's enough.
A business whose questions are "how many people came, from where, and how many did the thing" is well served. One dashboard of eight cards covers it: sessions by channel, key events by channel, conversion rate, revenue or leads, top landing pages, a funnel of the main journey, new against returning, and devices.
That's the weekly check, in a tool that costs nothing extra, with no connector to break.
It also removes the usual reason dashboards go stale: nobody owns the Looker Studio file after the person who built it leaves. A dashboard inside the property belongs to the property.
When you still need Looker Studio.
- Blending. Cost from more than one ad platform, CRM stages, finance figures, anything that isn't GA4. Looker Studio joins sources; the GA4 dashboard doesn't.
- Audience. A client, a board or a franchisee who shouldn't have GA4 access. Scheduled email delivery. Your branding rather than Google's.
- Segments and comparisons. Cohorts side by side, a segment of paying customers, a comparison on every card.
- BigQuery. Anything that needs unsampled, stitched or historical data beyond what the interface will give you.
- Size. More than fifteen cards, or one view per department.
And one caution that applies to both. A dashboard is only as good as the tracking under it. A funnel chart built on broken events is a confident picture of the wrong thing, and it's harder to doubt once it has a chart.
What Marc recommends.
Start with the built-in dashboard, because it's free and it's where the data already lives. Build the eight-card version, publish it, and see what questions people ask when they look at it.
The first time the question is "why doesn't this match the CRM" or "what did the ad spend actually buy", you've found the point where a custom dashboard on blended data, or a BigQuery connection, pays for itself.
Before either, make sure the numbers underneath are right: that's what the GA4 mini audit is for.