Visits, Hits, Users, Sessions: What Your Traffic Numbers Actually Mean

"We got 10,000 hits last month" used to be a common boast, and it was almost always a misleading one. Traffic terminology gets thrown around loosely, but the differences between these terms aren't pedantic โ€” mixing them up leads directly to overestimating how well a site is actually doing.

The Terms, Defined Correctly

  • Hits count every single file requested from the server on a page load โ€” the HTML, every image, every script, every stylesheet. One person loading one page can easily generate 30โ€“50 hits. This is essentially a meaningless number for judging actual traffic and has fallen out of use for good reason.
  • Pageviews count how many times a page was loaded, regardless of who loaded it. One person refreshing a page five times generates five pageviews.
  • Sessions (or "visits") group a user's activity into a single period of engagement, typically ending after a period of inactivity โ€” one session might include several pageviews.
  • Users count distinct individuals, ideally deduplicated across sessions, giving the closest approximation of "how many different people actually came to the site."

Why This Matters Beyond Terminology

Reporting the wrong metric changes the story entirely. A site with 50,000 hits might have only 800 actual users. A site owner who doesn't know the difference could believe they're reaching tens of thousands of people when the real number is a fraction of that โ€” and could make budget or strategy decisions based on a number that was never real in the first place.

A Simple Framework for Reading Your Own Traffic

  1. Always default to users as the headline number when judging real reach, not pageviews or hits
  2. Track sessions per user to understand engagement depth, not just raw volume
  3. Segment traffic by source (organic, direct, referral, paid, social) rather than looking at one combined total
  4. Watch trend direction over time more than any single month's absolute number

> Tip: If a report only shows "hits" or an unqualified "traffic" number with no breakdown, ask what's actually being counted before drawing any conclusion from it. It's one of the oldest ways traffic numbers get inflated, intentionally or not.

Common Mistakes

  • Treating hits as if they were visitors, wildly overstating actual reach
  • Ignoring source breakdown and treating all traffic as equally valuable
  • Focusing only on volume while ignoring engagement metrics like session duration or pages per session
  • Comparing traffic numbers across tools or time periods that measure things differently without adjusting for the difference

For a deeper look at how modern analytics platforms define these metrics, Google Analytics' own metrics documentation is a reliable, current reference.


The number on the dashboard is only useful if you know exactly what it's counting. Getting fluent in the difference between hits, pageviews, sessions, and users is a five-minute investment that prevents months of decisions based on a number that was never what it looked like.