Metric

Session Length

Glossary Term

Metric

Session Length

Glossary Term

Metric

Session Length

Glossary Term

What is session length?

Session Length is the average amount of time a user spends in an app during a single session. It is a core engagement signal that tends to move with retention and monetization, and it is most useful read alongside how often users open the app.

What is session length?

Session Length is the average amount of time a user spends in an app during a single session. It is a core engagement signal that tends to move with retention and monetization, and it is most useful read alongside how often users open the app.

What is session length?

Session Length is the average amount of time a user spends in an app during a single session. It is a core engagement signal that tends to move with retention and monetization, and it is most useful read alongside how often users open the app.

Session length is one of the simplest engagement measures a publisher tracks: on average, how long does a user stay in the app once they open it? On its own it is just a duration, but as part of a set of Engagement Metrics it says a lot about whether an app is holding attention. Longer sessions usually mean users are finding something worth their time, which tends to line up with stronger retention and more chances to monetize.

How to calculate session length

Average session length = Total session duration / Number of sessions
Average session length = Total session duration / Number of sessions
Average session length = Total session duration / Number of sessions

A session starts when a user opens the app and ends when they leave or go idle past a set timeout. Add up the duration of every session over a period, divide by the number of sessions in that period, and you get the average session length. Analytics tools usually report it automatically, but the formula is worth knowing so you understand what the number includes.

A worked example

Say an app records 50,000 sessions in a day, and the total time across all of them adds up to 250,000 minutes:

250,000 minutes / 50,000 sessions = 5 minutes per session
250,000 minutes / 50,000 sessions = 5 minutes per session
250,000 minutes / 50,000 sessions = 5 minutes per session

If a new feature raises total time to 325,000 minutes across the same 50,000 sessions:

325,000 minutes / 50,000 sessions = 6.5 minutes per session
325,000 minutes / 50,000 sessions = 6.5 minutes per session
325,000 minutes / 50,000 sessions = 6.5 minutes per session

The same number of sessions now holds users for ninety seconds longer each, a sign the feature gave them a reason to stay.

Read it alongside session frequency

Session length answers how long, while session frequency answers how often. The two can move in opposite directions. An app people open many times a day for quick checks may have short sessions but very high engagement, while an app opened once for a long stretch shows the reverse. Reading length next to frequency, and next to DAU (Daily Active Users), keeps you from over-reading either number. A drop in length is only worrying once you know whether visits also became less frequent.

Why session length matters

Time in the app is the raw material for both engagement and revenue. Longer, satisfying sessions correlate with stronger Retention Rate and give ad-supported apps more impressions to serve and more moments to present offers. They also feed broader health measures like Stickiness (DAU/MAU Ratio), since users who stay longer tend to come back more. The goal is not maximum time at any cost, though. Time that comes from confusion or friction is not the same as time users choose to spend.

How offerwalls affect session length

An offerwall gives users a reason to stay a little longer. Browsing the list of available offers, choosing one, and completing it all happen inside the app, which extends the session rather than ending it. For users who are not ready to make a purchase, it turns idle moments into engaged ones and adds a second reason to keep the app open beyond its core content. Used well, it lengthens sessions in a way users welcome, because they are getting a reward for the time they spend.

Common mistakes to avoid

  • Treating longer sessions as always better. Time spent stuck or lost is a problem, not a win, so pair the metric with satisfaction and retention.

  • Ignoring session frequency. A short average session can be perfectly healthy if users return many times a day.

  • Comparing raw averages across very different apps. A utility opened for seconds and a game played for an hour cannot be judged by the same benchmark.

Frequently asked questions

Q: What is a good session length?

A: It depends entirely on the app category, so there is no universal target. A quick utility and an immersive game have very different healthy ranges, which is why your own trend over time matters more than any benchmark.

Q: How is session length different from session frequency?

A: Session length measures how long each visit lasts, while session frequency measures how often users open the app. Read together, and alongside DAU (Daily Active Users), they describe engagement far better than either alone.

Q: Does longer session length increase revenue?

A: Often, because more time means more ad impressions and more chances to present offers, which supports Retention Rate as well. The time has to come from genuine engagement rather than friction, though.