Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Session

A group of one user's interactions with a site or app in one visit, ended by inactivity.
AnalyticsconceptUpdated

Definition

In Google Analytics 4, a session begins when the tag records a session_start event, which it does when activity starts after a period of inactivity. Every later event in the visit carries the same session identifier and a session number as parameters. The session ends when the inactivity timeout passes; the timeout has a documented default that an editor can change in the data stream settings. Unlike the previous generation of Google Analytics, GA4 does not start a new session at midnight or when the campaign source changes partway through a visit, which is one reason session counts fell for many sites when they moved over.

Each session is given a source, medium and campaign from the way it began, and those session-scoped dimensions are what most acquisition reports group by. The GA4 reports and dimensions guide explains how the session scope sits alongside the user and event scopes, and why mixing scopes in one table produces numbers that do not add up.

In practice

Sessions matter less as a count than as a denominator. Engagement rate is engaged sessions divided by sessions, bounce rate is its complement, and most on-site conversion rates divide key events or orders by sessions. A change in how sessions are counted therefore moves every one of those rates, even when behaviour has not changed.

That makes the session the right unit for questions about visits, such as which landing page or campaign brings engaged traffic, and the wrong unit for questions about people. A customer who visits five times before buying produces one order and five sessions; a session-based conversion rate describes visits, and a user-based rate describes customers. Paid campaigns bought for visits are judged the same way: the Google Ads guide to traffic campaigns reads results on engaged sessions in analytics rather than on the platform's click count.

Sessions, users and clicks

UnitCounted byStarts when
ClickThe ad platformSomeone clicks the ad
SessionThe analytics toolThe tag on the site records activity after inactivity
UserThe analytics toolA new identifier is seen, blended according to the reporting identity setting

A click becomes a session only if the landing page loads, the tag fires and consent allows it to be recorded. People who leave before the page loads, who block the tag or who decline consent produce clicks without sessions; people who click twice in quick succession produce two clicks and one session. The guide to why Google Ads and GA4 numbers differ works through these gaps and how to reconcile them by cause.

Why counts differ between GA4, BigQuery and ad platforms

Even inside one product, sessions are counted in more than one way. The GA4 interface estimates user and session counts with an approximation technique, may add modelled data under consent mode and applies thresholds. The raw export has none of those adjustments, and it has no session rows at all: as the BigQuery export basics guide explains, a session is the combination of the pseudonymous user identifier and the session identifier parameter, counted distinct. Warehouse models then often build their own sessions table, and the SQL for marketers guide starts from exactly such a table. Small gaps between these sources are expected; a large one usually means two queries are not counting the same thing. The GA4 common mistakes guide lists treating the lower GA4 session count as lost data among the usual misreadings.

Illustrative example — not a real result

More clicks than sessions

Askew Piano Tuition runs a search campaign that Google Ads reports as 1,240 clicks in March, while GA4 shows 960 sessions from that campaign. The teacher suspects a broken tag. Checking by cause: the site's consent banner is declined by about 15% of visitors, which accounts for roughly 190 missing sessions; around 50 clicks come from people who tapped twice or left before the page loaded; and a handful arrive on a landing page whose redirect strips the click identifier, so GA4 files them under another source. With those explained, the remaining gap is under 3%, and the teacher keeps judging the campaign on enquiries per session rather than on clicks.

GA4 defines sessions by its own rules, which differ from older analytics tools and from other products. Engagement Rate and Bounce Rate are both shares of sessions, so they inherit every change in how sessions are counted. CVR calculated per session describes visits, not customers, and should say which denominator it uses.

Common confusions

  • A session is not a user. One person can produce many sessions, and one shared device can blend several people.
  • A session is not a click. Clicks are counted by the ad platform, sessions by the analytics tag.
  • Lower session counts after a migration are not lost data. The definition changed.
  • Session counts in the interface and the export will not match exactly. One is estimated, the other raw.
  • A session rate is not a customer rate. State the denominator whenever a conversion rate is quoted.

More terms to look up

Calculators

Where this term is used

Sources

  1. Google Analytics Help — Google Analytics Help

Related