What creates a pageview
The SDK sends an initial page event by default. A client router may need an explicit page call after navigation. The SDK avoids repeated empty page calls for the same path within one instance; a full reload can create another event.
Successful accepted events are deduplicated by message ID in the report pipeline. An event count is affected by which requests arrive, not just what appears on screen.
Pageviews, visitors, and sessions
One anonymous visitor can create many pageviews and multiple sessions. A pageview does not prove a person read the content, completed an action, or stayed for a measured duration.
Example
One visitor opens /, /pricing, and /docs during one visit. That is three pageviews, one anonymous visitor ID, and one session if no gap between them exceeds 30 minutes. The session continues past midnight.
Frequently asked questions
Does reloading count again?
A new accepted page event with a new message ID can count again, so a full reload can create another pageview. A retry of the same event should not count again, because the report pipeline deduplicates accepted events by message ID. Counts depend on which requests arrive, not only on what appears on screen.
Does a pageview count unique people?
No. A pageview measures observed page loads or tracked client-side navigation, not unique people. One anonymous visitor can create many pageviews and more than one session. A pageview also does not prove that a person read the content, completed an action or stayed for a measured duration.
Do client-side route changes count as pageviews?
Not always on their own. The SDK sends an initial page event by default, but a client router may need an explicit page call after each navigation. The SDK avoids repeated empty page calls for the same path within one instance. Test your router to confirm that each route change sends a page event.