Marketing2026-10-07

Google Analytics Dashboards for Service Businesses: A Practical KPI Setup

Google Analytics launched native Dashboards in September 2026. Build a simple service-business KPI view for traffic, enquiries, bookings, landing pages, devices, and local actions.

Overview

Google Analytics added native Dashboards on September 9, 2026.

The new dashboard builder lets you create a single KPI page with drag-and-drop visualizations directly inside Google Analytics. For a small service business, that is useful because the owner often does not need a forty-chart reporting system.

They need a page that answers a few practical questions:

A good dashboard does not try to answer everything.

It makes the most important changes visible quickly, then sends you to deeper reports when something needs investigation.

Are the right people reaching the website?
Where did they come from?
Which landing pages are producing action?
Are people starting and completing the booking or enquiry journey?
Are local Google interactions contributing?
Did those website actions become real customers?

Quick answer

Google's new Analytics Dashboard feature supports:

Google currently documents these launch limits:

For most service businesses, the 15-card limit is not a problem.

It is a useful discipline.

a single-page KPI view;
a grid-based canvas;
drag-and-drop dimensions and metrics;
scorecards;
tables;
line charts;
bar charts;
donut charts;
funnel charts;
direct publication into the Reports left navigation.
standard properties: up to 15 cards per dashboard;
premium properties: up to 30 cards;
Editor or Administrator role required to create and publish;
published dashboards are shared with the property;
API support is not currently supported;
segments are not currently supported;
card-level comparisons are not currently supported.

What launched on September 9, 2026

Google describes Dashboards as a flexible way to bring important business KPIs into one report.

The new builder lives in the Reports area.

A user with the right permissions can:

The main difference from jumping between separate standard reports is that the owner can assemble a small decision surface around the questions the business actually asks every week.

open Reports;
choose + Create;
select Dashboard;
drag visualizations onto the canvas;
drag dimensions and metrics onto those visualizations;
customize each visualization;
save;
publish the dashboard into the Reports navigation.

Dashboard vs standard reports vs Explorations vs Looker Studio

The new dashboard is useful, but it does not replace every reporting tool.

Use a Dashboard when

You want:

a small set of recurring KPIs;
quick weekly checks;
one view for owners or managers;
a funnel snapshot;
a few acquisition and landing-page breakdowns.

Use standard Reports when

You need:

a broader built-in report;
more rows and dimensions;
a closer look at a particular acquisition or engagement question.

Use Explorations when

You need:

deeper analysis;
flexible funnels;
path analysis;
more advanced slicing;
exploratory work that does not belong on the weekly owner dashboard.

Use Looker Studio or another reporting layer when

You need:

Do not ask the native dashboard to become something it is not.

several data sources in one report;
highly customized presentation;
client-facing reporting;
more complex calculated fields;
a reporting model that goes beyond current native Dashboard limits.

The service-business dashboard should answer seven questions

Before adding any chart, write down the questions the dashboard needs to answer.

A useful owner dashboard can usually stay focused on these seven.

1. How much useful website activity are we getting?

Traffic volume provides context.

Useful metrics may include:

Do not make "more traffic" the goal by itself.

A hundred relevant visits can be more valuable than a thousand irrelevant visits.

users or active users;
sessions;
engaged sessions.

2. Where are visitors coming from?

A source or channel view helps explain sudden changes.

Useful breakdowns can include:

Google added a dedicated AI Assistant channel in 2026, so service businesses can now watch referral traffic from recognized AI assistants without inventing manual channel rules for every source.

Organic Search;
Paid Search;
Direct;
Referral;
Organic Social;
Email;
AI Assistant, where it appears in your property;
other configured channels.

3. Which landing pages are receiving the traffic?

Landing pages connect acquisition to the website experience.

A campaign can be healthy while one page is weak.

A useful landing-page table can expose:

If the page is commercially important, compare it with a strong service-page structure.

a service page getting traffic but no meaningful actions;
an old page still receiving paid traffic;
a blog or guide bringing discovery traffic;
the homepage doing too much work because service pages are underused.

4. Are people taking the next step?

For a service business, the next step is often:

Only put an event on the owner dashboard if the event is configured reliably.

