Google Analytics dashboard: how to build one in GA4 and when to use Looker Studio

A Google Analytics dashboard in GA4 is a single page of charts that an Editor or Administrator builds under Reports, then publishes to the left navigation for everyone who has access to the property. It suits a one-page KPI view of GA4 data; when you need cost data from other platforms, viewers outside the property, or more than one page of charts, Looker Studio is the better tool.

Google Analytics has offered several ways to put numbers on one screen over the years, and the overlap confuses people. GA4 now has native dashboards, customisable overview reports inside Reports library collections, explorations, and the separate Looker Studio product. Each one has a different builder, different permissions and different limits. This guide covers how to build a dashboard in GA4, how it compares with the other three options, which cards earn a place on a marketing dashboard, and the point at which moving to Looker Studio makes sense.

What a Google Analytics dashboard is in GA4

The GA4 dashboard is a grid canvas that lives in the Reports section. Each chart on the grid is a card. You place cards by dragging them onto the canvas, then drag dimensions and metrics onto each card, and you can resize and align cards freely. When you save, you can publish the dashboard straight to the Reports left navigation without going through the Library.

Google's help documentation lists six chart types:

• Score cards for headline KPIs. They show a percentage change only when a date comparison is applied.
• Table charts for detailed rows, with shaded bars and pagination.
• Line charts for metrics over time at daily, weekly or monthly granularity.
• Bar charts, horizontal or vertical, for comparing dimension values.
• Donut charts for showing how parts contribute to a whole.
• Funnel charts for conversion steps and drop-off points.

Standard properties can hold up to 15 cards per dashboard. Premium properties can hold up to 30. Google also states that API support, segments and card-level comparisons are not currently supported.

How to build a dashboard in GA4, step by step

You need the Editor or Administrator role on the property. With a Viewer or Analyst role, the create option will not be there, and you will need to ask a property admin for access.

1. Sign in to Google Analytics and select the property.
2. Click Reports in the left menu.
3. Click + Create at the top of the Reports navigation and choose Dashboard. To change an existing dashboard, open it from the left navigation and click the Edit icon.
4. Drag a visualisation type, such as a score card or a line chart, onto the canvas.
5. Drag the dimensions and metrics you want onto that card.
6. Use the right-hand panel to customise the card, including its title and settings.
7. Repeat for each card, keeping an eye on the card count.
8. Click Save, then Publish to add the dashboard to the Reports left navigation.

Plan the layout before you drag anything

The 15-card ceiling on standard properties forces choices. Write the questions the dashboard must answer on paper first, one card per question, and drop anything that is not tied to a decision. A card that nobody acts on still costs a slot that could hold a funnel or a landing-page table.

Score cards and date comparisons

Because score cards show a percentage change only when a date comparison is applied, a dashboard viewed without a comparison reads as a row of flat totals. Tell viewers to set the comparison range in the date picker, or the headline row will hide whether things got better or worse.

GA4 dashboards vs Reports library collections vs explorations vs Looker Studio

These four tools overlap, but each one fits a different job. The table sets out who can build each one, who can see it, and what it is best at.

When a Reports library collection is enough

Collections change the standard Reports menu itself. Each property can have up to 7 collections, a collection can have up to 5 topics, and each topic can have up to 10 reports. Each topic can have one overview report, which acts as that topic's summary page. Saving a collection does not make it visible: you must publish it from the Library before it appears in the left navigation. Use collections when the problem is that the default menu does not match how your team thinks, and dashboards when the problem is that the KPIs are scattered across many reports.

When an exploration is the right tool

Explorations are for analysis, not monitoring. They support segments, which dashboards currently do not, and they start private. Each user can create up to 200 explorations per property, and a property can hold up to 500 shared explorations. One thing to remember: the GA4 data retention setting, which is 2 or 14 months on standard properties, applies to explorations and funnel reports, not to standard aggregated reports. A year-on-year exploration on a property set to 2 months will come back with missing data.

Which cards and metrics to put on a marketing dashboard

A marketing dashboard should answer three questions: where visitors came from, what they did, and whether that turned into business. The layout below is illustrative, sized to fit inside the 15-card limit with room left for later additions.

• Score cards (4): sessions, engaged sessions, key events, and total revenue for e-commerce or a lead key event for lead generation.
• Line chart (1): sessions and key events by day, so a tracking break shows up as a sudden flat line.
• Bar chart (1): sessions by session default channel group.
• Table (2): landing pages with sessions, engagement rate and key events; and session source/medium with key events.
• Funnel chart (1): the main conversion path, for example product view, add to cart, begin checkout, purchase.
• Donut chart (1): device category share.

That illustrative layout uses 10 cards. Keep the remaining slots for a campaign table or a second funnel rather than filling them on day one.

Metrics to be careful with

Key events are only as good as the event setup behind them. If a form-submit key event fires on page load, every card that uses it is wrong at once. Check events in DebugView before you build cards on top of them. Revenue cards need the purchase event to send a value and currency. Engagement rate is often a more useful health signal than bounce rate because GA4 defines the two as complements, so showing both wastes a card.

Sharing and permissions

