sessions
A session is one continuous visit to your site by one person, from the moment they land to the point they go quiet, counted as a single unit no matter how many pages they look at.
A session is the basic unit that analytics tools count a visit in. Someone lands on your site, clicks around for a while, maybe reads a page, maybe fills out a form, and then leaves or goes quiet. That whole stretch, start to finish, is one session. It does not matter if they looked at one page or ten. It is still counted once.
The tool watching your site has to decide when a session ends, since nobody clicks a button to say “I am done browsing.” The usual rule is a timeout: no activity for a set stretch, commonly thirty minutes, and the session closes. Come back an hour later and you start a fresh one, even though it is the same person on the same device.
Sessions are the denominator behind almost every other number you look at. A funnel tells you what fraction of sessions turned into a lead. A click-through rate tells you what fraction of ad impressions turned into a session. Get sessions wrong, through duplicate tracking or a broken tag, and everything built on top of it is wrong too.
Why it matters to you
Session counts are the first thing most business owners look at, and the easiest to misread. A jump in sessions after a slow news week or a Facebook mention feels like progress, but if none of those sessions turned into a call or a booking, nothing actually changed for the business. I treat sessions as the starting point for a question, not the answer to one.
Where sessions matter more is as a sanity check. If your ad spend goes up and sessions from ads do not move, something in the account is broken before you even get to results. If sessions collapse overnight, you likely have a tracking problem, not a traffic problem. Either way, the number is a diagnostic, not a scoreboard.
How I use it
I set up analytics so sessions are counted once, cleanly, across the whole site, using Google Analytics or PostHog depending on the client. I check that sessions from paid ads, organic search and direct visits are labelled separately, because a session from someone who searched your business name means something different from a session from a stranger who clicked an ad.
I do not chase raw session growth as a goal. I look at sessions next to events, which record what people actually did during the visit. A month with fewer sessions but more calls booked is a better month than the reverse, and sessions alone would never show you that.
What it looks like in practice
In the reporting I send, sessions show up as one line among several, usually broken down by where they came from: organic search, paid search, direct, referral. Next to it sits the number that matters more, how many of those sessions led to a phone tap, a form or a booking click.
If a client asks “how many people visited my site,” sessions is the honest answer to that specific question. It is a real number and it is worth knowing. It is just not the number that tells you whether the month went well.
Questions I get about this
- If someone visits my site twice in one day, is that one session or two?
- Usually two. Most analytics tools close a session after a set stretch of inactivity, often thirty minutes, so a morning visit and an evening visit count separately even though it is the same person.
- Is a high number of sessions automatically good?
- Not on its own. A session with no phone tap, no form and no booking click is just a number. I care more about what happened inside the session than how many there were.
- How is a session different from a pageview?
- A pageview is one page loading. A session is the whole visit, which might include five pageviews or one. Sessions tell you how many separate visits you got. Pageviews tell you how much people looked at once they arrived.
Want this set up properly for your business?
This is the kind of thing I build every week. Grab a time and we will talk through what fits.