---
title: Interpret your User Sessions chart
description: Interpret the results of your User Sessions chart
product: analytics
token_estimate: 1857
---
# Interpret your User Sessions chart

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

The [User Sessions chart](https://amplitude.com/docs/analytics/charts/user-sessions/user-sessions-track-engagement-frequency) measures how frequently users start sessions, how long those sessions last, and how those metrics differ by user segment.

## Interpret your User Sessions chart

The results in User Sessions depend on the metrics you chose while [building your chart](https://amplitude.com/docs/analytics/charts/user-sessions/user-sessions-track-engagement-frequency), such as a count of sessions or a count of events.

The example below displays a daily count of sessions with at least one `Add to Cart` event for all users over the last 30 days. The chart also filters users by `Country` (United Kingdom).

**Figure: Daily sessions with an Add to Cart event (United Kingdom)**

Sessions with at least one Add to Cart event follow a weekly rhythm — a weekday plateau near 2,000 and weekend troughs near 800.

Line chart. X axis: Date. Y axis: Sessions. United Kingdom: values from 2026-03-18 onward cover an incomplete period and render dashed.

| Date | United Kingdom |
| --- | --- |
| 2026-02-18 | 1987 |
| 2026-02-19 | 2054 |
| 2026-02-20 | 1936 |
| 2026-02-21 | 2103 |
| 2026-02-22 | 1978 |
| 2026-02-23 | 743 |
| 2026-02-24 | 828 |
| 2026-02-25 | 1902 |
| 2026-02-26 | 2041 |
| 2026-02-27 | 1965 |
| 2026-02-28 | 2088 |
| 2026-03-01 | 1919 |
| 2026-03-02 | 767 |
| 2026-03-03 | 812 |
| 2026-03-04 | 1994 |
| 2026-03-05 | 2062 |
| 2026-03-06 | 1927 |
| 2026-03-07 | 2077 |
| 2026-03-08 | 1948 |
| 2026-03-09 | 726 |
| 2026-03-10 | 851 |
| 2026-03-11 | 1914 |
| 2026-03-12 | 1950 |
| 2026-03-13 | 2076 |
| 2026-03-14 | 2090 |
| 2026-03-15 | 1963 |
| 2026-03-16 | 705 |
| 2026-03-17 | 849 |
| 2026-03-18 | 1923 |
| 2026-03-19 | 1763 |

This view counts every session from UK users that includes at least one `Add to Cart` event, with one point per day. Read it left to right to see a weekly rhythm: sessions hold a weekday plateau around 2,000 and fall to weekend troughs near 700 to 800. The dashed segment at the right marks the most recent day, whose data is still incomplete, so treat that final point as provisional rather than a real drop.

The same chart with an added group segment by `Carrier` shows the segmented carriers as different colored lines.

**Figure: Daily sessions by carrier (United Kingdom)**

The same sessions split by carrier. Verizon leads, followed by AT&T, T-Mobile, and Sprint, and every carrier shares the same weekday-plateau, weekend-trough rhythm.

Line chart. X axis: Date. Y axis: Sessions. Verizon, AT&T, T-Mobile, Sprint: values from 2026-03-18 onward cover an incomplete period and render dashed.

| Date | Verizon | AT&T | T-Mobile | Sprint |
| --- | --- | --- | --- | --- |
| 2026-02-18 | 781 | 592 | 328 | 263 |
| 2026-02-19 | 796 | 614 | 341 | 278 |
| 2026-02-20 | 773 | 576 | 319 | 257 |
| 2026-02-21 | 807 | 643 | 359 | 294 |
| 2026-02-22 | 762 | 601 | 333 | 268 |
| 2026-02-23 | 281 | 221 | 121 | 99 |
| 2026-02-24 | 318 | 258 | 128 | 103 |
| 2026-02-25 | 788 | 588 | 322 | 261 |
| 2026-02-26 | 774 | 631 | 347 | 283 |
| 2026-02-27 | 802 | 607 | 336 | 271 |
| 2026-02-28 | 759 | 573 | 314 | 254 |
| 2026-03-01 | 791 | 619 | 344 | 279 |
| 2026-03-02 | 274 | 214 | 119 | 97 |
| 2026-03-03 | 339 | 249 | 123 | 102 |
| 2026-03-04 | 783 | 603 | 331 | 266 |
| 2026-03-05 | 797 | 627 | 352 | 288 |
| 2026-03-06 | 768 | 581 | 318 | 258 |
| 2026-03-07 | 809 | 641 | 361 | 296 |
| 2026-03-08 | 751 | 596 | 329 | 264 |
| 2026-03-09 | 286 | 218 | 117 | 96 |
| 2026-03-10 | 347 | 263 | 126 | 104 |
| 2026-03-11 | 780 | 568 | 305 | 261 |
| 2026-03-12 | 767 | 581 | 334 | 268 |
| 2026-03-13 | 755 | 640 | 372 | 309 |
| 2026-03-14 | 807 | 650 | 338 | 295 |
| 2026-03-15 | 771 | 613 | 347 | 232 |
| 2026-03-16 | 274 | 214 | 119 | 98 |
| 2026-03-17 | 352 | 269 | 124 | 104 |
| 2026-03-18 | 771 | 571 | 332 | 249 |
| 2026-03-19 | 734 | 516 | 292 | 221 |

Each line tracks the same session count for one `Carrier`, which lets you compare segments at a glance. The carriers hold the same rank all month: Verizon sits highest, followed by AT&T, T-Mobile, then Sprint. Because every line dips together on weekends and none of them cross, the differences between carriers are proportional rather than a sign that one segment is overtaking another.

### The data table

A table of session or event data appears below the chart. To specify which segments to see in the graph, click a segment name in the [breakdown table](https://amplitude.com/docs/analytics/charts/review-chart-data). To download the table, click **Export CSV**.

Using the example above, Amplitude segments the breakdown table's results by `Carrier`.

![userSessionsBreakdownTable.png](https://amplitude.com/docs/images/user-sessions/usersessionsbreakdowntable-png.png)

> **Note:**
>
> Amplitude counts users as `(none)` if the segmented property values aren't available when the events trigger. [Read more about `(none)` or unexpected values in this FAQ article](https://help.amplitude.com/hc/en-us/articles/360016257391#Event-Properties).

## The three ways Amplitude records sessions

Amplitude records sessions on either the server side or the client side. Client-side sessions can be either mobile or web.

- **Server side**: Use the HTTP API v2 to track sessions on the server side by including a value in the `session_id` field. The `session_id` value is the number of milliseconds since epoch, counting from the start of the session.
- **Client side (mobile)**: When you use Amplitude's mobile SDKs, events triggered within 5 minutes of each other count toward the current session by default. The time of the first event marks the session's start time, and the last event triggered marks the end time. For example, an 'Open App' event can mark the first event. Amplitude counts events sent within five minutes of each other toward the current session.
- **Client side (web)**: When you use Amplitude's JavaScript SDK, events triggered within 30 minutes of each other count toward the current session by default. The time of the first event marks the session's start time, and the last event triggered marks the end time.

You can also define a session without instrumenting your events first, by setting a [custom session property](https://amplitude.com/docs/data/sources/instrument-track-sessions).

> **Note:**
>
> The User Sessions chart only displays data if you send a session ID with your events. Amplitude's SDKs handle this automatically, unless you flag an event as out-of-session (assigning the session ID a value of `-1`). If you're using Amplitude's HTTP API, you must explicitly send a `session_id` with your events.

## How filtering works in the User Sessions chart

Filtering events for the User Sessions chart is a multi-step process. The order of those steps matters.

First, Amplitude filters for events that match the property filters. Amplitude then takes those events and groups them into sessions, which lets Amplitude calculate session length and count events performed each session.

Property filters apply before session filters. Amplitude filters on raw events first, then on the filtered events.

Amplitude only considers events with property filters when computing session length.