Analytics and Tracking

Session

Also called visit

One visit's worth of activity — the actions a person takes before a set period of inactivity ends the visit.

Quick facts: Session

Category
Analytics and Tracking
Also called
visit
Level
Beginner
Affects
Traffic reporting, conversion rate, engagement metrics
Where to see it
GA4 reports, Looker Studio, most analytics platforms
In this article4
  1. What a session measures
  2. Why sessions matter
  3. Where sessions go wrong
  4. How to act on it

What a session measures

A session groups everything one person does on your site into a single visit. It opens when the first page view or event is recorded and closes after a stretch of inactivity that the analytics tool defines. Come back after that gap and the tool opens a fresh session, even though the browser and the person have not changed.

Google Analytics 4 also closes a session when the day rolls over in the property’s reporting time zone. The inactivity timeout itself can be adjusted in the admin settings, which is worth knowing if your pages ask for long reading or carry a slow booking form where people naturally sit still for a while.

Why sessions matter

Almost every headline traffic number is built on sessions rather than on people. Conversion rate is usually conversions divided by sessions, channel reports count sessions, and a year-on-year traffic comparison compares them. Once you hold on to the fact that a session is a visit and not a visitor, those numbers stop being confusing. Sessions rising while users stay flat means people are returning more often, which is a very different story from reaching a new audience.

GA4 adds engaged sessions, which only count visits that lasted, went beyond one page, or triggered a conversion. That distinction is more useful than raw sessions when you are judging whether a page is doing its job, because it separates a real read from an instant exit.

Where sessions go wrong

Comparing session counts between tools is the most common trap. Analytics platforms rarely define the timeout, the reporting time zone and the rules for restarting a visit in the same way, so their totals differ even when both are installed correctly, and neither of them is wrong.

The other problem is inflation from your own side. Staff browsing the site, developers testing a change and uptime monitors all create sessions, and on a small site that noise is easily large enough to change the picture. Arriving from a link that carries no UTM parameters tends to open a new session filed as direct traffic, which quietly moves credit away from the campaign that earned the visit.

How to act on it

Set the property up so the counts mean something. Exclude internal and developer traffic, confirm the reporting time zone matches the market you actually sell to, and adjust the inactivity timeout if your pages demand long attention. Then pick one tool as the source of truth and stop trying to reconcile the others against it.

Use sessions for volume and trend, not for judging people or value. If the question is whether marketing is working, follow enquiries and sales through a properly configured analytics and tracking setup and treat sessions as the denominator sitting underneath them. A month with fewer sessions and more enquiries is a better month, and nothing in a sessions chart will tell you that on its own.

Do and do not

Do

  • Check the inactivity timeout suits how your pages are read
  • Use engaged sessions when judging content quality
  • Filter internal traffic before trusting session counts

Do not

  • Compare session counts across two different analytics tools
  • Judge a campaign on sessions rather than enquiries
  • Assume one session equals one person

Questions people ask about this

What is the difference between a session and a user?

A user is the browser or device identifier that analytics recognises, while a session is one visit made by that user. One person can create many sessions in a week, and the same person on a phone and a laptop usually appears as more than one user. Sessions measure how often people come; users estimate how many there are.

Why does my session count not match my hosting visitor stats?

Server logs and analytics measure different things. A log counts every request, including bots, crawlers and monitoring tools, while analytics only counts visits where its tag actually ran, which leaves out blocked scripts and people who leave before the page loads. Expect the log figure to be higher, and use analytics for behaviour and logs for infrastructure.

Should I worry if sessions rise but enquiries do not?

Treat it as a question rather than a failure. It usually means the extra traffic arrives with a different intent, lands on the wrong page, or comes from a source that was never going to buy. Look at which pages and which channels gained the sessions before changing anything on the site itself, because the cause is rarely the page you suspect.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.