A quick back is a behavioural analytics measurement that records a visitor clicking through from one page, arriving somewhere else, and returning to the starting point almost immediately. The term belongs to Microsoft Clarity, the free session-recording and heatmap product that ships the metric alongside rage clicks, dead clicks and excessive scrolling in a group Microsoft labels semantic metrics. It exists because conventional traffic counts cannot distinguish a link that did its job from a link that misled the person who clicked it. Both produce a pageview. Only one of them produces a fast return.

Microsoft's semantic metrics reference describes a quick back as a click that leads users away from the current page to another website, where the visitor does not find the navigation useful and comes back under a certain threshold of time. The detection rule stated on the same page is narrower: Clarity flags a quick back when a user moves from a new page to the previous page in less time than a defined threshold, which the documentation ties to the dwell time for that page.

Neither the threshold nor the method for setting it is published. The reference adds that the metric will adapt to the specific site in future releases, wording that has survived successive revisions of the page, most recently dated December 1, 2025.

The related quantity is click dwell time, which Microsoft defines in two ways depending on destination. For external sites it runs from the click to the moment users resume activity on the origin. For internal sites it is the time spent on a subpage before returning to the source page or moving to another page. The asymmetry matters because a browser cannot observe activity on a third-party domain; the origin tag can only see that focus came back.

Clarity's mobile SDK documentation restates the definition with screens substituted for pages, so an in-app quick back is a navigation to a screen followed by a fast return. Nothing in the documentation exposes a client-side quick back event. The classification is produced inside Clarity's pipeline and appears only in Clarity's own reporting surfaces.

Four places. The dashboard Insights card carries the aggregate, and the Trends feature added on July 16, 2025 draws a 30-day line graph on the card rather than a single figure.

The second is filtering. Quick backs sit in the User actions group under Insights, described in Microsoft's filter reference as a way to find confusing navigation or content. There are more than 30 filters across nine groups, so a quick-back population can be cut by device, browser, operating system, country, state and city, by traffic channel including the AI platform groups added in August 2025, by ad campaign, by session duration and page duration, and by performance score, Largest Contentful Paint, Interaction to Next Paint or Cumulative Layout Shift. Filter combinations save as segments.

The third is session recordings, reachable directly from the filtered set, which is the only route to seeing what a flagged visitor actually did.

The fourth is programmatic. Clarity's Data Export API exposes a metric named Quickback Click through a single endpoint at www.clarity.ms/export-data/api/v1/project-live-insights, authenticated with a JWT bearer token generated by a project admin. Requests accept a numOfDays value of 1, 2 or 3 and up to three dimensions drawn from browser, device, country or region, operating system, source, medium, campaign, channel and URL. The published caps are ten requests per project per day, a three-day lookback, and 1,000 rows per response with no pagination. Microsoft's Model Context Protocol server for Clarity, which reached developers on June 4, 2025, wraps the same endpoint and inherits the same ceilings.

Clarity began as an internal Microsoft tool for studying user behaviour on Bing, ran as a closed beta from 2018, and reached general availability on October 28, 2020 through an announcement on the Bing Webmaster blog. Quick backs were present at that launch. Microsoft's fifth-anniversary post, published December 15, 2025, lists rage and dead clicks, sessions, scroll depth, JavaScript errors and quick backs among the metrics already on the original dashboard.

The metric itself has changed remarkably little since. What changed around it was reach and plumbing. Clarity for mobile apps arrived in April 2023, extending the definition to native screens. The Data Export API reference carrying Quickback Click is dated November 26, 2024. City and state granularity landed on dashboard cards on October 22, 2025. Adoption widened through Google Tag Manager, WordPress and Shopify integrations, with the WordPress plugin simplified in July 2025 to create projects automatically on activation.

Paid media buys attention up to the click and then loses visibility. A quick back is one of the few free signals that describes what happened immediately after, and Clarity has been steadily wired into advertising reporting to exploit that. Google Ads integration arrived in January 2025 and gained additional columns in March 2025, while Campaign Insights, announced on May 14, 2025, joined advertising performance data to behavioural friction signals so that landing pages producing negative engagement could be identified per campaign.