A dashboard cannot repair weak tracking.

form submission;
booking start;
booking completion;
click to call;
quote request;
consultation request.

5. Where does the booking funnel leak?

If your property tracks the relevant booking steps, a funnel chart can be one of the most useful cards.

For example:

service page → booking start → time selected → booking complete

The exact events depend on the website and booking setup.

Do not invent a funnel step simply to fill the chart.

The online-booking guide can help define what a clean booking journey should look like operationally.

6. Are device or location patterns hiding a problem?

A mobile-vs-desktop breakdown can reveal a broken mobile form.

A location breakdown can reveal traffic from places the business does not serve.

Use these as diagnostic cards, not vanity charts.

7. Did website actions become business outcomes?

Google Analytics is strongest at describing website and attributed marketing behavior.

It does not automatically know every later business outcome.

Pair dashboard data with CRM or booking outcomes such as:

That prevents a common reporting mistake: calling every tracked website conversion "revenue."

qualified lead;
booked appointment;
attended visit;
completed job;
paid invoice;
repeat client.

A 12-card dashboard template

A standard property allows up to 15 cards, but you do not need to use all 15.

This 12-card template leaves room to add one or two business-specific metrics later.

This is a template, not a rule.

A home-service business may care more about calls.

A photography studio may care more about consultation bookings.

A salon may care more about completed online appointments.

A professional-services firm may care more about qualified enquiry submissions.

#	Card	Visualization	Question
1	Users or active users	Scorecard	How much audience activity did we have?
2	Sessions	Scorecard	How many visits occurred?
3	Primary key event or conversion	Scorecard	How many meaningful actions occurred?
4	Booking completions or qualified enquiries	Scorecard	Did the main commercial action happen?
5	Users/sessions over time	Line chart	Is traffic trending up or down?
6	Key events/conversions over time	Line chart	Are outcomes moving with traffic?
7	Channel or source group	Bar chart	Where is traffic coming from?
8	Landing pages	Table	Which pages start the journey?
9	Device category	Donut or bar chart	Is one device underperforming?
10	Geographic area	Table or bar chart	Are we reaching relevant locations?
11	Booking/enquiry funnel	Funnel chart	Where is the journey leaking?
12	Optional local/GBP action card	Scorecard or table	Are Google local interactions contributing?

Card 1: users or active users

This is context, not success.

If users rise 50% while bookings stay flat, the dashboard should make that visible.

That can trigger questions such as:

Traffic only becomes useful when paired with an outcome card.

Did a broad informational page get more traffic?
Did paid campaigns expand?
Did a social post create low-intent visits?
Did tracking change?
Did mobile conversion break?

Card 2: sessions

Sessions help show how often the website is being visited.

A repeat customer may create several sessions, which is one reason sessions and users answer different questions.

Do not obsess over the difference on a weekly owner dashboard.

Use both only when the distinction is useful for the business.

Card 3: the primary commercial event

Choose one event that represents the website action the owner cares about most.

Examples:

Avoid making a weak interaction the primary success card.

Examples of weak owner-level goals include:

Those can be useful diagnostic events, but they are rarely the final business outcome.

booking complete;
quote request submitted;
consultation request submitted;
contact form successfully submitted.
page view;
scroll;
button hover;
form started but not submitted.

Card 4: booking completions or qualified enquiries

If the property tracks a stronger outcome than the generic conversion count, show it separately.

For example:

That immediately tells the owner that "93 conversions" does not mean 93 customers.

If qualified-lead status lives only in the CRM, keep it in the CRM or reconcile it during the weekly review rather than pretending Google Analytics knows it automatically.

all tracked key events: 93;
completed bookings: 21.

Cards 5 and 6: traffic and outcomes over time

Two line charts can reveal whether traffic and outcomes move together.

Healthy pattern

Traffic rises and meaningful actions rise proportionally.

Possible problem

Traffic rises while booking completions fall.

That can signal:

The dashboard should help you notice the pattern. It does not diagnose the cause by itself.

worse traffic quality;
a broken form;
slower mobile experience;
a pricing or availability issue;
a campaign change;
seasonality.

Card 7: acquisition source

