At a glance
Clarity Session Outcome vs Ecom Conversion places the success of sessions observed in Microsoft Clarity side by side with the conversion rate your ecommerce platform actually records. When healthy-looking Clarity sessions are not turning into the orders your store reports, the gap points to friction or tracking problems between behaviour and checkout. For merchants, it is an early warning that revenue is leaking somewhere between intent and purchase.
| What it counts | Clarity-observed session success measured against the ecommerce platform’s recorded conversion rate over the window. |
| Sample type | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| Why it matters | A widening gap between observed session quality and recorded conversion flags friction, drop-off, or tracking loss before revenue reports do. |
| Reading the value | Closely tracking lines are healthy; a growing divergence means behaviour and conversion are telling different stories. |
| Currency | percent |
| Time window | 30D |
| Alert trigger | >10pp divergence vs platform |
| Sentiment key | clr_xc_funnel_vs_ecom_conversion |
| Roles | owner, marketing |
Calculation
Vortex IQ pairs the session outcome signal that Microsoft Clarity exposes from behavioural data with the conversion rate recorded by your ecommerce platform, then plots both on a dual axis over the selected window so divergence is visible at a glance. The Clarity side reflects observed session success; the conversion side comes from your store platform, not Clarity. See At a glance for the headline definition and the worked example below for a representative reading.Worked example
A representative reading of Clarity Session Outcome vs Ecom Conversion for a typical merchant on Microsoft Clarity. Over the 30 days to 12 Mar 26, Clarity-observed session success might hold steady around 6% while your platform conversion rate slides to 3.5%, a divergence past the alert threshold. That gap suggests sessions look successful in behaviour terms but orders are not completing, perhaps due to a broken payment step or lost conversion tracking. Use Vortex Mind to trace the divergence to the affected step, then ask Ask Viq in plain English which device or channel widened the gap most.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_xc_session_quality_vs_cart_abandonment | Shows whether the conversion gap coincides with frustration signals around the cart. |
clr_xc_landing_page_perf_vs_bounce | Checks whether slow or quick-back landing pages are starving the funnel before conversion. |
clr_xc_traffic_source_vs_revenue | Reveals which sources drive sessions that do or do not turn into recorded revenue. |
clr_session_conversion_rate | The Clarity-side conversion view that this card compares against the platform figure. |
clr_javascript_errors_detected | Script errors are a common cause of healthy sessions failing to convert or report. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Review the Dashboard insights and session recordings for the period to confirm the Clarity-observed outcome side, but note the ecommerce conversion figure comes from your store platform’s own reporting, not Clarity. Confirm the period and any device, channel, or bot 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. |