Dash0 Raises $110M Series B at $1B Valuation

Last updated: March 14, 2026

Investigate Sessions

The Sessions tab lists every user session recorded for a website within the selected time window.

Use it to understand session volume trends, identify users who encountered errors, filter sessions to a specific page or deployment, and open the full session detail to follow a user's exact journey through your application.

DDash0 Websites Sessions tab showing the New session count chart, Bounce rate chart, and the sessions list with User, Start, System, Country, Errors count, and Page view count columns

Use the Session Summary Charts

Above the session list, two charts provide an aggregated view of session behaviour over the selected time window:

  • New session count — a bar chart showing how many new sessions were started in each time bucket. Useful for detecting traffic patterns, deployment-driven spikes, or suspicious bot activity.
  • Bounce rate — a line chart showing the percentage of sessions where the user left without a second interaction. A rising bounce rate after a deployment is an early signal that something may have broken on the landing page.

Switch the chart type using the Session metrics / None toggle to focus on the raw session count chart, the session metrics charts, or hide the charts entirely.

Use the Sessions List

The sessions table lists individual sessions with the following columns:

ColumnDescription
UserThe identified user's name and email, or "No user details" for anonymous sessions
Start (duration)When the session started and whether it is still ongoing or has ended
SystemOperating system, browser name and version, and screen resolution
CountryThe user's geographic location
Errors countNumber of unhandled JavaScript errors recorded during the session — highlighted in red if non-zero
Page view countTotal number of page loads and SPA navigations in the session

Sessions with at least one error are marked with a red left border, making them immediately visible when scanning for problematic sessions.

Filter Sessions

Use the search bar (⌘F) to filter sessions by any attribute. Common filters include:

FilterExampleUse case
page.url.path= /cartShow only sessions that visited the cart page
http.status_code>= 400Show sessions that encountered backend errors
session.country= USFilter to a specific geography
browser.name= FirefoxIsolate a specific browser

The session count in the top bar updates immediately to show how many sessions match the current filter (e.g. "Showing 32 of 361 sessions").

Dash0 Websites Sessions tab filtered by page.url.path = /6E92ZMYYFZ, showing 32 of 361 sessions, with Reed Haag's session selected and the detail panel open on the right

Use the Session Detail Panel

Click any session row to open the detail panel on the right. The panel contains:

Summary

The user's name, email, operating system, browser, screen resolution, geographic location, and the session start time and duration.

Events

A list of events from this session that match the current search filter — showing the event type badge and a human-readable title (e.g. "LCP measured at 49 ms", "Finished loading after 100 ms"). Click See all events to open the full event list in the Web Events explorer.

Page flow

A compact timeline of the pages visited during the session, with the time spent on each page and any tab switches indicated. The page flow makes it possible to reconstruct exactly what the user did — including how they navigated between tabs — without needing to watch a video replay.

Switching between tabs within the same session is tracked and shown inline in the flow, so you can see when a user opened a new tab, what they loaded there, and when they switched back.

View the Full Session

Click View full session in the detail panel to open a complete, chronological event-by-event view of the session in the Web Events explorer.

This shows every browser.page_view, browser.request, browser.web_vital, browser.error, and custom event that occurred during the session — with full timing, payloads, and links to backend traces.