Device & Technology

The Device & Technology dashboard shows what combination of browser, version, OS, device and screen size your users are on. This data turns directly into an actionable call for engineering and design: which environments to test and support, whether to design mobile-first or desktop-first, and which breakpoint is genuinely broken.

This dashboard splits into four key parts:

This part gives you the macro measures of your technical environment.

Imagine you open this dashboard first thing in the morning to know which environment to prioritize testing today; Users tells you the total audience size, and Target Environments tells you how many OS-by-browser combinations you need to cover to see 95% of them. Bounce Rate means something specific here: a rise on one particular device type or browser is a compatibility or UX signal in that environment. Top OS, Top Browser and Device Distribution together picture what your audience mostly sees the site through.

To see the full test matrix, click Target Environments — its download and QA-copy buttons turn it directly into a team task.

This part breaks down user behavior by screen size and orientation.

Imagine the frontend team wants to prioritize responsive design; Viewport Width Distribution shows your audience's real, live breakpoints. Initial Viewport marks the boundary of what users see without scrolling so you know where to place key content, and Screen Orientation tells you whether to build visual content for portrait or landscape.

This part gives you comparison and deeper-exploration tools.

• Comparison chart: switchable across four dimensions and two views, plotting only up to 5 rows ticked in the table below.
• Breakdown table: four tabs with an optional secondary dimension and a group-by-version switch. Anomaly tags may include end-of-life, bot signal and spoofed combo.
• Detail panel: opens on row click, showing trend over time, overall stats, the complementary dimension, version breakdown, location and user agent.

These tools help you examine the technical makeup of your incoming users as precisely as possible, and quickly spot a spoofed combo or a legacy version if one shows up in your traffic.

This part explains the technical framework and processing mechanics behind this report.

Knowing the rules of the game matters for sharper analysis; every detail is parsed from each request's User-Agent string, and traffic from identified bots is excluded from the calculations by default. Target environments and the test matrix are built from OS-by-browser combinations until coverage reaches 95%, and the list should always be tested top-down. The dominant-version percentage and the vulnerable-breakpoints status are both calculated relative to your own site's behavior.