Tracking Gap (session count collapsed), Microsoft Clarity

Tracking Gap (session count collapsed) for Microsoft Clarity stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Nerve Centre

At a glance

This real-time alert fires when your Microsoft Clarity session count drops sharply against its recent 7-day baseline. A sudden collapse almost always means the Clarity tracking tag has broken, been removed, or stopped firing, rather than that real traffic vanished overnight. Catching this fast protects the behavioural data the rest of your Clarity cards depend on.

What it counts	The shortfall in recorded sessions once the count drops past the collapse trigger relative to the 7-day baseline.
Sample type	Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh.
Why it matters	A tracking gap quietly blinds every other Clarity metric, so behavioural insight stops arriving until it is fixed.
Reading the value	A non-zero or rising value means sessions have collapsed and tracking is likely broken; zero means session capture looks healthy.
Currency	count
Time window	RT
Alert trigger	session count down >25% vs 7D baseline
Sentiment key	clr_alert_tracking_broken
Roles	owner, marketing

Calculation

Microsoft Clarity records a session count as it captures heatmaps and recordings. Vortex IQ compares the current count against the trailing 7-day baseline and raises this alert when sessions fall past the collapse trigger, which typically points to a broken or missing tracking tag rather than a genuine traffic drop. See the At a glance table for the trigger and time window, and the worked example below for how it reads in practice.

Worked example

A representative reading of Tracking Gap (session count collapsed) for a typical merchant on Microsoft Clarity. A store normally records around 5,000 Clarity sessions a day. After a deploy, the daily count falls to roughly 300 and this alert fires the same morning. The merchant opens Vortex Mind to trace the collapse upstream and finds the Clarity script was dropped from the theme during the deploy. They restore the tag, then ask Ask Viq “are Clarity sessions back to last week’s level yet?” in plain English to confirm capture has recovered before trusting the other cards again.

Sibling cards merchants should reference together

Card	Why merchants reach for it
clr_sessions_captured	The session capture count this alert watches for a collapse.
clr_bot_traffic_pct	Rules out a bot-filtering shift as the cause of a session swing.
clr_alert_event_volume_drop	Confirms whether signal volume moved with the session count.
clr_top_pages_by_sessions	Shows whether the gap hits all pages or just a few.
clr_javascript_errors	JavaScript errors that can stop the tracking tag firing.

Reconciling against Microsoft Clarity

Where to look in Microsoft Clarity’s own dashboard:

Open the Clarity Dashboard and check the session count trend, then confirm the tracking tag is reporting under your project’s setup. 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.

Cross-connector reconciliation: complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does Tracking Gap (session count collapsed) update? The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard.

Q: Why does my Microsoft Clarity dashboard show a different number? Clarity may sample sessions on high-traffic sites and filters bots automatically, so its session count can differ from the Vortex IQ baseline. Period boundaries and any device or channel filters in your profile also shift the total. Match those settings before assuming a real divergence.

Q: Could a genuine traffic drop trigger this instead of a broken tag? Yes, a real fall in visitors, for example after a campaign ends or a site outage, can also collapse the session count. The alert flags the drop; use Vortex Mind and your analytics connector to confirm whether the cause is lost traffic or lost tracking.

Q: Can I customise the alert threshold? Yes, alert thresholds are configurable per profile in the Alert Rules tab. Adjust to match your business baseline rather than relying on the generic default.

---

Tracked live in Vortex IQ Nerve Centre

Tracking Gap (session count collapsed) is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Clarity and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.