Website Analytics: What to Look at Beyond Visitor Counts

"How Many Visitors Did We Get This Month?" May Be the Wrong Question

Almost every business with a website has an analytics tool installed. Usually it is set up, watched with interest for a few weeks, then forgotten. Every now and then someone opens it to answer "how many visitors did we get?", feels good if the number beats last month and slightly worried if it does not. Then life goes on.

The trouble is that visitor count on its own leads to almost no decision. More people arriving at your site may be good news; but if they cannot find what they came for and leave within seconds, or if the traffic consists of an audience that will never buy from you, the rising number is just an illusion.

Set up properly, web analytics answers a far more useful question: why are people coming to your site, what are they looking for, and why do they leave without taking the step you want? This post covers how to make web analytics actionable at the scale of a small or medium-sized business.

How Modern Analytics Works: An Event-Based View

GA4, the current version of Google Analytics, introduced an important shift from the previous generation: measurement now centres on the event rather than the page view. A page view is one event; so is clicking a button, submitting a form, watching a video, or downloading a file.

The practical implication is significant. You used to easily answer "which pages did the user browse"; now you can answer "what did the user do on the site." For a services business, "the contact form was submitted 12 times" is far more valuable than "the contact page was viewed 400 times."

The natural consequence: installing the tool is not enough. Until you define the actions that matter to you, all you have is traffic numbers again. That is where the real setup work begins.

Which Metrics Actually Tell You Something?

Dashboards contain dozens of metrics, and watching all of them produces the same result as watching none. For a small or medium-sized business, the meaningful core is:

• Conversions: how many times did the action you want on your site actually happen? Form submission, phone tap, quote request, purchase. This is the lifeblood of analytics.
• Traffic source breakdown: are visitors arriving from search, social, direct, or ads? Which of those converts?
• Landing pages: which page do people enter through? Usually it is not your home page — more often a blog post or a service page.
• Engagement quality: do visitors spend meaningful time, scroll, move to another page — or open and close immediately?
• Device split: if most traffic is mobile, a problem in the mobile experience hits revenue directly.

Most metrics outside this list are useful when you are chasing a specific problem, but they should not occupy space on your regular review. When choosing what to track, the logic from our post on choosing the right KPIs applies here too: a metric is worth watching only if you would change something based on it.

Define Your Conversion First

The most critical step in an analytics setup is the one most sites skip: telling the tool what "success" means for you.

To work it out, ask a simple question: what does a visitor have to do on my site for it to be valuable to me? For a consultancy, that might be submitting the contact form. For an online store, a purchase — but also an add-to-cart. For a local business, tapping the phone number or opening the directions link.

Once those actions are marked as key events, analytics suddenly makes sense. You are no longer asking "which page got the most views" but "which page brought me customers." Those are almost never the same page — and the gap between them determines where your budget should go.

Reading the Numbers by Source

Looking at total traffic melts different sources into a single average and hides the truth. In the same month, 200 visitors from search might leave 8 quote requests while 2,000 from social media leave 1. Someone looking at the total thinks social media is working; someone looking at the source knows where to invest.

A few things to watch when making this split. Visits from your own team and developers should be kept out of the measurement. If ad and email links are not tagged with campaign parameters, that traffic usually shows up as "direct" and you lose sight of which effort worked. And compare like with like — if your sector has weekday/weekend or seasonal patterns, comparing two dissimilar periods will mislead you.

The groups that emerge when you read traffic by source are really a first step toward customer segmentation: audiences from different channels behave differently and need different messages.

The Limits of Analytics, and the Privacy Side

However well it is set up, web analytics never gives you absolute truth, and it should be used with that in mind.

Because of ad blockers, visitors who decline cookie consent, and browser restrictions, some portion of traffic never enters the measurement at all. That is why your analytics figures will never exactly match hard records such as your orders — this is not a bug, it is the nature of the tool. The right approach is to use analytics as a trend and comparison instrument, not as a source of absolute numbers. Firm figures like revenue should always come from your own systems.

There are also responsibilities on the privacy side that should not be skipped. Tools that measure visitor behaviour may fall within the scope of personal data processing, which means your site needs a cookie notice and privacy statement, an explanation of what is measured, and a review of retention periods. Our data protection compliance guide covers these topics; where the regulation demands it, it is worth getting expert advice. It is also both safer and more useful in practice to analyse groups and trends rather than individual visitors.

Turning Numbers into Decisions

Analytics starts paying off the moment you look at the dashboard and change something. The simplest way to make that a habit is a half-hour review once a month: how many conversions last month, from which sources, which page brought the most customers, and which page got plenty of visits but produced nothing?

That last question usually yields the most valuable finding. A page with heavy traffic and no conversions is either attracting the wrong audience or failing to tell the right audience what to do next. Both have clear fixes, and usually small ones.

Once this rhythm is in place, web analytics stops being an isolated report and becomes part of the business's overall measurement. Viewed alongside sales, stock, and customer data in one place, its value multiplies; we covered how to build that in our post on designing an effective dashboard. For the broader picture of why numbers so often fail to become decisions, see why deciding with data is hard.

At Lumethis, we help businesses combine web and sales data into a single meaningful view that can actually be reviewed regularly. If you would like to make your own site's data decision-ready, get in touch; you can also explore our data and software services to see how we work.