One-Line Definition
A session is a single continuous period of interaction between a user and a website or app — it starts when the user arrives, and it ends when they leave or stay inactive past a defined timeout (typically 30 minutes).
Real-Life Analogy
Think of a session like a single visit to a physical store.
You walk in the door (session starts). You browse aisles, pick up products, ask a staff member a question, and maybe try something on. If you walk out and come back five minutes later, that's a new visit — a new session. But if you're inside the store the whole time, wandering between departments, it's still one visit, no matter how many things you look at.
The "timeout" rule matters here too. If you sit in the store's café for two hours without moving, most analytics tools would consider your visit "over" after 30 minutes of inactivity — and if you then get up and shop again, that counts as a brand-new session.
Core Formula
At its simplest:
Session = [First interaction] → [Activity] → [30 min of inactivity OR browser close]
In practice, most analytics platforms (GA4, Adobe Analytics, Mixpanel) apply two rules:
1. Inactivity timeout: A session ends after 30 minutes of no interaction by default.
2. Midnight reset: A session also ends at 11:59:59 PM in the property's timezone, even if the user is still active. A user browsing at 11:58 PM and continuing at 12:02 AM generates two sessions.
Some tools let you customize the timeout — e.g., 15 minutes for high-velocity news sites, or 60 minutes for B2B SaaS with long reading patterns.
Comparison with Related Terms
| Term | Definition | Key Difference from Session |
|---|---|---|
| **Session** | Continuous interaction period, ends on timeout or exit | The container for a visit |
| **Pageview** | A single page load within a session | Many pageviews can occur in one session |
| **User** | A unique person (identified by cookie, login, or device ID) | One user can generate many sessions over time |
| **Visit** | Often used interchangeably with session | "Visit" is the older term (Universal Analytics); GA4 standardized on "session" |
| **Event** | Any tracked action (click, scroll, purchase) | Events happen *inside* sessions |
| **Hit** | A single data send to the analytics server | Multiple hits make up a session |
Rule of thumb: Users contain sessions; sessions contain pageviews and events.
Use Cases
Sessions are one of the most versatile metrics in e-commerce analytics. Here's where they matter most:
1. Conversion rate calculation
Conversion rate = Conversions ÷ Sessions. If your store had 4,000 sessions last week and 120 purchases, your conversion rate is 3.0%. Tracking this by session (not by user) gives you a cleaner read on how well each visit performs.
2. Traffic source attribution
When a user lands from a Facebook ad, browses for 10 minutes, leaves, and returns two hours later via Google search — that's two sessions with two different sources. This lets you see which channel truly drives engagement, not just first-touch credit.
3. Engagement and bounce analysis
A "bounced session" is one with no meaningful interaction (in GA4, under 10 seconds and no conversion event). If 65% of your sessions bounce, your landing pages or ad targeting need work.
4. Funnel drop-off
Sessions reveal where users abandon: e.g., 1,000 sessions → 400 product views → 90 add-to-carts → 25 checkouts → 18 purchases. Each step is measured within the session container.
5. Session duration and pages per session
Average session duration of 2 minutes 45 seconds with 3.2 pages per session signals healthy browsing. A 20-second average with 1.1 pages signals a mismatch between ad promise and landing page.
6. Cross-border considerations
For DTC brands selling internationally, session data helps compare behavior across markets. A German shopper may average 4.1 pages per session while a US shopper averages 2.3 — same product, different research culture.
Misconceptions
❌ "One user = one session."
No. A single user can generate dozens of sessions per month. Someone who checks your site every morning for a week produces 7 sessions from 1 user.
❌ "A session ends when the browser tab closes."
Not exactly. Closing a tab *often* ends a session, but analytics tools primarily rely on the 30-minute inactivity rule. If a user closes a tab and reopens your site 5 minutes later, most tools still count it as the same session (depending on configuration).
❌ "Session duration is precise."
It's an estimate. If a user views one page and leaves, the tool has no "exit ping," so duration is recorded as 0 seconds. This is why single-page sessions drag down your average.
❌ "Sessions reset at midnight only if the user leaves."
Wrong. Sessions reset at midnight regardless of activity. A user reading a long article from 11:50 PM to 12:10 AM generates two sessions — one of 10 minutes, one of 10 minutes.
❌ "More sessions always means more growth."
Not necessarily. If sessions doubled but conversion rate dropped from 3% to 1%, you're attracting low-intent traffic. Sessions are a volume metric; pair them with quality metrics.
❌ "Session and visit are different things."
Functionally, they're the same. "Visit" was the Universal Analytics term; "session" is the GA4 and industry-standard term. Don't overthink the distinction.
Related Terms
- Session ID — A unique identifier assigned to each session, used to stitch events together.
- Session Duration — Total time from first to last interaction in a session.
- Bounce Rate — Percentage of sessions with no meaningful engagement.
- Pages per Session — Average pageviews within a single session.
- Session Timeout — The inactivity window (default 30 min) that closes a session.
- New User vs. Returning User — Defined at the user level, not the session level.
- Attribution Window — The lookback period (e.g., 30 or 90 days) across sessions for crediting conversions.
- Engaged Session — GA4's term for a session lasting 10+ seconds with a conversion or 2+ pageviews.
- Concurrent Sessions — Number of sessions happening at the same moment; critical for server capacity planning during flash sales.
Bottom line: A session is the fundamental unit of "a visit" in web analytics. Get it right, and every downstream metric — conversion rate, engagement, attribution — becomes more trustworthy. Get it wrong (by misconfiguring timeouts or ignoring midnight resets), and your entire reporting stack drifts.