Last updated: May 13, 2026
Filter Sessions and Data
The Websites Explorer filter bar lets you narrow data across the Overview, Web Vitals, and Sessions tabs to focus on specific user segments, pages, deployments, or geographic regions.
This guide covers website-specific filtering: which attributes are available, how filters apply to each tab, and common filtering scenarios. For general filtering UI mechanics (pinning, copying, resolving conflicts, keyboard shortcuts), see Filtering.
Available Filtering Attributes
The following OpenTelemetry semantic convention attributes are commonly available for filtering:
| Attribute | Example Value | Description |
|---|---|---|
deployment.environment.name | production | Environment (production, staging, development) |
deployment.id | abc123 | Unique deployment identifier (commit SHA, build number) |
deployment.name | main | Deployment name (main, preview branches) |
geo.country.iso_code | US | Country code (ISO 3166-1 alpha-2) |
http.response.status_code | 404 | HTTP response status codes |
page.url.path | /checkout | URL path of the page |
service.name | my-website | Service name set during SDK initialization |
service.version | 1.2.3 | Service version |
user_agent.name | Firefox | Browser name (Chrome, Firefox, Safari) |
You can also filter by any custom attributes you've added via additionalSignalAttributes or addSignalAttribute().
How Filters Apply by Tab
Filters apply differently depending on which tab you're viewing:
- Overview tab — affects traffic KPIs, web vital gauges, pages chart, and geography map.
- Web Vitals tab — affects p75 gauges, performance charts, and pages tables.
- Sessions tab — affects session list and summary charts. Use the search bar (
⌘F) to filter sessions. The session count updates immediately (e.g. "Showing 32 of 361 sessions").
Common Filtering Scenarios
Here are examples of how to combine filters to answer specific questions about your website's performance and user behavior.
- Compare deployments — Filter by
deployment.name=mainfor one time window, then switch to a feature branch to see if metrics improved. - Identify browser issues — Filter by
user_agent.nameto isolate browser-specific performance problems. - Investigate errors — Combine filters like
page.url.path=/checkoutANDhttp.response.status_code>= 400 to find sessions with errors on specific pages. - Analyze regional performance — Filter by
geo.country.iso_codeto understand country-specific patterns.
Further Reading
- Monitor Website Overview. Overview tab with traffic KPIs, web vital gauges, and geography map affected by filters.
- Analyze Web Vitals. Web Vitals tab with p75 scores and performance charts that respond to filtering.
- Investigate Sessions. Sessions tab for browsing and filtering individual user sessions.
- Set Up the Web SDK. Configure deployment attributes that enable filtering by environment, deployment name, and deployment ID.
- Filtering. Complete guide to filtering in Dash0, including pinning, copying, and resolving conflicts.