Google Analytics has dashboards again. On 9 September Google added a short entry to its “What’s new in Google Analytics” page: “Dashboards are now available in Google Analytics. Dashboards are a highly flexible way to help businesses view their KPIs on a single report.” The entry points to a new help article, and Search Engine Land and Search Engine Roundtable both covered the launch on 11 September.
For anyone who moved from Universal Analytics to GA4 and lost the one-page overview along the way, this is the feature they have been asking for since 2023. It arrives with a clear set of capabilities, a clear set of limits, and one open question about the AI version Google promised a month earlier.
How we got here
Universal Analytics had dashboards for years. Google’s own legacy documentation still describes them: collections of widgets you could arrange to watch the numbers that mattered without opening a dozen reports. GA4 launched without an equivalent. Instead it offered the Reports library, where an editor could customise the standard reports and their navigation, and Explorations, a separate analysis workspace for funnels, paths and free-form tables. Neither gave a business owner a single page of scorecards to open on a Monday morning, which is why so many teams ended up rebuilding that page in Looker Studio or a third-party tool.
The first public signal that this was changing came on 10 August. In a post on the Google Ads & Commerce Blog titled “Evolve your marketing with new AI tools”, Josh Moser, Senior Director of Product Management, announced dashboards in Google Ads that turn text prompts into visualisations with a generated summary explaining the data. According to PPC Land’s report on that announcement, the same capability was described as “coming soon” for Google Analytics rather than available there immediately. The 9 September entry is that arrival.
What the feature does
Google’s help article describes dashboards as a way to “create custom visualizations to quickly pull actionable insights from your Google Analytics data, all in a single, consolidated page.” The mechanics, as documented by Google and confirmed by Search Engine Land:
- A grid canvas. Charts are placed on a grid, and you can position, resize and align them by hand rather than accepting a fixed layout.
- Drag-and-drop building. You create a chart by dragging dimensions and metrics directly onto the canvas, then adjusting it, instead of configuring each report separately.
- Six visualisation types. Scorecards for headline KPIs, tables for detail, line charts for trends, bar charts (horizontal or vertical) for comparisons, donut charts for breakdowns, and funnel charts for conversion steps and drop-off.
- Publishing into Reports. When you save a dashboard you can publish it directly into the left navigation of Reports, without going through the Reports library first.
The path is Reports, then the ”+ Create” button, then Dashboard. Creating and publishing requires the Editor or Administrator role on the property; once a dashboard is published, anyone with access to the property can open it from the navigation.
What the feature does not do
The help article is equally explicit about the boundaries, and they matter for anyone deciding whether to retire an external reporting tool.
- Card limits. A dashboard in a standard property holds at most 15 cards. Premium (Google Analytics 360) properties get 30.
- No API support. Dashboards cannot be created, read or exported through the Google Analytics API, so they live inside the interface.
- No segments. You cannot restrict a dashboard, or a card on it, to a segment of users or sessions the way you can in Explorations.
- No card-level comparisons. Comparisons apply to the whole dashboard, not to an individual chart.
- Property-wide sharing. All published dashboards are shared with everyone who has access to the property. There is no per-user or per-team dashboard, and no private draft that only its author can see once it is published.
There is also a gap between what Google promised in August and what the September documentation describes. The Google Ads version was announced as prompt-driven: type a question, get a chart and an explanation. The Google Analytics help article describes drag-and-drop construction and says nothing about text prompts or generated summaries. Whether the prompt-based building arrives in Analytics later, or whether the drag-and-drop canvas is the Analytics version, Google has not said. We would treat the feature as a manual dashboard builder until the documentation says otherwise.
What it means for your business
Build the Monday-morning page first. The single most useful dashboard for an owner is not clever. It is the handful of numbers you already ask for by email: sessions by channel, leads or purchases, conversion rate, revenue if you sell online, and one funnel from landing page to enquiry. Fifteen cards is enough for that page, and it is deliberately not enough for everything else. Use the limit as an editor: if a card does not change a decision, it does not earn a slot.
Decide what stays in Looker Studio. Native dashboards remove the need for an external tool in one case only: an internal overview of Google Analytics data, seen by people who already have property access. They do not replace external reporting where any of these apply: you blend Analytics with ad spend, CRM or sales data; you need segments; you need a client-facing or board-facing report for people without property access; or you need an export. Our reading is that the native dashboard is the daily glance and Looker Studio remains the monthly report.
Mind the sharing model. Because every published dashboard is visible to everyone on the property, a dashboard is a shared artefact, not a personal one. Agree who owns each dashboard and who may edit it, and give the rest of the team Viewer or Analyst access. Otherwise the navigation fills with near-duplicate pages within a month.
Check the numbers before you trust the page. A dashboard is only a new way to display what Analytics already records. If your conversion events are misfiring, if your landing pages are not tagged, or if enquiries arrive by phone and never reach Analytics at all, the scorecards will be confidently wrong. The reconciliation between what the platform counts and what the CRM records is the part that no dashboard automates, and it is where the measurement work in our CRM and analytics projects begins: from the enquiry backwards to the source, not from the chart forwards.
Use the funnel card for one question. The funnel visualisation is the most valuable of the six types for a service business, because it shows where visitors stop between arriving and asking. Build one funnel, from landing page to form view to submission, and review it weekly. When a step starts leaking, that is a website or content problem to fix, not a reporting problem to redesign.
Our view is that Google has shipped a solid, deliberately limited feature: it answers the request that GA4 users have made most often, and it stops well short of an analysis tool. For most small and mid-sized businesses that is the right scope. Build the one page, keep it honest, and keep the heavier reporting where it already lives.