Distribution took a harder turn on November 11, 2025, when Microsoft Advertising began requiring third-party publishers to install Clarity across their placements, with clicks from pages lacking the tag filtered out as nonbillable. That requirement puts Clarity's tag, and the quick back count with it, on inventory that publishers previously instrumented at their own discretion.

Segmentation gives the metric a second use. Because channel filters separate AI platform referrals from organic search, quick-back rates for visitors arriving from chat assistants can be compared against search arrivals on the same page.

The undisclosed threshold is the central problem. A number that cannot be reproduced cannot be audited, and the promise of site-specific adaptation has stood unfulfilled in the documentation for five years.

Microsoft's own wording is also inconsistent. The semantic metrics page frames the behaviour as navigation to another website; the filter reference frames it as movement to a new page and back to the previous one. Third-party guides split along the same line, some describing quick backs as outbound-link regret and others as internal navigation failure. The two readings imply different fixes.

Interpretation is contested on separate grounds. Agency RicketyRoo, publishing an analysis of quick backs across four page types, reported that flagged sessions skewed towards longer visits in which people were sampling pages rather than abandoning them, and that recommended changes moved the count up on three of the four pages while conversions improved. A return is not proof of dissatisfaction.

Coverage is partial in Europe. Clarity began enforcing consent signals for sessions originating in the European Economic Area, the United Kingdom and Switzerland from October 31, 2025, following an earlier shift to requiring calls to its own Consent API that surfaced in December 2024. Rates from consent-gated markets are not directly comparable with rates from markets where the tag runs unimpeded.

Export limits constrain analysis. Ten calls a day against a three-day window means a historical series has to be assembled by polling and storing results externally.

One documentation conflict is worth flagging. Several practitioner guides state that quick backs can be viewed as a click heatmap. Microsoft's click maps reference lists six types: all clicks, dead clicks, rage clicks, error clicks, first clicks and last clicks. Quick backs is not among them.

Bounce rate and engagement rate in Google Analytics 4 operate at session level. Google counts a session as engaged if it lasts at least ten seconds, includes at least one key event, or includes two or more page or screen views, and treats bounce rate as the complement. A quick back is an event inside a session, and a session containing one has by definition produced at least two pageviews, so it registers as engaged. The two metrics can move in opposite directions on the same traffic.

Dead clicks involve no navigation at all: a click on an element that produces no visual response and no page change. A quick back requires that navigation succeed and then be reversed.

Rage clicks are repeated clicks in a tight cluster within a brief period on a single page, a frustration signal that never leaves the page.

Pogo-sticking, and the badClicks attribute associated with it, sit on the search engine rather than the site. Google's Navboost system was described in Department of Justice antitrust testimony by search vice-president Pandu Nayak and named in the May 2024 leak of internal Content Warehouse documentation, which listed goodClicks, badClicks and lastLongestClicks. Those are measured from the results page by Google, retained on a rolling window, and unavailable to site owners. Google has published none of the definitions. A quick back is measured by the site, on the site's own tag, and says nothing directly about ranking.

Clarity's development has moved decisively towards AI visibility, with Bot Analytics arriving in January 2026, robots.txt violation detection on June 23, 2026, Topic Insights on July 9, 2026, and an AI scrape-to-referral ratio card on August 13, 2026. The frustration metrics have been left broadly as they were. The filter reference was revised on May 21, 2026 and still carries the same one-line description of quick backs written years earlier. As of August 2026, no numeric threshold, no site-adaptive model and no published benchmark range for the metric have appeared.