GA4 dashboards have no private mode. Google's documentation says all published dashboards are shared with the property, and anyone with property access can view them from Reports in the left menu. In practice:

• Viewers and Analysts can read every published dashboard but cannot build or edit one.
• An Editor's draft experiments become visible to the whole property once published, so keep test dashboards unpublished or remove them.
• Someone without any access to the GA4 property cannot see a GA4 dashboard at all. To show data to a board member, a client or an outside partner without adding them to the property, you need Looker Studio.

Looker Studio sharing works through Google accounts, similar to Google Docs. The key setting is the data source's credentials. With owner's credentials, viewers see the data using the owner's authorisation, so they do not need their own GA4 access. With viewer's credentials, each viewer must have access to the underlying GA4 property, or the charts stay empty for them. Choosing owner's credentials and then sharing the report link widely exposes the data to everyone with the link, so check the sharing settings before sending it out.

Limits to know before you start

• Card count: 15 per dashboard on standard properties, 30 on premium.
• Not supported yet: API access, segments and card-level comparisons.
• Granularity: line charts go down to daily. Hourly patterns need a different report.
• Chart types: the six listed above. No maps, scatter plots or pivot tables in the documented list.
• Single source: the dashboard shows GA4 data. Spend from Meta, TikTok or LINE, CRM deal values and offline sales are not there unless they already reach GA4.
• Custom reports: each property can have up to 150 custom reports, which matters if a team builds many library reports alongside dashboards.

When to move to Looker Studio

Stay in GA4 while the dashboard is one page of GA4 data for people who already have property access. Move to Looker Studio when any of the following becomes true:

• You need cost or results from other ad platforms next to GA4 sessions and key events.
• Viewers do not have, and should not get, GA4 property access.
• The report needs more than one page, or more cards than the GA4 limit allows.
• You need a branded, scheduled or client-facing report.
• You need to combine sources with a blend, such as GA4 sessions joined to a CRM export on a shared date or campaign key.

Looker Studio has its own costs. Its GA4 connector draws on the Google Analytics Data API, which has quotas. A report with many charts, many viewers or long date ranges can hit those quotas and show errors instead of numbers, so keep chart counts sensible and avoid needlessly wide date ranges on busy pages.

Common mistakes and what each one costs

• Building cards on broken events. Every chart inherits the error, and the dashboard makes it look official. Audit events first.
• Publishing experiments. Because published dashboards are property-wide, a half-finished test dashboard ends up in everyone's navigation and people quote its numbers.
• Using an exploration as the team dashboard. It stays private until shared and is bound by the data retention window, so long comparisons break.
• Using owner's credentials in Looker Studio by default. Fast to set up, but anyone the report reaches sees the data.
• Filling all 15 slots. No room is left for the next question, and the page becomes hard to scan.

What this means for Thai businesses

A few settings matter more on Thai sites. Check that the property's reporting time zone is Bangkok and the currency is Thai baht under Admin, property details. A property left on another time zone shifts daily totals, so a daily line chart will not match the sales system's daily figures. Thai page titles are often long and similar to each other, so a landing-page table reads better with page path than page title.

Traffic from LINE needs attention. Links shared inside LINE chats and LINE Official Account broadcasts can open in an in-app browser, and without UTM parameters that traffic may end up as direct or a vague referral. Tag every LINE link with utm_source and utm_medium so the channel bar chart reflects reality. Shopee and Lazada sales happen on the marketplace, not on your site, so GA4 will not see them. If marketplace sales are a large part of the business, that is a clear signal the dashboard belongs in Looker Studio with marketplace data added.

Consent also shapes the numbers. Under Thailand's PDPA, sites commonly run a consent banner, and with Consent Mode the share of visitors who decline affects what GA4 records. A sudden change in sessions after a banner update may be a consent change rather than a traffic change.

FAQ

Is there a built-in Google Analytics dashboard in GA4?

Yes, GA4 has a native dashboard builder under Reports, opened from + Create and then Dashboard. Editors and Administrators can build it, and published dashboards are visible to everyone with access to the property.

How many cards can a GA4 dashboard have?

A standard GA4 property allows up to 15 cards per dashboard, and premium properties allow up to 30. Plan one card per question to stay inside the limit.

Can I share a GA4 dashboard with someone who has no GA4 access?

No, a GA4 dashboard is only visible to people with access to the property. To share data with people outside the property, build the report in Looker Studio and choose the data credentials setting carefully.

Should I use a GA4 dashboard or Looker Studio?

Use a GA4 dashboard for a single page of GA4 data viewed by property users, and Looker Studio when you need other data sources, more pages or outside viewers. The two also work together: GA4 for daily checks, Looker Studio for monthly reporting.

Why are segments missing from my GA4 dashboard?

Segments are not currently supported on GA4 dashboards, according to Google's documentation. Use an exploration for segment analysis, or Looker Studio filters for a recurring view.

A dashboard is only as reliable as the tracking underneath it. If your GA4 events, key events or consent setup need checking before you build on them, the Google Analytics 4 setup service covers the measurement plan, event tracking and dashboards. For paid traffic, linked Google Ads management keeps campaign data consistent between the two platforms, and an SEO audit can confirm that the landing pages your dashboard reports on are indexed and healthy.