Page views, visitors, and clicks: what your link-page numbers mean
Learn which traffic numbers count visits, which count actions, and how to avoid reporting page views as customers.
The useful takeaway
Choose the measurement that answers your question, and keep its definition beside the number.
A link-page dashboard can show several encouraging numbers without telling you whether anyone became a customer. Views describe exposure to a page. Visitors attempt to count people or browsers. Clicks describe actions. Those are different questions, and combining them under a single heading called traffic makes it harder to decide what to improve.
Start with the decision you need to make. If you want to know whether a campaign brought attention, count relevant arrivals. If you want to know whether the page helped, examine actions after arrival. If you want to know whether the business benefited, follow those actions to a confirmed outcome.
What a page view can tell you
A page view is an observation that a page was viewed under the tracking system's rules. A person can create several by returning, reloading, or navigating. Google explains its own collection behavior in its pageview documentation. Your link provider may use a different implementation, so read its definition before comparing products.
Use views to understand page activity, not audience size. Also separate the page that sells your service from pages your customers have published. A platform can have growing customer-page traffic while its own signup page receives very little attention. Both numbers matter, but they answer different business questions.
Why visitors are an estimate
A visitor metric needs a rule for deciding whether two observations belong together. Different browsers, devices, privacy settings, and reporting identities affect that rule. Google's reporting identity documentation describes how its user calculations depend on available identity information. A dashboard label does not establish that every counted visitor is a distinct human being.
Prefer the tool's actual label in reports. Write estimated visitors or tracked browsers when that is what you have. Avoid turning a session identifier into a claim about a named person. A respectful analytics setup accepts gaps instead of trying to defeat browser protections to make the count look complete.
Clicks are actions, not completed tasks
A click on Book a consultation shows that someone attempted the next step. It does not establish that the booking page loaded, that an available appointment existed, or that a reservation was confirmed. Likewise, a click on a shop button is not a sale. Measure completion in the destination system when access and consent permit.
Count total clicks and unique clicking sessions separately if your tooling supports both. A visitor who tries the same broken link four times can increase total clicks while experiencing failure. If you see a sudden increase in repeat clicks, inspect the destination before congratulating the page on stronger engagement.
An illustrative visit ledger
Imagine a hypothetical day with three browsers. Browser A opens the link page twice and clicks the menu once. Browser B opens it once and clicks the booking button twice. Browser C opens it once and leaves. That produces four page views, three observed browsers, and three total clicks, before any filtering or collection loss.
Two browsers clicked, so the session or browser level clicking proportion could be two out of three under this simplified example. Dividing three clicks by four page views produces a different statistic: clicks per view. Neither formula is automatically wrong, but they cannot share the same label. This small ledger is useful for checking what your own dashboard actually calculates.
Build a four-line measurement dictionary
Write down the name, counting rule, exclusions, and limitation for each metric you use. For views, specify whether refreshes and internal previews count. For visitors, identify the deduplication method and reporting window. For clicks, describe whether every tap counts. For outcomes, define the confirmed business event and whether retries are deduplicated.
Keep this dictionary beside the weekly report rather than buried in a technical document. When someone asks why social-platform clicks differ from website views, you can compare definitions before investigating a failure. An unexplained difference deserves attention; a difference caused by two legitimately different counting systems deserves a clear note.
Use the numbers to choose the next action
If arrivals are scarce, work on distribution and the reason to visit. If arrivals are healthy but useful clicks are scarce, inspect message clarity, link relevance, and mobile usability. If useful clicks occur but completions do not, examine the destination, offer, and tracking connection. Each pattern points to a different job.
End the report with a decision rather than a bigger aggregate number. For example: keep the booking button in place, repair the confirmation event, and review again after a complete reporting week. A modest set of well-defined measurements helps you act more confidently than an impressive total assembled from incompatible events.
Sources & further reading
References for the principles and technical details in this guide.
Found something that needs correcting? Send us a correction.