How Amplitude calculates session length

Feature Experiment Web Experiment

SDKs APIs

Overview of Amplitude Data Getting set up with Amplitude Data Autocapture Visual Labeling Data structure video walkthrough Debug with the Amplitude Chrome extension Manage your Amplitude Data settings Data backfill

Plan your taxonomy Planning and instrumentation workflow Create a tracking plan Work with branches Ampli and developer tools Monitor your data with observe Protect your schema from unexpected data Integrate Jira with Amplitude Data

About user properties and event properties Event and property descriptions Event and property display names Event categorization Set an event's activity status Property types IP address and location properties Override a property definition Revert an overridden property definition Using property groups Cross-project analysis with Portfolios

Organize your tracking plan with Data Assistant Remove invalid or incorrect data Block bot web traffic Change the description of an event or property Fix your data with transformations Time to Live (TTL)

Custom events Object management Derived properties Lookup Tables Channels

Warehouse-native Amplitude: Overview Build a warehouse-native data model Warehouse-native Amplitude: Best Practices Warehouse Native Bulk Model Management

Amplitude Audiences overview

Recommendations: Help users reach the goals you've set for them

Build a recommendation

Use recommendations in personalization campaigns

Predictions: Use Amplitude's AI to help maximize lift

Build a prediction

Use recommendations in personalization campaigns

Sync to third-party destinations

Source catalog

Connect to a source

Understand the data differences between Amplitude, Snowflake, and the Export API

Profiles

Amplitude Wordpress plugin

Converter configuration reference

Destination catalog

Connect to a Destination

Destination event streaming overview

Client-side vs Server-side

Streaming transformations

Data

Amplitude Sources

How Amplitude calculates session length

Amplitude calculates session length via the following formula when session ID is used as the session property:

1*max(client\_event\_time) - min(client\_event\_time)*

Where:

client_event_time is the local timestamp (UTC) when the device logged the event
max(client_event_time) is the local timestamp (UTC) of the last event logged by the device

Additionally, hidden, inactive, and deleted events will not be included in the session length calculation. For example, let's say you have the following series of events:

Event A --> Event B --> Event C --> Event D

If Event C and Event D are hidden, inactive, or deleted, then the max(client_event_time) is taken from Event B instead of Event D.

Read more about how Amplitude tracks sessions in this help center article.

Was this page helpful?

Thanks for your feedback!

October 29th, 2024

Need help? Contact Support

Visit Amplitude.com

Have a look at the Amplitude Blog

Learn more at Amplitude Academy