At a glance
Avg Page Engagement Time is the average active time, in seconds, that a visitor spends genuinely engaged on a page, as measured by Microsoft Clarity. It is distinct from total session duration because it focuses on active attention rather than idle time on a tab. Watching it move tells you whether your content is holding interest or losing it.
| What it counts | The average active engagement time, in seconds, per page across Clarity-captured sessions. |
| Sample type | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| Why it matters | Active engagement time reflects how well content holds attention, which underpins conversion. |
| Reading the value | Higher usually means stronger engagement, but read it with intent: very long times on a checkout step can signal friction. |
| Currency | count |
| Time window | 30D vsP |
| Alert trigger | - |
| Sentiment key | clr_page_engagement_time |
| Roles | owner, marketing |
Calculation
Microsoft Clarity measures the active engaged time within each captured session, separating it from periods when the page is idle or backgrounded, then averages it per page over the window. Vortex IQ reads that average in seconds and compares it to the prior period. See At a glance for the time window and the worked example below for a typical reading.Worked example
A representative reading of Avg Page Engagement Time for a typical merchant on Microsoft Clarity. A product page averaged 38 seconds of engagement, up from 31 the prior 30 days, suggesting a new description was holding attention better. On the checkout page, however, engagement time climbed from 22 to 55 seconds, which the merchant read as a warning rather than a win. They used Vortex Mind to trace the checkout slowdown to a sluggish address lookup, then asked Ask Viq in plain English to compare engagement against conversion to confirm the friction.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_avg_scroll_depth | Pairs time on page with how far visitors read. |
clr_quick_back_rate | Low engagement often coincides with quick exits. |
clr_top_pages_by_sessions | Identifies which high-traffic pages drive engagement. |
clr_pages_per_session | Frames per-page engagement against overall depth of visit. |
clr_health_score | Sets engagement in the context of overall UX health. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Open the Clarity Dashboard insights for engagement and time-related metrics, or review per-page behaviour in heatmaps and recordings. Confirm the period and filter settings match the Vortex IQ profile. 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. |