GA4 dashboards or Looker Studio for a small e-shop?

Short answer: GA4 dashboards, launched in Google Analytics on 9 September 2026, let you put your key KPIs on one page without Looker Studio. For a small e-shop that needs one weekly overview, they are enough. Standard properties are capped at 15 cards per dashboard, and segments, card-level comparisons and API access are missing. For any of those, you still need Looker Studio.

What GA4 dashboards are and what they include

A dashboard is one report inside your GA4 property. You build it from cards, and each card shows one metric or one view of your data. Google documents the feature in the official GA4 dashboards help article.

These are the confirmed facts:

• Visualizations: score cards, table charts, line charts, bar charts, donut charts and funnel charts.
• Card limit: up to 15 cards per dashboard on standard properties and up to 30 on Premium (GA4 360) properties.
• Permissions: you need the Editor or Administrator role to create and publish. Anyone with access to the property can view published dashboards.
• Sharing: every published dashboard is shared with the whole property. You cannot publish a dashboard to only some users.
• Not supported yet: API access, segments and card-level comparisons.

The practical point: most small teams used Looker Studio for one reason, which was to see revenue, traffic and conversion rate on one screen. That job can now stay inside GA4.

GA4 dashboards or Looker Studio: how to decide

Base the choice on the questions your team asks every week, not on which tool looks nicer.

Your situation	GA4 dashboard	Looker Studio
One e-shop, one country, owner checks KPIs weekly	Enough	Overkill
You need GA4 data only	Enough	Optional
You want to compare new and returning customers or other segments	Not possible yet	Needed
You need this month vs last month on every card	Not possible yet	Needed
You combine GA4 with ad spend, CRM or margin data	Not possible	Needed
You need more than 15 views on one page (standard property)	Split into two dashboards	No such cap
Some people must not see a report	Not possible, published means whole property	Share per report

If every row that applies to you says “Enough”, build the GA4 dashboard and stop maintaining a Looker Studio report nobody opens.

How to build a 15-card e-shop dashboard step by step

Fifteen cards is fewer than it sounds. Decide what goes in before you open GA4.

Step 1: Check the data before you chart it

A dashboard only makes bad data easier to read. Make sure purchases fire once, revenue is sent without VAT or consistently with it, and staging or test domains are excluded. If you have not done the last one, follow my guide to setting up a GA4 hostname include filter first.

Step 2: Write down 5-7 questions the owner asks

Examples: “How much did we sell this week?”, “Which channel brought the buyers?”, “Where do people drop out of checkout?”. Every card has to answer one of them. If a card answers nothing, leave it out.

Step 3: Use a fixed layout

Here is the layout I start from for a small e-shop. Adjust the metrics to your own key events.

1. Score card: total revenue
2. Score card: purchases
3. Score card: average order value
4. Score card: sessions
5. Score card: e-commerce conversion rate
6. Line chart: revenue by day
7. Line chart: sessions by day
8. Funnel chart: product view, add to cart, begin checkout, purchase
9. Bar chart: revenue by session default channel group
10. Table chart: source/medium with sessions, purchases, revenue
11. Table chart: top products by revenue
12. Bar chart: revenue by country (useful if you sell in SK, CZ and beyond)
13. Donut chart: sessions by device category
14. Table chart: top landing pages with purchases
15. Score card or table: your main lead or newsletter key event

This uses all 15. If you need a card for a second country or a campaign launch, something has to go. That trade-off is useful, because it keeps the dashboard focused.

Step 4: Publish once, then show people where it is

Publishing needs the Editor or Administrator role. Once it is published, everyone with property access sees it, so give it a clear name like “Weekly KPIs” and publish only the final version.

What I see in the accounts I run

In most of the smaller e-shop accounts I work in, the Looker Studio report is not missing. It exists, it was built by someone years ago, and nobody opens it. The owner still asks “how did we do last week?” by email.

The report failed because it had too much in it, not because the tool was wrong. Three pages, 40 charts, filters nobody understood. The 15-card cap in GA4 dashboards forces the discipline those reports never had.

The other thing I see often: owners take GA4 revenue as the truth about ad performance. A dashboard makes that worse, because the number looks official. GA4 revenue is not profit, and it does not include your ad spend. If you judge campaigns on value, set up conversion values that reflect margin, as described in my Google Ads conversion value for profit guide.

Most common mistakes with GA4 dashboards

• Publishing test dashboards. Published means visible to the whole property, including agencies and freelancers you gave viewer access to. Keep experiments unpublished.
• Charting before fixing tracking. Duplicate purchases or test orders now show up in a clean, trustworthy-looking card.
• Expecting segments. You cannot split a card by new vs returning buyers or by a custom audience yet. Do not promise that to a client or a boss.
• Expecting period comparisons on cards. Card-level comparisons are not supported. Change the date range of the whole report and compare by eye, or use Looker Studio.
• Treating it as an ad report. There is no cost data from Meta or other platforms here, so no ROAS (return on ad spend: revenue divided by ad spend) and no MER (marketing efficiency ratio: total revenue divided by total marketing spend).
• Planning automation on it. There is no API support yet, so you cannot pull dashboard data into other tools.

When not to use GA4 dashboards

Skip them, or use them only as a quick internal view, if you report blended performance across Google Ads, Meta and email, if you need to calculate profit after VAT, shipping and ad costs, or if different people must see different reports. In those cases Looker Studio, or a spreadsheet fed from each platform, is still the right tool.

Also skip them if your GA4 data is broken. A clean dashboard on top of broken tracking is worse than no dashboard, because people stop questioning the numbers.

What to do first

Check that purchases and revenue are tracked correctly, write down the handful of questions your team actually asks, and build one 15-card dashboard from the layout above. Use it for a month before you decide whether Looker Studio is still needed.

If you want someone to check your tracking and set up reporting that ties back to ad spend, see my PPC specialist services or the full list of performance marketing services.

Email me and I’ll reply within 24 hours.