Most dashboards fail the same way: they show thirty numbers, nobody knows which one matters, and the report is opened once and forgotten. If you want the practical build steps, follow our guide to building your first traffic dashboard in Looker Studio. This article answers the question that comes before it: what should be on the dashboard at all?
Start with decisions, not data
A useful metric is one that could change what you do next. Before choosing any number, write down three decisions your dashboard should help you make. For a small business site they are usually:
- Where should I spend my next hour? (Which channel brings people who actually read and act.)
- Which content deserves more of my time? (Which pages attract and keep visitors.)
- Is anything broken? (A sudden drop that needs investigating.)
If a metric cannot influence one of these decisions, leave it off the first version.
The six numbers worth tracking first
The definitions below are quoted or closely paraphrased from Google Analytics Help, so you can check them yourself.
| Metric | What it means | Decision it supports |
|---|---|---|
| Active users | Unique users who engaged with the site or app in the date range | Is the audience growing? |
| Sessions | Visits to the site; one person can create several | Is overall activity rising or falling? |
| New users | Unique users who triggered a first visit in the date range | Are we reaching new people? |
| Engagement rate | Percentage of sessions that were engaged: longer than 10 seconds, or with a key event, or with two or more page views | Is the traffic any good? |
| Sessions by channel | Visits grouped by how people arrived (organic search, direct, referral, social and so on) | Where should I spend my time? |
| Key events | The actions you marked as important, such as a form submission | Is the site achieving its purpose? |
Two traps in the definitions
- Bounce rate is not what it was. In GA4 it is simply the percentage of sessions that were not engaged, the opposite of engagement rate. Do not compare it with bounce rates from older Universal Analytics reports or from other tools.
- "Users" has two meanings. Total users counts anyone who triggered any event; active users counts those who engaged. Analytics reports show active users, so mixing the two in a dashboard will make numbers disagree.
Define your key events honestly
Key events are the one metric that is entirely up to you, and the one most often set badly. Mark only actions that matter to the business:
- A contact form submission (we track our own this way).
- A click on a phone, email or WhatsApp link.
- A purchase or booking confirmation, if you sell online.
Do not mark every scroll or every page view as a key event. If everything is a conversion, the number says nothing. Note also that older guides call these "conversions"; Google's current pages say "key events".
A weekly review in ten minutes
A dashboard earns its place only if you look at it on a schedule. This routine fits a small site:
- Look at the trend first. Is this week's line above or below the previous four? Ignore single-day spikes.
- Check the channels. Did one grow while another fell? Write one sentence about why you think so.
- Open the top pages. Which pages gained readers? Plan an update or a follow-up for the best one.
- Read the engagement rate. A fall after a change to the site is a signal to investigate that change.
- Record one action for the coming week.
Keeping the sentence and the action in a notes file turns the dashboard into a decision log. After a few months it also shows you which of your guesses were right.
Numbers to leave off (at least at first)
- Pageviews on their own. They rise when people get lost as well as when they are interested.
- Total users beside active users. Pick one and use it consistently.
- Averages without context. An average session duration can be dragged around by a handful of very long or very short visits.
- Anything you cannot act on, however impressive it looks.
Be careful with small samples
A new or small site produces small numbers, and small numbers move around. A day with ten visits instead of twenty is not a "50 percent drop". Compare weeks or months, and treat any single-digit changes as noise.
Privacy and consent
Analytics data comes from real visitors. Tell visitors what you collect, honour consent requirements where they apply, and keep reports to the people who need them. Our privacy policy shows how we describe this for our own site, which you can use as a model for the structure (what is collected, why, and how to opt out), although you should write your own to match your actual setup.
Putting it together
- Write down your three decisions.
- Choose the six metrics above and mark your key events honestly.
- Build one page following our Looker Studio walkthrough.
- Review it weekly for four weeks and write one action each time.
- Only then add a second page, if a real question demands it.
A real dataset to practise on
The dashboard in this guide is only as useful as the numbers behind it. Here is the honest starting point for this blog, from Search Console for October 10 to November 6, 2026: 237 impressions, 0 clicks and an average position of 45.5. Putting those three numbers on a scorecard is a good first dashboard, because the first job of a dashboard is to show where you stand before you try to change it.
We update the figures when new data is available. We have not built this dashboard for a client; the guide follows Google's own documentation, and the article says where we have and have not verified steps.
How this article was produced
This article was researched and drafted with AI assistance, working from the primary sources listed below, then published by the site owner, who is responsible for it. If you find an error, tell us. Our standards are described in the editorial policy.
What we have and have not verified
The metric definitions come from Google Analytics Help pages linked below. The six-metric starter set, the weekly routine and the list of metrics to leave off are our recommendations for small sites based on those definitions; they are judgement, not Google rules, and your business may need different ones.
Sources
- Google Analytics Help: Engagement rate and bounce rate
- Google Analytics Help: Understand user metrics
- Google Analytics Help: Session
Disagree with something here, or found an error? Write to us and we will review it.
About the author: Junaid Sabir writes about practical AI and automation for people without a technical background. This article was drafted with AI assistance, then checked and edited by the author; the "What we have and have not verified" notes say which parts were tested.