Hey folks! 👋 I see this question come up a lot for folks just starting to dive into analytics, and it's a really important distinction to understand when you're looking at your Fathom dashboard.
In simple terms:
* **A Pageview** is counted every single time a page loads or reloads in a browser. If one user refreshes a page 5 times, that's 5 pageviews.
* **A Visit (or Session)** is a group of pageviews (or other interactions) from a single user within a given timeframe. That same user, with their 5 refreshes, is still just **1 visit**.
Here's a concrete example from my own site's logs. I was checking a blog post deployment yesterday. My own activity looked like this in raw logs:
1. Loaded the article page.
2. Refreshed to see a style fix.
3. Clicked to the "About" page.
4. Came back to the article via the nav menu.
In Fathom's terms, that's **4 pageviews**, but they all happened within 30 minutes with no long break, so it's just **1 visit**. Fathom typically ends a visit after 30 minutes of inactivity, which is pretty standard.
Why does this matter for us? When you're monitoring traffic after a new feature launch or a blog post, you want to know both numbers. A high pageview-per-visit ratio might mean people are engaging deeply with your content. A spike in visits but not pageviews could mean folks are bouncing quickly—maybe a link title was misleading.
It's like CI/CD metrics: you track both **build time** (a single event) and **deployment frequency** (a series of events over time) to get the full picture. They're related but tell you different things about your pipeline health.
Hope that clears it up! How is everyone else using these two metrics to inform their decisions?
-pipelinepilot
Pipeline Pilot
Excellent example, and you're spot on with that 30-minute timeout being the typical standard. That timing detail is crucial.
It gets even more interesting when you think about how different tools can slice this data. For example, in a data pipeline pulling from multiple sources, you might see a discrepancy where one system (like a CDN log) counts *every single HTTP 200 request* as a pageview, while the analytics script, using that 30-minute session logic, bundles them. I've seen reports differ by 20% just because of that!
Also, what about single-page applications (SPAs)? A user might navigate through five "views" without a single full page reload. In your example, that could be 1 pageview but 5 distinct events within a visit. Really makes you appreciate how the definition shifts based on the tech stack.
Data nerd out
That 30-minute "standard" session timeout is a perfect example of analytics tools overselling precision. It's an arbitrary line in the sand that gets treated like a physical law. If I open a blog post, get pulled into a 31-minute meeting, and then come back to finish reading, your tool calls that two visits. My intent was one continuous session. So when someone says "visits are up," you have to ask if engagement actually changed or if you're just measuring against a made-up timeout window.
Show me the TCO.