Use a channel or source view to answer:

Where did the visit begin?

Depending on your configuration, you may use dimensions such as source, medium, channel group, or source group.

Keep the chart readable.

A business owner generally does not need fifty tiny source rows on the first screen.

Group the big sources, then investigate smaller sources in the underlying reports when needed.

Card 8: landing pages

A landing-page table is one of the highest-value website cards.

Suggested columns include:

Look for pages with:

This is where analytics becomes website work.

landing page;
users or sessions;
meaningful event count;
booking or enquiry count where available.
high traffic and weak action;
low traffic and strong action;
sudden traffic loss;
unexpected paid traffic;
outdated offers.

Card 9: device category

Mobile matters because many service-business customers search while away from a desk.

A device card can expose:

If mobile performance looks suspicious, test the actual booking or enquiry path on a real phone.

Do not conclude "mobile users are worse" until you have ruled out a broken mobile experience.

mobile traffic is high but booking is weak;
desktop converts well but has little volume;
tablet traffic is negligible.

Card 10: location

A location card can help a local business detect geographic mismatch.

For example, a studio may serve Kraków but suddenly receive paid traffic from another region.

The dashboard can surface the symptom.

Then check:

Do not use Google Analytics location as a perfect representation of a person's physical address. Treat it as a directional reporting dimension.

paid campaign geography;
local SEO visibility;
referrals;
service-area language;
spam or bot patterns.

Card 11: booking or enquiry funnel

Google's new Dashboard supports funnel charts.

That is especially useful for service businesses with a multi-step booking flow.

A useful funnel might be:

Another might be:

The value is not the funnel's beauty.

The value is finding the biggest drop.

service page viewed;
booking started;
date/time step reached;
booking completed.
landing page;
quote form started;
quote form submitted;
thank-you page.

Example

The biggest drop is between page visit and booking start.

That suggests a different investigation than a funnel where 120 people start and only 20 complete.

500 service-page visits
120 booking starts
75 time selections
68 booking completions

Card 12: Google Business Profile metrics, if available in the Dashboard builder

Google Analytics added a native Google Business Profile integration in June 2026.

When a profile is linked, Google says Analytics can report GBP metrics such as:

Google currently documents a rolling six-month window for those GBP metrics.

Because Google documents the GBP collection separately from the new Dashboard feature, first check whether the Dashboard builder in your property exposes the GBP metric you want. If it does, a local-action card can be useful. If it does not, keep the GBP check in the dedicated Business Profile reports instead of forcing it into the dashboard.

This Dashboard Guide is about using the KPI view. The separate connection workflow belongs in the Google Business Profile integration setup.

interactions;
calls;
bookings;
direction requests;
website clicks;
messages;
menus.

Do not fill all 15 cards because the limit exists

A dashboard is not a storage locker.

Every additional card competes for attention.

Before adding a card, ask:

If the answer is no, leave it out.

Does someone review this every week?
Does a change trigger a decision?
Is the metric configured reliably?
Is there another card already answering the same question?

Use the right visualization

Google currently supports six visualization types.

Scorecard

Best for:

Examples:

one KPI;
one current total;
percentage change where useful.
bookings;
enquiries;
users.

Table

Best for:

landing pages;
source/medium;
cities;
campaigns.

Line chart

Best for:

traffic trend;
conversions over time;
weekly or monthly patterns.

Bar chart

Best for:

channel comparison;
device comparison;
top locations.

Donut chart

Best for:

Avoid donuts with twenty slices.

a small number of parts of a whole.

Funnel chart

Best for:

booking steps;
lead form steps;
other sequential conversion journeys.

Current launch limitations

The feature is new, and the limitations matter.

15 cards on standard properties

Standard properties are limited to 15 cards per dashboard. Premium properties can use up to 30.

For a small business, 15 is usually enough.

Published dashboards are shared with the property

Google says published dashboards are shared with the property.

Do not put an experimental or confusing dashboard into the main Reports navigation without considering who else uses the property.

Editor or Administrator needed to create and publish

Viewers can see published dashboards if they have property access, but creating and publishing requires the Editor or Administrator role.

No API support

