Contact support

We reply by e-mail, usually within two days.

Google reCAPTCHA checks this submission against abuse; data is sent to Google. The script loads only when this form is opened.

← All posts

A visit is not a person

A fundamental misconception in web analytics involves equating every registered image request with a distinct individual. Understanding how tally systems record activity requires distinguishing technical events from human presence.

one personfive subpagesfive requestsand several people behind one shared connection look like one

One person, several requests

Every time a browser loads a web page, it requests all embedded resources independently. If a single visitor opens five different subpages, the server registers five separate file requests. Conversely, multiple individuals sharing a single corporate workstation or household network might trigger requests that appear bundled under a unified network signature.

The reverse case is just as common and less obvious. A household with four people behind one connection, a school with two hundred pupils behind one, a company office — all of them arrive under a single network address. A counter that tried to correct for this would have to guess, and guessing is worse than counting.

What triggers a request without a reader

Furthermore, automated background checks, browser pre-fetching routines, and RSS feed readers can trigger image requests without a human ever viewing the visible page layout. These technical automated behaviors blend into the general log stream, meaning numbers reflect interactions between machines rather than a direct census of human bodies.

Pre-fetching deserves a sentence of its own because it is invisible from both ends. A browser that expects the next page to be opened may fetch it in advance, image and all. If the reader never clicks, the page was counted and never seen. Nothing malfunctioned; the browser did exactly what it was built to do.

What the number is instead

Recognizing this distinction transforms how statistics are interpreted. A counter provides an objective index of system engagement and content delivery frequency, serving as an operational gauge rather than a biological headcount.

The useful reframing is to stop reading the number as a headcount and start reading it as a delivery count. It says how often the page was handed out. That is a real quantity, it is measured rather than estimated, and it does not become less true for failing to be a census.

It also has the property that matters most over time: it is consistent with itself. Whatever the ratio of requests to people happens to be, it stays roughly the same from month to month, so a doubling of the number still means that roughly twice as much reading is going on.

Which is why the comparison to make is always internal. This month against last month, this article against that one, this season against the one before — never this counter against a figure from a different tool, which counts a different thing under the same word.

Advertisement