MWM
Contact salesMWM AI
Analytics & Retention

App Session

Also known asSessionUser SessionUsage Session

A single period of continuous user activity in an app, from open to close (or background past an inactivity timeout) — the atomic unit on which most engagement metrics are built.

Key takeaways

  1. 01An app session is one continuous period of use — from foreground to background after an inactivity timeout (commonly 30 seconds).
  2. 02It's the atomic unit underneath session length, session frequency, and time-in-app metrics.
  3. 03The timeout definition matters: change it and every session-based metric shifts, so consistency is critical.
  4. 04Sessions roll up into engagement KPIs — sessions per user, session duration, and stickiness (DAU/MAU).

An app session is a single, continuous period of user activity — from the moment the app is opened (foregrounded) until it's closed or backgrounded beyond an inactivity timeout. It's the atomic event of engagement analytics: nearly every behavioral KPI ([[session-length]], [[session-frequency]], time-in-app, [[stickiness]]) is computed by aggregating sessions.

How a session is bounded

A session starts on foreground and ends when the app is backgrounded for longer than an inactivity timeout — the industry-standard default is 30 seconds. If the user briefly leaves (checks a notification) and returns within the timeout, it counts as the same session; longer than that, the next foreground starts a new session. This timeout is a configurable definition, and that's the catch: change the timeout and your session counts, average [[session-length]], and sessions-per-user all move — so it must be held constant for trends to be comparable.

Why the session is foundational. Sessions aggregate upward into the metrics teams actually steer on: sessions per active user (frequency), average duration (length), and total time-in-app. Together with active-user counts they feed [[dau-mau]] stickiness and [[retention]] analysis. Because everything depends on the session definition, mature analytics setups document their timeout and never change it casually — a definition change silently rewrites historical engagement trends.

Quick answers

What is an app session?

An app session is one continuous period of user activity, from when the app is opened until it's closed or backgrounded past an inactivity timeout (commonly 30 seconds). It's the basic unit of engagement measurement — session length, session frequency, and time-in-app are all built by aggregating sessions.

How is a session boundary determined?

A session begins when the app is foregrounded and ends after it's been backgrounded longer than the inactivity timeout — typically 30 seconds. Brief interruptions within the timeout keep the same session; longer gaps start a new one on the next open. The exact timeout is configurable, so it must stay consistent for metrics to be comparable over time.

Why does the session definition matter?

Because every session-based metric depends on it. If you change the inactivity timeout, session counts, average session length, and sessions-per-user all shift — without any real change in user behavior. That's why analytics teams document their session definition and avoid changing it, since a change silently breaks historical engagement comparisons.

Next reads

Back to glossary