Session · web analytics

On this page 8

A session in web analytics is a group of interactions that one user performs on a website or app within a single visit, such as page views, scrolls, clicks and purchases, bounded by a period of inactivity or another defined break. In marketing analytics, the session is the basic unit of traffic: it carries the traffic source, the landing page and the engagement signals that marketers use to judge campaigns, channels and content.

Sessions are not observed directly. They are constructed by the analytics tool from a stream of timestamped events, so every session count depends on rules that the tool or the analyst defines. Understanding those rules is essential before comparing session metrics across platforms, periods or properties.

How analytics tools build a session

An analytics tool builds a session by grouping events that share a client identifier and fall within a continuous time window. A tracking script or SDK assigns each browser or device a client ID, usually stored in a first-party cookie or local app storage, and attaches it to every event sent to the collection endpoint.

The first event from a client with no active session opens a new session and receives a session identifier. Later events join that session until a termination rule fires. In GA4, the session_start event and the ga_session_id parameter mark this boundary, and the session inherits the campaign parameters of the event that started it, including any UTM tags on the landing URL.

The following table lists the most common rules that end a session and how major tools apply them.

RuleTypical settingEffect on the count
Inactivity timeout30 minutes by defaultA pause longer than the limit starts a new session
Midnight boundaryApplied in Universal AnalyticsA visit crossing midnight splits in two
Campaign changeApplied in Universal AnalyticsArriving through a new source restarts the session
Maximum durationOften 24 hours or tool specificVery long visits are cut into parts
App backgroundingMobile SDKs, often 10 to 30 secondsReturning from background may start a new session
Common session termination rules

Because GA4 does not restart sessions on campaign changes or at midnight, the same traffic usually produces fewer sessions in GA4 than it did in Universal Analytics. Analysts who compare historical data across the migration should expect a gap and should not read it as a loss of visitors.

Session metrics used in marketing analytics

Session metrics describe how much traffic arrives and how it behaves once it lands. They form the denominator of many ratios, so a change in session definition shifts conversion rates, engagement rates and cost per session at the same time.

This table summarizes the core session metrics and what each one tells a marketer.

MetricDefinitionTypical use
SessionsCount of sessions started in the periodVolume of traffic by channel
Engaged sessionsSessions over 10 seconds, with a conversion or with 2+ page viewsQuality of traffic in GA4
Engagement rateEngaged sessions divided by sessionsReplacement for the inverse of bounce rate
Average session durationTotal engagement time divided by sessionsDepth of content consumption
Session conversion rateSessions with a key event divided by sessionsLanding page and campaign efficiency
Pages per sessionPage views divided by sessionsNavigation depth and content discovery
Core session metrics

In GA4, bounce rate is defined as the share of sessions that were not engaged, which differs sharply from the older single-page definition. The 10-second engagement threshold can be raised to as much as 60 seconds in the property settings, and that change alone moves engagement rate and bounce rate without any change in actual visitor behavior.

Sessions compared with users, page views and events

A session sits between the user and the event in the analytics hierarchy. One user can produce many sessions, and one session usually contains many events. Confusing these levels leads to wrong denominators and inflated or deflated rates.

UnitScopeMain identifierKey weakness
UserAll visits by one person or deviceClient ID or user IDCookie loss creates duplicate users
SessionOne visit bounded by rulesSession IDDepends on timeout and tool rules
Page viewOne page or screen loadEvent with page locationSingle-page apps may undercount
EventOne recorded interactionEvent name and timestampVolume makes raw analysis costly
Session and neighboring measurement units

The choice of unit should match the business question. Campaign landing performance is usually analyzed per session, while retention and lifetime value require user-level analysis. Multi-touch attribution works with sequences of sessions, because each session carries its own source and medium.

Attribution and the session source

Each session is tagged with a source, medium and campaign derived from the referrer, the UTM parameters or an ad click identifier such as gclid. Session-scoped dimensions in GA4, such as session default channel group, describe how the visit began, while user-scoped dimensions such as first user source describe how the person was first acquired.

Direct visits receive special treatment. Many tools apply a last non-direct click rule, so a returning visitor who types the address is credited to the earlier marketing source if it falls within the lookback window. This rule makes session-level channel reports look more favorable to paid and organic channels than a strict last-click view would.

Configuring and validating session tracking

Accurate sessions require consistent tagging, correct domain settings and a sensible timeout. Most problems appear when a site spans several domains, uses a payment gateway or loads content without full page reloads.

The decision table below shows typical situations and the recommended configuration.

SituationRecommended settingReason
Long-form content or videoRaise the timeout to 60 minutes or moreReaders pause without leaving
Checkout on another domainEnable cross-domain measurementPrevents a new session at payment
Payment gateway referralsList gateways as unwanted referralsKeeps the original campaign source
Single-page applicationSend page views on route changesKeeps page and engagement data accurate
Server-side taggingPreserve the client and session IDsAvoids broken or duplicated sessions
Session configuration decisions

Validation should combine debug views, raw event exports and spot checks of real journeys. A sudden rise in sessions with the source set to the own domain or a payment provider is a reliable sign of a broken cross-domain setup.

Limitations and common mistakes

Session data is an approximation of human visits, and several factors distort it. Analysts should treat session counts as estimates with known biases rather than exact visitor tallies.

  • Consent and blocking: when visitors decline cookies or run blockers, sessions are lost or only modeled, which lowers counts in privacy-focused markets.
  • Bots and crawlers: automated traffic that executes scripts inflates sessions and lowers engagement rates.
  • Cookie expiry: browser limits on cookie lifetime split one person into several users, though each visit still forms a session.
  • Tool differences: comparing sessions from two analytics platforms without aligning timeout and source rules produces misleading gaps.
  • Sampling and thresholds: reports on large ranges may be sampled or hide rows, so exported raw data gives more reliable session totals.

In plain words

A session is one visit to a website or app. Think of a shop that counts each trip through its door: you walk in, look at a few shelves, maybe buy something, and leave. That trip is one session.

If you step out for a long coffee break and come back later, the shop counts a second visit. Analytics tools do the same, usually after 30 minutes without activity. The key point is that a session is a counting rule, so different tools can count the same visits differently.

A real-world example

An online furniture retailer runs a spring campaign with UTM-tagged email links and paid social ads. After launch, the marketing team sees email sessions rise by about 40 percent, yet revenue from email barely moves. A closer look at the session reports shows many new sessions from the payment provider’s domain, each starting just before the purchase confirmation.

The analyst finds that the hosted checkout was not listed as an unwanted referral, so every returning buyer started a new session credited to the payment provider. After adding the referral exclusion and enabling cross-domain measurement, sessions drop to realistic levels, and revenue is once again attributed to the email and social campaigns. The corrected session conversion rate for email is roughly three times higher than the broken report suggested, which changes the next quarter’s budget split.