Analytics dashboards bury owners in charts that never touch the register. A local business needs five numbers, each tied to a real-world event like a phone ringing or a car pulling in.
Open Google Analytics for your business website and you get a wall of charts: active users, engagement rate, average engagement time, event counts, a graph titled "sessions by session primary channel group." Somewhere underneath all of it is the one thing you actually wanted to know, which is whether the website made the phone ring.
The dashboard isn't lying to you. It was designed for every website on earth at once, from newspapers to software companies, and much of what it measures only becomes meaningful at that scale. A business serving one town needs a far shorter list.
I count five numbers that matter for a local consumer business. Each one maps to something that happens in the physical world.
Start with how many people tapped to call. On a phone your number should be a live link, so a tap opens the dialer with your number already filled in. Some of those taps become conversations, and conversations are where the money is. The tap itself can be counted.
Directions taps come next. A tap on your address or your map link is someone asking their phone how to get to your building. That is a person planning a trip to you.
Email taps are usually the smallest count of the three, and often the most serious, because email is where quotes and longer questions tend to live.
The fourth number is where visitors came from: Google, Facebook, a link on some other site, or your address typed straight into the browser. This is the only honest way to learn whether the effort you put into any one of those places actually produces visits.
And the fifth is which page people landed on, meaning the door they came in by rather than the pages they wandered through afterward. Landing pages tell you which parts of your site can actually be found from the outside.
Notice what the list has in common. A tap to call is a phone about to ring. A tap for directions is a car that might pull into your lot. Every number here either is a customer acting or explains where that customer came from.
Bounce rate sounds damning, and in today's Google Analytics it has a definition most owners don't expect. A bounce is a visit that lasted under ten seconds and triggered no tracked event, with no second page viewed. Now picture your best visitor: someone who finds your hours in eight seconds and heads straight over. That perfect visit gets recorded as a bounce. The metric was never built to tell the difference between leaving disappointed and getting the answer instantly.
Session duration has the opposite problem. It climbs when somebody leaves your site open in a tab while they make lunch. And at local traffic levels the math underneath is fragile. With a few hundred visits a month, a handful of odd sessions can move an average enough to look like a trend when nothing actually changed. Averages need volume before they mean anything, and volume is exactly what a one-town business doesn't have.
Pages per session quietly rewards wandering. On a site whose whole job is answering a visitor's question fast, more pages per visit can just as easily mean the visitor got lost. One page followed by a phone tap is a better visit than five pages followed by nothing.
None of these metrics is broken. Each is an answer to a question a local business isn't asking.
Google Analytics does not count these taps out of the box. Each one has to be configured as a tracked event, which is a modest job for whoever builds or maintains your site. Done once, it turns the tool from a wall of charts into a running record of customer actions.
That leads to a fair expectation. Whoever runs your website should have these events in place already, and once a month they should be able to tell you, in plain English, how many people tapped to call, where your visitors came from, and which page brought the most of them in. You shouldn't need a login or a tutorial to hear it. If the person hosting your site can't produce those sentences, the tracking probably isn't there, and it's worth asking about.
Less than you'd think, and that's the good news. These five work as a monthly pulse rather than weekly levers: is the tap-to-call count holding up through the slow season, and did last month's push on Facebook actually send anyone. When a number moves, you'll usually know why, because you did something in the real world around the same time.
The numbers also settle arguments cheaply. Whether a new page was worth building, or whether anyone arrives from that directory listing you pay for, stops being a matter of opinion once the doors are being counted.
There's also an entire layer these numbers can't reach. Analytics starts counting when someone arrives at your site, and it knows nothing about what happened before that. What people typed into Google, and how many of them saw your site in the results and passed it by, lives in a different free tool. I wrote about that one here: what Search Console knows about your customers that analytics doesn't.
Tell me what you're building. I'll come back with a plan for what the site should actually do.