• 2018: Microsoft Clarity begins as a closed beta, built from an internal tool for studying behaviour on Bing.
• October 28, 2020: Clarity reaches general availability. The launch dashboard includes quick backs alongside rage clicks, dead clicks, scroll depth and JavaScript errors.
• April 2023: Clarity for mobile apps ships, extending quick backs to native app screens.
• November 26, 2024: The Data Export API reference is published, listing Quickback Click among available metrics.
• January 13, 2025: Google Ads integration launches in Clarity.
• May 14, 2025: Campaign Insights connects advertising performance to behavioural friction signals.
• June 4, 2025: Microsoft releases a Model Context Protocol server for Clarity built on the Data Export API.
• July 16, 2025: Trends adds 30-day line graphs to dashboard cards.
• August 29, 2025: AI platform and paid AI platform channel groups are introduced.
• October 22, 2025: City and state granularity is added to dashboard cards.
• October 31, 2025: Consent signal enforcement begins for sessions from the EEA, United Kingdom and Switzerland.
• November 11, 2025: Microsoft Advertising requires third-party publishers to install Clarity on their placements.
• December 1, 2025: The semantic metrics documentation is revised, retaining the original quick back definition.
• December 15, 2025: Clarity's fifth-anniversary post confirms quick backs shipped with the 2020 dashboard.
• May 21, 2026: The filters reference is revised, keeping the same quick back description.

• Microsoft Clarity bridges ad gap with AI insights - Campaign Insights, announced May 14, 2025, ties post-click friction signals to specific advertising campaigns.
• Microsoft Clarity expands Google Ads metrics - Six additional data columns and drag-and-drop column management arrive in the advertising dashboard.
• Microsoft Advertising requires Clarity for third-party publishers - Placements without the Clarity tag produce nonbillable impressions and clicks from November 11, 2025.
• Microsoft Clarity enforces cookie consent requirements across Europe - Consent signals become mandatory for EEA, UK and Swiss sessions from October 31, 2025.
• Microsoft Clarity and OneTrust announce major changes to consent management - Clarity moves to requiring active calls to its own Consent API before enabling recordings and funnels.
• Microsoft launches AI analytics bridge for developer tools - The Clarity MCP server, released June 4, 2025, and the ten-request daily export ceiling it inherits.
• Microsoft Clarity introduces trends feature with line graphs - Dashboard cards gain 30-day trend visualisation on July 16, 2025.
• Microsoft Clarity adds city and state metrics to dashboard cards - Geographic reporting moves below country level on October 22, 2025.
• Microsoft Clarity introduces AI channel groups for traffic analytics - Dedicated channel groups separate AI assistant referrals from other traffic sources.
• Microsoft Clarity vs. Google Analytics 4: a detailed comparison - How Clarity's frustration indicators sit alongside GA4's traffic and engagement reporting.
• Microsoft Clarity simplifies WordPress setup with streamlined plugin - Automatic project creation and an embedded dashboard lower the deployment barrier.
• Microsoft Clarity card ranks which AI operators scrape most and refer least - The August 13, 2026 scrape-to-referral card, the most recent addition to Clarity's AI reporting.

Who: Microsoft defines and computes the metric inside Clarity. The people who read it are conversion rate optimisation specialists, UX researchers, SEO practitioners, paid media buyers analysing landing page quality, and publishers running Clarity as a condition of Microsoft Advertising monetisation.

What: A count of instances in which a visitor clicks through to a page or screen and returns to the previous one before passing a dwell time threshold that Microsoft has not published. It is reported as an aggregate insight, a session and heatmap filter, and an API metric named Quickback Click.

When: Present since Clarity reached general availability on October 28, 2020, extended to mobile app screens in April 2023, and exposed programmatically through the Data Export API documented in November 2024. The definition remains unchanged as of August 2026.

Where: The Clarity dashboard Insights card, the User actions filter group, session recordings, and the project-live-insights endpoint, plus the Clarity Model Context Protocol server that sits on top of it.

Why: Pageview counts cannot separate a link that satisfied intent from one that misled. The quick back isolates the second case at the level of an individual navigation, giving site owners and advertisers a free post-click signal that traditional session metrics such as bounce rate cannot produce, subject to an unpublished threshold and consent-limited coverage in Europe.