> ## 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.

# Quick-Back Rate %, Microsoft Clarity

> Quick-Back Rate % for Microsoft Clarity stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Card class:** [Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Executive Overview](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Quick-Back Rate % is the share of visitors who land on a page then almost immediately hit back, a signal Microsoft Clarity is distinctively good at surfacing. A high rate means the page did not match what the visitor expected when they clicked, pointing to a landing-page or intent mismatch. It is one of the fastest ways to spot wasted ad spend and weak landing experiences.

|                       |                                                                                                                            |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | The percentage of Clarity-captured sessions where the visitor lands then quickly navigates back.                           |
| **Sample type**       | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| **Why it matters**    | Quick-backs reveal landing-page and intent mismatch, often tied to misaligned ads or messaging.                            |
| **Reading the value** | Lower is better; a rise versus the prior period flags a growing gap between visitor expectation and page content.          |
| **Currency**          | percent                                                                                                                    |
| **Time window**       | `30D vsP`                                                                                                                  |
| **Alert trigger**     | `>25%`                                                                                                                     |
| **Sentiment key**     | `clr_quick_back_rate`                                                                                                      |
| **Roles**             | owner, marketing                                                                                                           |

## Calculation

Microsoft Clarity identifies sessions where a visitor arrives on a page and rapidly returns to the previous page, then expresses those as a share of captured sessions over the window. Vortex IQ reads that rate 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 **Quick-Back Rate %** for a typical merchant on Microsoft Clarity.* A store's quick-back rate climbed from 18% to 29% after launching a new paid campaign, breaching the 25% alert. The merchant compared the ad creative to the landing page and found the promised discount was not visible above the fold. They used Vortex Mind to trace the spike to the campaign's launch date and traffic source, then asked Ask Viq in plain English which landing pages had the worst quick-back rate so they could fix the highest-traffic offenders first.

## Sibling cards merchants should reference together

| Card                                                                                                                           | Why merchants reach for it                                 |
| ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
| [`clr_landing_page_performance_vs_quick_back`](/nerve-centre/kpi-cards/clarity/landing-page-performance-vs-quick-back)         | Maps quick-backs directly to landing-page performance.     |
| [`clr_session_source_vs_ecom_revenue_attribution`](/nerve-centre/kpi-cards/clarity/session-source-vs-ecom-revenue-attribution) | Links quick-back traffic sources to revenue impact.        |
| [`clr_top_traffic_sources`](/nerve-centre/kpi-cards/clarity/top-traffic-sources)                                               | Shows which channels send the quick-back traffic.          |
| [`clr_avg_page_engagement_time`](/nerve-centre/kpi-cards/clarity/avg-page-engagement-time)                                     | Confirms whether quick-backs coincide with low engagement. |
| [`clr_health_score`](/nerve-centre/kpi-cards/clarity/clarity-ux-health-score)                                                  | Shows how quick-backs feed overall UX health.              |

## Reconciling against Microsoft Clarity

**Where to look in Microsoft Clarity's own dashboard:**

Open the Clarity Dashboard insights for the quick-back signal, or filter recordings to sessions flagged for fast return navigation. 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.             |

**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 Quick-Back Rate % 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 exclude bots, and its calendar period can differ from the Vortex IQ rolling window. Device or channel filters on either side will also move the rate. Match sampling, bot filtering, period, and filters before assuming a real divergence.

**Q: How is quick-back different from bounce rate?**
Bounce rate typically measures single-page sessions with no further interaction, while quick-back focuses on the specific behaviour of landing and immediately returning to the prior page. Quick-back is especially useful for diagnosing ad-to-landing mismatch, where the visitor's expectation breaks on arrival.

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

***

### Tracked live in Vortex IQ Nerve Centre

*Quick-Back Rate %* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.