Google Analytics added a report type called Dashboards on September 9, 2026, a grid-based canvas with six chart types, a ceiling of 15 cards on standard properties and 30 on premium ones, and no support for segments, the API or card-level comparisons.

In Short

Google Analytics now lets people build a single page of charts by dragging metrics onto a grid, instead of clicking between separate reports to find each number. It matters because the platform has spent nine months adding data and until now offered no native place to assemble that data into one view without a second tool. What changes is where a summary page lives: inside Analytics itself, shared with everyone on the property, and capped at 15 charts unless the account is a paid one.

What arrived on September 9

The release was documented in the "What's new in Google Analytics" Help Center page, the same surface that has carried nearly every Analytics product change this year. No blog post accompanied it. No press release was issued. According to the release note, "Dashboards are now available in Google Analytics. Dashboards are a highly flexible way to help businesses view their KPIs on a single report."

The same note describes the build experience in one sentence: "This launch features enhanced UI capabilities, such as intuitive data visualization creation, drag-and-drop functionality, and new report visualizations."

A separate Help Center article, titled "About Google Analytics dashboard", carries the detail. The mismatch between the plural in the release note and the singular in the documentation title is the first small inconsistency in the material, and it is not explained anywhere in either page.

According to that documentation, the feature rests on a grid. "The dashboard is built on a grid system that allows for flexible card placement and resizing," the article states. Charts are created by dragging dimensions and metrics onto the canvas rather than by configuring a report definition first. Placement, alignment and custom dimensions are handled manually. A right-hand panel holds the formatting controls for whichever visualisation is selected.

Google lists four characteristics as the headline features. The first is a consolidated single-page view of cross-functional metrics, which the documentation frames as removing the need to move between multiple reports to assemble a set of core business figures. The second is the grid canvas. The third is drag-and-drop chart creation. The fourth is publication straight to the left navigation at save time, bypassing the report library that has governed custom report placement in the platform since the Universal Analytics era.

Six chart types, and what each supports

The documentation enumerates six supported visualisations, each with its own constraints.

Score cards display high-level figures and can carry percentage changes when a date comparison is applied. Table chartssupport shaded bar graphs and pagination. Line charts plot metrics over time at daily, weekly or monthly granularity. Bar charts render horizontally or vertically for dimension comparison. Donut charts show part-to-whole relationships. Funnel charts track conversion steps and identify drop-off points, which places a native conversion funnel visual inside the standard Reports section rather than inside Explorations.

The list is short by the standards of the category. Data Studio, the product Google renamed from Looker Studio on April 11, 2026, counts 36 chart types and more than 600 partner connectors. Scatter plots, geo maps, treemaps, gauges and waterfall charts are absent from the Analytics set. So are pivot tables, which remain an Explorations capability.

The limits section is the news

Three constraints are documented, and each one narrows the use case in a way that matters operationally.

The first is volume. "Standard properties are limited to a maximum of 15 cards per dashboard, while premium properties support up to 30 cards," according to the documentation. Premium here means Analytics 360, the paid tier that received the Meridian marketing mix model integration at Google Marketing Live on May 20, 2026. The card ceiling is therefore a paywall as much as a technical limit, and it is the first time this year that a reporting feature inside Analytics has been tiered by volume rather than by availability.

The second is visibility. "All published dashboards are shared with the property," the documentation states. There is no private or personal dashboard. A board built by one analyst for one client stakeholder appears in the left navigation for every user with property access. For an agency running a single property across several internal teams, or for an in-house team where finance, merchandising and performance marketing each maintain separate views, the shared namespace is a governance question rather than a formatting preference.

The third is scope. "API support, segments, and card-level comparisons are currently not supported," according to the documentation. Each of those three absences removes a workflow.

No API support means a dashboard cannot be read, written or replicated programmatically. That sits awkwardly against the direction of travel elsewhere in the product: on May 4, 2026, Google opened cross-channel conversion reporting to the Data API in alpha, closing a gap between what analysts could see in the interface and what developers could retrieve in code. Dashboards reopen a version of that gap in the opposite direction, since the assembled view exists only in the interface.

No segment support is the sharper omission for analysts. Segments are the mechanism by which Explorations isolate a cohort, and their absence means a dashboard describes property-level totals filtered only by the dimensions placed on each chart. No card-level comparison means that while a score card can show a percentage change when a date comparison is applied at the report level, individual cards cannot each carry their own comparison basis.

Two roles can build. Editor or Administrator permissions are required to create and publish, while anyone with property access can view what has been published. The documentation also links to Google's cardinality article, an unstated signal that high-cardinality dimensions will degrade dashboard output the same way they degrade every other Analytics reporting surface.

What Google described in August, and what shipped

On August 10, 2026, Google added dashboards generated from a typed prompt, insight cards and peer benchmarking to Google Ads and Google Analytics, with the Dashboards capability listed as coming soon in Analytics. That announcement, published on the Google Ads and Commerce Blog by Josh Moser, Senior Director of Product Management, described dashboards in Google Ads that turn text into visualisations with automatically generated explanatory summaries. All four capabilities in that post were attributed to Gemini. The same announcement placed AI Overviews at the top of the Google Analytics homepage.

The September 9 release note and the accompanying documentation contain no reference to Gemini, to any generated summary, or to building a chart from a typed instruction. Both documents describe a manual builder operated by dragging fields onto a grid. Whether the shipped Dashboards feature is the delivery of the August commitment in a stripped form, a separate manual product, or an initial version to which the generative layer is added later, is not stated in either source document. Google did not publish rollout dates, geographic scope or language restrictions for the September release, which repeats the pattern of the August post.

