Session fragmentation and inflation
A session is meant to represent one continuous visit, but several rules can split one journey into many. A timeout during a pause, a campaign parameter mid-visit, crossing midnight, or a self-referral each starts a fresh session. The result inflates session counts and shrinks per-session metrics. This page explains the fragmentation rules and how to read counts affected by them.
What restarts a session
Tools end and restart sessions on several triggers. A period of inactivity beyond the timeout ends the session, so a visitor who pauses then resumes is counted twice. Arriving with new campaign parameters can force a new session to credit the campaign. Crossing the reporting day boundary at midnight can split a session. And a self-referral mid-journey starts a fresh, re-attributed session.
Each trigger turns one human visit into more than one session row.
- Inactivity past the timeout ends the session
- New campaign parameters can start a session
- Midnight in the reporting time zone can split it
- Self-referrals re-attribute and restart sessions
Reading and reducing fragmentation
Expect sessions to exceed visitors and per-session averages to fall when fragmentation is high. Reduce avoidable splits: do not re-tag visitors already on your site with campaign parameters, fix self-referrals, and be aware of the midnight boundary when reading long evening sessions. For journey questions, analyse user-level paths rather than leaning on session counts alone.
How it appears in analytics and logs
Session counts well above visitor counts, with thin per-session engagement, often means single visits are being split into multiple sessions.
Diagnostic use case
Interpret inflated session counts and low per-session metrics as fragmentation artefacts, and reduce avoidable splits like mid-visit re-tagging.
What WebmasterID can help detect
WebmasterID records the underlying events with timestamps, so you can see how a tool's session rules split a continuous journey and reconcile the counts.
Common mistakes
- Reading inflated sessions as more visits than really occurred.
- Re-tagging on-site visitors and forcing new sessions.
- Ignoring the midnight split when reading long sessions.
Privacy and accuracy notes
Session boundaries are derived from timing and campaign fields, not from visitor identity. No personal data is needed to analyse fragmentation.
Related pages
- Self-referrals and lost attribution
A self-referral is when your own site shows up as a referring source in your reports. It usually means a session was broken and a new one started attributed to your domain, often when a visitor crosses subdomains or returns from a payment provider. Self-referrals fragment sessions and steal credit from the real source. This page explains the causes and the fix.
- Time-zone mismatches in reporting
Every analytics property reports against a configured time zone, and it decides which calendar day each hit belongs to. A wrong zone shifts your daily curve; two tools on different zones never match day-to-day; and daylight-saving changes create a short or doubled hour. This page explains how the reporting time zone shapes data and the artefacts to expect.
- Why two analytics tools disagree
It is normal for two analytics tools to report different numbers for the same site. The differences are structural, not bugs: each tool defines a session differently, filters bots differently, samples or does not, attributes on different windows, and fires its tag at a different moment. This page explains the recurring causes and how to reconcile them.
- Web analytics
Reconcile session counts against underlying events.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.