This guide is written for the marketing manager who feels slightly lost every time they open an analytics dashboard. For the business owner who knows they should be tracking things but is not sure what to track. For the product lead whose developer installed an analytics tool months ago, but who has never quite figured out what to do with the numbers.
You do not need to be a data analyst to make good decisions from web analytics. You need a clear mental model, a small set of metrics that actually tell you something useful, and a repeatable process for reading them. This guide covers all three.
By the end, you will know which numbers to look at first, what they mean in plain terms, how to diagnose the problems hiding in your data, and how to turn what you see into decisions your team can act on the same week.
Chapter 1: What web analytics actually measures
Before reading any dashboard, it helps to understand what is being counted and how. Most people open analytics and see a number (4,287 visitors last month) without understanding what that number represents or why it might be wrong.
The basic model
When someone visits your website, their browser sends a request to your web server. The page loads. Your analytics tool records that a visitor arrived, which page they landed on, where they came from (the URL they clicked or the search they did), and what device and browser they used.
From that point on, the analytics tool tracks what happens: does the visitor click something, navigate to another page, fill out a form, or leave without doing anything? All of this gets recorded as a series of events associated with that visitor's session.
The three levels of data
The relationship is: many pageviews per session, many sessions per visitor. When a dashboard says "10,000 visitors, 14,000 sessions, 42,000 pageviews," it means 10,000 distinct people visited, they came on average 1.4 times each, and they viewed 4.2 pages per visit on average.
Why the numbers might be wrong
Two important things to know before trusting any analytics number:
Cookie-based tools miss opted-out visitors. Tools like Google Analytics place a cookie on the visitor's browser to identify them across sessions. In European markets, 30 to 50% of visitors decline or ignore cookie consent banners. Those visitors are completely invisible in your reports. The data you see represents only the people who accepted tracking, which skews toward engaged, brand-familiar users. Your actual traffic is higher than what GA4 reports.
Cookieless tools see everyone. Tools that do not place cookies (such as Sublim, Plausible, or Fathom) measure all visitors, regardless of consent preferences, by processing signals available without storing anything on the visitor's device. Their numbers are more complete. For more on this distinction, see our article on running analytics without a consent banner.