That absence of scope detail carries weight because the preceding AI reporting features in this product line all arrived with explicit language limits. Ads Advisor and Analytics Advisor reached general availability only for English-language accounts in December 2025. Ask Advisor, the unified agent presented at Google Marketing Live on May 20, 2026, was global but English-only and in beta. A manual drag-and-drop builder has no language dependency, which is one reading of why no restriction was published.

A new surface in a platform that already had five

In October 2025, Google published a reporting playbook mapping five distinct reporting surfaces inside Analytics: Reports, Explore, Advertising, the Data API and the BigQuery export. The document existed because practitioners could not reliably determine which surface answered which question, and because approximation behaviour differs between them.

Dashboards adds a sixth. It sits inside Reports, alongside the overview reports and detail reports that have structured that section since the GA4 migration. Google previously attempted to solve the same summary-view problem with templates, releasing three preconfigured Reports snapshot layouts in April 2025 covering user behaviour, sales and revenue, and marketing performance. Those templates assembled existing summary cards defined in detail reports. Dashboards inverts the relationship: the chart is built directly from dimensions and metrics, with no detail report underneath it.

The overlap with Data Studio is the obvious commercial question, and neither document addresses it. Data Studio holds broad adoption in the search and analytics community precisely because Google Ads and Google Analytics connectors are available on its free tier, and it received cross-data-source filtering, component visibility controls and histogram charts on January 15, 2026. A 15-card dashboard with six chart types, no segments and no API does not displace that. It does remove the need to open a second product to answer a question that three charts would settle.

Nine months of releases behind it

The "What's new" page lists 14 release dates for 2026 before September 9: January 16, February 10, April 29, May 4, May 7, May 13, June 8, June 11, July 13, July 28, July 30, August 10 and August 11. Read together, they describe a year spent widening what enters the property and what the property can classify, rather than widening how the resulting data can be displayed.

A native AI Assistant channel arrived on May 13, 2026, automatically assigning the medium value "ai-assistant" to traffic from recognised chatbots including ChatGPT, Gemini and Claude. Google Business Profile linking followed on June 8, 2026, importing seven local interaction metrics on a rolling six-month window. The Source Group dimension arrived on June 11, 2026, consolidating fragmented source values such as facebook, fb and Meta-facebook into a single reporting entry, with built-in grouping for ChatGPT and Perplexity. AdMob linking moved natively into the Admin interface on July 13, 2026. Campaign data import began requiring a currency field on every cost upload on July 28, 2026, and a diagnostic for missing GBRAID and gad_ parameters arrived two days later. A campaign data import validation report shipped on August 10, 2026.

On August 11, 2026, Google replaced the fixed three-day engaged-view conversion window with any integer from 1 to 30 days and converted the six preset click-through options into any integer from 1 to 90 days, making lookback windowseditable per conversion action.

The release-notes document contains one further inconsistency. Cross-channel budgeting appears twice, first under January 16, 2026 and again under February 10, 2026, with identical wording in both entries, including the same beta eligibility caveat. The February 10 entry also covers Generated insights on the Home page, which summarises the top three data changes since a user's last visit. Nothing in the page explains the duplication, and no correction is noted.

Why it matters for the marketing community

A reporting layer determines which questions get asked. For practitioners who have spent two years exporting Analytics data into Data Studio to build a client-facing summary, an in-platform grid removes one hop in that chain for simple cases, at the cost of segments and programmatic access.

The governance implication is more immediate than the feature set. Shared-by-default publication means dashboard sprawl accrues to the property rather than to the individual, and the left navigation is the surface that absorbs it. Properties with multiple stakeholder groups inherit a naming discipline problem on day one. The 15-card ceiling caps how much of a reporting deck can migrate before a property hits the constraint, and the 30-card allowance on Analytics 360 sets a visible price on the difference.

The unresolved question is what Google intends the relationship between Dashboards and its generative reporting layer to be. Ask Advisor was positioned in May 2026 as a performance interpretation layer that connects campaign data from Google Ads with behavioural data from Analytics, so that marketers would not have to reconcile separate dashboards. Four months later, the company shipped a dashboard builder. Both directions can hold simultaneously, but the documentation published on September 9, 2026 makes no attempt to connect them.

Timeline

Summary

Who: Google, through the Google Analytics Help Center. The change affects Google Analytics property administrators, analysts, agencies and in-house marketing teams, with a distinction drawn between standard properties and premium Analytics 360 properties.

What: A report type called Dashboards, built on a grid canvas with drag-and-drop chart creation and six visualisation types: score cards, table charts, line charts, bar charts, donut charts and funnel charts. Standard properties are capped at 15 cards per dashboard and premium properties at 30. Editor or Administrator roles are required to create and publish; any user with property access can view published boards. API support, segments and card-level comparisons are not supported, and all published dashboards are shared with the property.

When: September 9, 2026, documented in the "What's new in Google Analytics" release notes and a companion Help Center article. No rollout dates, geographic scope or language restrictions were published.

Where: Inside the Reports section of the Google Analytics interface, with publication to the Report left navigation at save time rather than through the report library.

Why: Google frames the feature as consolidating cross-functional metrics into a single page so that core business figures can be read without moving between separate reports. The release closes a long-standing gap between Analytics reporting and external visualisation tools, while leaving segments, programmatic access and per-user privacy outside its scope.