Pageviews are the least useful number you have

Useful website analytics count the actions that matter — form submissions, tapped phone numbers, booking clicks, map taps — and attribute each one to the page and the source that produced it. Visitor counts tell you almost nothing you can act on, which is why they're the number most dashboards lead with.

What's wrong with knowing how many people visited?

Nothing, except that you can't do anything with it. "The blog got 400 visits last month" leads to no decision. "The blog produced eleven enquiries, nine of them from one article about pricing" tells you exactly what to write next.

The number you actually want is which pages produce contact, and what sends the people who make it. That's the only way to know where the next dollar should go.

Which conversion gets missed most often?

The tapped phone number. On a local business site it's usually the single most common way someone gets in touch, and it is almost never counted anywhere — because it isn't a form submission and it doesn't load a "thank you" page, so the default setup never sees it.

The full list worth counting:

• Form submissions, with the page they came from
• Tapped phone numbers and tapped email addresses
• Booking-link clicks and map or directions taps
• How far down the page people got — did anyone reach the part that sells?
• JavaScript errors from real browsers, which is what makes "we notice before you do" literally true rather than a slogan

How do I know if AI search is sending me anyone?

Only if the traffic is named individually. By default, visits from ChatGPT, Perplexity, Gemini, Copilot and Claude land in a generic "referral" bucket where they're invisible.

Naming them separately is the only way to find out whether any of the AI-visibility work is producing anything — which is a question you should be able to ask your own analytics, and should be suspicious of anyone who avoids.

Why no cookie banner?

Because the measurement is cookieless: no cookies, no fingerprinting, no cross-site tracking pixel. That's what removes the legal requirement for a consent banner interrupting people before they've read a word.

It's a deliberate trade. You give up individual-level tracking — you can't follow one person around the internet, and you can't say who a visitor was. For almost every business that's the right trade. It's reversible, but adding a cookie-based tool later is a change to your privacy policy, not just a technical change, and we'll put that in writing before doing it.

Common questions

Do I still get Google Analytics?

You can, and some businesses need it for ad platforms. It obliges a consent banner, so it's a decision rather than a default — we'll set it up and tell you in writing what it commits you to.

Do you record sessions or use heatmaps?

Not by default. Session replay captures whatever people type into forms, including things they type and then delete. If you want it, it goes in your privacy policy and your contract.

What do I actually receive?

One private portal with your own numbers, and one weekly plain-English email. Not a PDF of charts nobody opens.