At a glance
Sessions by Device shows how your Clarity-tracked sessions split across desktop, mobile, and tablet. Microsoft Clarity records every session it captures and tags the device, so this card gives you a quick read on where your audience actually browses. If most sessions are mobile but your frustration signals also concentrate there, you know where to focus your next round of fixes.
| What it counts | The number of Clarity-captured sessions broken down by device category (desktop, mobile, tablet). |
| Sample type | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| Why it matters | It tells you which devices drive your traffic so you can prioritise UX and conversion work where it lands. |
| Reading the value | A growing mobile share signals your experience must be mobile-first; a sudden swing can flag a tracking or campaign change. |
| Currency | count |
| Time window | 30D |
| Alert trigger | - |
| Sentiment key | clr_device_split |
| Roles | owner, marketing |
Calculation
Microsoft Clarity classifies each captured session by the device used to browse, then totals sessions within each category over the selected window. Vortex IQ reads those device-tagged session counts and renders the split. See At a glance for the time window and the worked example below for a typical reading.Worked example
A representative reading of Sessions by Device for a typical merchant on Microsoft Clarity. Over the last 30 days a store captured 42,000 sessions: 27,300 mobile (65%), 12,600 desktop (30%), and 2,100 tablet (5%). The merchant noticed mobile had climbed from 55% a quarter earlier, so they used Vortex Mind to trace whether the shift came from a new social campaign or a tracking change, then asked Ask Viq in plain English to compare frustration signals by device to decide where to invest first.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_sessions_captured | Confirms the total session base this split divides up. |
clr_sessions_by_country | Pairs device mix with geography for audience targeting. |
clr_rage_click_pct | Shows whether frustration concentrates on a particular device. |
clr_quick_back_rate | Reveals device-specific landing mismatch when paired with the split. |
clr_health_score | Frames the device picture against overall UX health. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Open the Clarity Dashboard insights and review the device breakdown, or apply device filters in the recordings and heatmaps views. Confirm the period and any filters match the Vortex IQ profile before comparing. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses rolling windows by default; Clarity may use calendar periods. | Variable | Match the period range. |
| Sampling. Clarity may sample sessions on high-traffic sites; Vortex IQ reads what Clarity exposes. | Variable | Allow for sampling on busy stores. |
| Filter scope. Profile-level filters (device, channel, bot exclusion) may narrow the Vortex IQ view. | Variable | Match filter settings. |