At a glance
This card breaks your Microsoft Clarity sessions down by visitor country over the last 30 days. It shows where your shoppers are actually browsing from, which helps you match marketing spend, currency, shipping, and language to real demand. Unexpected spikes from one region can also be an early hint of bot activity or a campaign overshooting its target market.
| What it counts | The number of tracked sessions grouped by the visitor’s country over the window. |
| Sample type | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| Why it matters | Knowing where shoppers come from lets you align spend, currency, and shipping with real demand. |
| Reading the value | Read it as a distribution; growth in a target market is good, while an odd surge in an unexpected country may need investigation. |
| Currency | count |
| Time window | 30D |
| Alert trigger | - |
| Sentiment key | clr_country_split |
| Roles | owner, marketing |
Calculation
Microsoft Clarity attributes each recorded session to a visitor country as it captures traffic. Vortex IQ groups the session count by country over the window so you can see the geographic split at a glance. See the At a glance table for the time window, and the worked example below for how it reads in practice.Worked example
A representative reading of Sessions by Country for a typical merchant on Microsoft Clarity. A UK-focused store sees its usual split of roughly 70% United Kingdom and 15% Ireland, then notices a new 12% slice from a country it does not ship to. The merchant opens Vortex Mind to trace the surge upstream and links it to a broad-match ad campaign. They ask Ask Viq “which campaign is driving sessions from outside our shipping regions?” in plain English, then refine geo-targeting so spend follows the markets they can actually serve.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_sessions_by_device | Pairs the country split with the device split for a fuller audience view. |
clr_bot_traffic_pct | Helps explain a sudden surge from one region as possible bot traffic. |
clr_sessions_captured | The total session count this card distributes by country. |
session_source_vs_ecom_revenue_attribution | Ties regional sessions back to revenue contribution. |
clr_top_pages_by_sessions | Shows which pages each market lands on most. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Open the Clarity Dashboard and review the country or geography breakdown within the session insights. Confirm the period and any device or channel filters 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. |