> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Clarity on Vortex IQ > Monitor traffic, conversion and tracking integrity from Microsoft Clarity, and catch instrumentation breaks before decisions are made on bad data. Monitor traffic, conversion and tracking integrity from Microsoft Clarity, and catch instrumentation breaks before decisions are made on bad data. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) ยท [How connecting works](/integrations/connector-catalogue) | **25** | **11** | **Build your own** | **Ready to build yours** | **1** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 25 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher. | Signal | Outcome | Alert behaviour | What it tracks | | ---------------------------------------------- | ----------------------- | --------------- | -------------------------------------------------------------------------------------------------------- | | **Avg Scroll Depth %** | Catalogue quality | Merchant rule | Clarity-distinctive - average page scroll reach. Low = key content below the fold is missed. | | **Checkout-Path Frustration Signals** | Grow revenue | Merchant rule | Dead clicks / rage clicks on checkout-path pages - direct conversion blockers. | | **Checkout-Path Frustration Spike** | Customer experience | Merchant rule | Alerts for Checkout-Path Frustration Spike. | | **Dead Click Rate %** | Run operations | Merchant rule | Clarity-distinctive - % of sessions with a dead click. Rising = something looks clickable but isn't. | | **Frustration Signal Spike** | Customer experience | Merchant rule | Alerts for Frustration Signal Spike. | | **Landing Page Performance vs Quick-Back** | Protect revenue | Merchant rule | Landing Page Performance vs Quick-Back, broken down by row. | | **Quick-Back Rate %** | Run operations | Merchant rule | Clarity-distinctive - visitors who land then immediately go back. High = landing-page / intent mismatch. | | **Session Source vs Ecom Revenue Attribution** | Protect revenue | Merchant rule | Session Source vs Ecom Revenue Attribution, broken down by row. | | **Tracking Gap (session count collapsed)** | Control risk and change | Merchant rule | Alerts for Tracking Gap (session count collapsed). | | **Worst Scroll-Depth Pages** | Run operations | Watch only | Pages where visitors scroll least - content / layout reorder candidates. | | **Clarity Session Outcome vs Ecom Conversion** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Clarity UX Health Score** | Customer experience | Merchant rule | Description pending editorial review; the signal is live. | | **Frustration Signals vs Cart Abandonment** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Rage Click Rate %** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Sessions Captured** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Bot Traffic %** | Grow revenue | Merchant rule | Clarity flags suspected bot sessions - high share inflates every other metric. | | **Dead Click Hotspots (by page)** | Run operations | Watch only | Dead Click Hotspots (by page), broken down by row. | | **Excessive Scrolling Rate %** | Run operations | Merchant rule | Sessions with frantic scrolling - visitor can't find what they came for. | | **JavaScript Errors Detected** | Grow revenue | Merchant rule | Clarity surfaces JS errors observed during sessions - checkout-page errors are revenue blockers. | | **Sessions by Country** | Grow revenue | Watch only | Sessions by Country. | | **Sessions by Device** | Grow revenue | Watch only | Sessions by Device. | | **Top Pages by Sessions** | Run operations | Watch only | Top Pages by Sessions. | | **Avg Page Engagement Time** | Grow revenue | Watch only | Description pending editorial review; the signal is live. | | **Avg Session Duration** | Grow revenue | Watch only | Description pending editorial review; the signal is live. | | **Pages per Session** | Grow revenue | Watch only | Description pending editorial review; the signal is live. | ## Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. | Check | Severity | Outcome | Why it matters | Fix status | | ------------------------------------------------------------------------- | -------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **Key events not configured (purchase event firing but conversions = 0)** | critical | Grow revenue | The property has meaningful traffic but reports zero conversions, which almost never means zero sales; it means the tool cannot see the sales that are happening. Every conversion-based repor | Report only | | **API Credentials Invalid** | high | Control risk and change | With invalid credentials the tool has stopped collecting entirely; every metric that depends on it is silently stale. | Report only | | **Attribution divergence with ecommerce platform > 25% over 30d** | high | Protect revenue | Analytics showing conversions while the store records zero orders (or the reverse) means one of the two systems is wrong; every decision made on the divergent numbers is at risk. | Report only | | **Cart abandonment rate above 75%** | high | Protect revenue | Three out of four shoppers who add something to their cart leave without buying it. These are the closest prospects the store has, people who already decided they wanted a specific product, | Report only | | **Checkout-Path Frustration** | high | Grow revenue | Frustration signals on the checkout path are as close to watching lost sales happen as analytics gets; each cluster is a prioritised fix. | Report only | | **Session Capture Collapsed** | high | Control risk and change | A sharp drop in captured events or sessions usually means a tracking break after a site change, not a real traffic collapse; decisions made on the partial data will be wrong. | Report only | | **Session conversion rate below 1%** | high | Grow revenue | Fewer than 1 in 100 sessions convert. At this rate the store needs a large multiple of today's traffic just to hold revenue flat, so the most efficient lever right now is fixing conversion, | Report only | | **Average engagement time below 30 seconds** | medium | Grow revenue | Under 30 seconds of engaged time is barely enough to read a headline, let alone consider a product. Visitors this disengaged are unlikely to convert on this visit or return for another, so t | Report only | | **Bounce rate above 70% over 30d** | medium | Protect revenue | Seven in ten visitors are leaving after one page. Whatever is bringing them, an ad, a search result, a link, is not being matched by what they find when they arrive, and every one of those v | Report only | | **Dead-Click Concentration** | medium | Grow revenue | Dead clicks concentrated on specific elements mean shoppers believe something is clickable and it is not; each cluster is a small usability fix with real conversion upside. | Report only | | **Quick-Back Spike** | medium | Customer experience | Visitors bouncing straight back after arriving signals a broken or misleading landing experience for that traffic source. | Report only | ### Build your own automated fixes 11 checks report findings on Microsoft Clarity today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change. ## Automate approved work Vortex IQ is integrated with **1 read** and **0 write** operations across projectliveinsights on Microsoft Clarity. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=clarity) | Resource | Read operations | Write operations | | ------------------- | --------------- | ---------------- | | projectliveinsights | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready to build your first Microsoft Clarity workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*