Google currently lists API support as unsupported for Dashboards.

Do not build an external automation plan around a Dashboard API that Google does not currently provide.

No segments

Segments are not currently supported in the native Dashboard.

If your analysis requires segments, use another reporting surface such as Explorations.

No card-level comparisons

Google also says card-level comparisons are not currently supported.

Plan the dashboard around the controls it has now rather than designing around a feature that may arrive later.

A weekly 15-minute review routine

A dashboard becomes useful when it has a routine.

Try this once a week.

Minute 1–3: traffic and outcome trend

Check:

Ask:

Did traffic and outcomes move together?

users;
sessions;
main conversion;
booking or enquiry result.

Minute 4–6: acquisition

Check channel/source.

Ask:

Which source changed most?

Minute 7–9: landing pages

Check the top entry pages.

Ask:

Did a commercially important page gain traffic without gaining action?

Minute 10–11: device and location

Look for anomalies.

Ask:

Is mobile, desktop, or a geographic area behaving differently?

Minute 12–13: funnel

Find the biggest current drop.

Ask:

Did the leak move?

Minute 14–15: CRM or booking reality

Leave Google Analytics for a moment.

Check:

Ask:

Did the marketing metric become a business result?

That final step is what keeps the dashboard grounded.

qualified leads;
bookings;
cancellations;
no-shows;
completed work;
revenue where reliable.

Pair analytics with client and booking records

OneStudio can keep website, booking, client records, payments when configured, notifications, and operational analytics closer together. Its public features page describes those modules.

That does not mean OneStudio replaces Google Analytics or automatically imports every GA metric.

The two reporting layers answer different questions.

Google Analytics can help answer

where website visitors came from;
which landing pages they entered through;
which configured website events occurred;
which devices and locations were associated with visits.

Business records can help answer

A website plus CRM workflow is valuable because it gives the marketing dashboard a reality check.

whether the enquiry was qualified;
whether the person booked;
whether they attended;
whether they paid;
whether they returned.

What not to put on the owner dashboard

Avoid metrics that are:

Examples often include:

The dashboard should be boring enough to trust.

technically impressive but commercially irrelevant;
duplicates of another card;
too unstable to interpret weekly;
not configured reliably;
impossible for the owner to act on.
dozens of engagement micro-events;
every UTM combination;
raw event names without explanation;
vanity percentages with no baseline;
revenue estimates that do not match the billing system.

Build a dashboard for decisions, not decoration

The new Google Analytics Dashboard makes reporting easier to assemble.

That does not automatically make the reporting better.

A useful service-business dashboard has a small job:

show where customers came from, what they did on the website, where the journey leaked, and whether those actions became real business outcomes.

Start with 10–12 reliable cards.

Review them on a schedule.

Delete anything nobody uses.

Then investigate the deeper reports only when the dashboard shows a meaningful change.

For the website side of the funnel, review your service pages, booking journey, and website-to-CRM setup. Those pages and workflows determine whether the dashboard is measuring a clear customer journey or a pile of disconnected events.

Questions businesses ask

Are Google Analytics Dashboards available now?

Google announced Dashboards as available on September 9, 2026. Availability can still depend on the property experience and permissions, so use Google's current interface and Help documentation as the final check.

How many cards can I add?

Google currently documents up to 15 cards on a standard property and up to 30 on a premium property.

Can I use segments?

Not in the native Dashboard at launch. Google lists segments as unsupported.

Can I access Dashboards through an API?

Google currently lists API support as unsupported for the Dashboard feature.

Can every user publish a dashboard?

No. Google says Editor or Administrator role is required to create and publish dashboards.

Does a Dashboard replace Looker Studio?

Not necessarily. Native Dashboards are strong for one-property KPI monitoring. Looker Studio remains useful when you need multiple data sources, more presentation control, or a reporting model beyond the native limitations.

Should I put Google Business Profile data on the dashboard?

If your Google Analytics property is linked to a Business Profile, local actions can be useful. First check whether the Dashboard builder exposes the GBP metric you want; otherwise review it in the dedicated Business Profile collection. Keep local actions separate from website conversions and remember that Google currently documents a rolling six-month window for imported GBP metrics.