--- title: How to find where website visitors get stuck with Microsoft Clarity description: Microsoft Clarity counts the moments visitors struggle on your site, such as rage clicks, dead clicks, quick backs, and shallow scrolling, and an AI marketer can turn those counts into a short, ranked list of pages to fix, find the cause on each page, ship the fix, and check Clarity again to see whether it worked. slug: /how-to/find-where-website-visitors-get-stuck-with-microsoft-clarity page_type: playbook lead_prompt: How do I find where website visitors get stuck with Microsoft Clarity? target_prompts: - How can I use an AI marketing agent to find where website visitors get stuck with Microsoft Clarity? entity: Kite category: AI marketing agent author: Devon Wells and Kite date_published: '2026-10-19' date_modified: '2026-10-19' related_use_cases: - /use-cases/improve-website-conversion.md integrations: - name: Microsoft Clarity page: /integrations/microsoft-clarity.md --- # Playbook # How to find where website visitors get stuck with Microsoft Clarity ## Key Takeaways - Microsoft Clarity shows where visitors get stuck by counting rage clicks, dead clicks, quick backs, excessive scrolling, and errors on each page, and by measuring how far visitors scroll and how long they stay engaged. - Doing this by hand means reading Clarity's dashboard, filtering session recordings by each signal, and checking heatmaps page by page. Clarity tells you where visitors struggled, but deciding which problem costs you the most and changing the page is still your job. - Kite reads your Clarity numbers by page, traffic source, campaign, and device, then ranks the problems by how much traffic they touch and how close they sit to a conversion. - For each problem worth fixing, Kite opens the page to find the cause and proposes a specific change. Once you approve, it publishes the change and reads Clarity again to see whether visitors struggle less. - You end up with a short list of pages and interactions to fix, each with its evidence, its likely cause, and a proposed change, plus a before-and-after reading for every fix that ships. ## How do I find where website visitors get stuck with Microsoft Clarity? You find where visitors get stuck with Microsoft Clarity by looking for the pages where its frustration signals cluster, then working out what on each page causes them. Clarity is Microsoft's free behavior analytics tool. Once its tracking code is on your site, it records sessions, builds heatmaps, and counts the moments that go wrong. Those counts are the place to start, because each one points to a different kind of problem: - A **rage click** is a burst of fast clicks on the same spot. It usually means a visitor expected something to happen and it didn't. - A **dead click** is a click on something that looks clickable but does nothing, such as text styled like a button. - A **quick back** is a visitor who opens a page and goes straight back to where they came from, which often means the page wasn't what they expected. - **Excessive scrolling** is a visitor scrolling up and down faster than anyone reads, which usually means they're hunting for something they can't find. - An **error click** is a click that triggers a JavaScript error, such as a signup button whose code fails when someone presses it. Clarity also measures scroll depth, which is how far down the page the average visitor gets, and engagement time, which is how long visitors actively spend on the page rather than how long a tab sits open. The manual route works like this. You open Clarity's dashboard to see which signals are high, filter the session recordings to sessions with rage clicks or dead clicks on a given page, and watch enough of them to spot a pattern. Then you open the page's click and scroll heatmaps to see where people tap and where they stop. Clarity's Copilot can summarize recordings and dashboard trends in plain language, which saves some of the watching. All of that tells you where visitors struggled. It doesn't tell you which problem to fix first. A page with dramatic rage clicks and fifty visitors a week matters less than your signup page with a modest problem and five thousand. An average can also hide the real story, because a form that works on a laptop may be broken on a phone. Once you've found the cause, someone still has to change the page and check whether the change helped. A good result is a short list rather than a long report. Each item names a page and the interaction that's going wrong, shows the numbers behind it, explains the likely cause, and proposes a change. After the change ships, the same numbers are read again so you know whether it worked. Kite does that work for you. It reads your Clarity data, decides which problems are worth your attention, finds the cause on the page, and fixes it with your approval. ## How to get started Start by asking Kite a plain question in the Kite web app or in Slack: > "Find out where people get stuck on our site and fix the worst one." Or point it at a page you already suspect: > "Our demo page gets traffic but hardly anyone books. Use Clarity to work out why." Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. By the time you ask, it already knows which pages matter to your business and what counts as a conversion for you, such as a demo booking, a trial signup, or a purchase. So it knows where to look first without a long brief. You'll need to connect your own Clarity project. An admin on the project creates an API token in Clarity under Settings, then Data Export, and adds it when Kite sends a connection link. Clarity has to be installed on your site and collecting visits before there's anything for Kite to read. Reading Clarity changes nothing, so Kite goes ahead and reports what it finds. Changing your website is different. Kite shows you the change it proposes and publishes it only after you approve. ## How Kite finds where visitors get stuck ### What does Kite read from Clarity? Kite reads a summary of how visitors behaved on your site from Clarity's data export, covering the last 24, 48, or 72 hours. The summary includes, for each page: - **Traffic**, meaning sessions, distinct users, pages per session, and bot sessions, so Kite knows how much weight each page's problems deserve. - **Frustration signals**, meaning rage clicks, dead clicks, quick backs, and excessive scrolling. - **Attention**, meaning scroll depth and engagement time. - **Errors**, meaning script errors and error clicks. - **Pages and referrers**, meaning your most visited pages, their titles, and the URLs that send visitors to them. Kite can break these numbers down by up to three dimensions at a time. The dimensions include page URL, traffic source, medium, campaign, channel, device, browser, operating system, and country or region. Microsoft allows only a limited number of exports per Clarity project each day, so Kite chooses its breakdowns deliberately. It usually starts with page and device, then adds source or campaign for the pages that look troubled. Kite reads counts and averages. Session recordings and heatmaps stay inside Clarity, where you can watch them yourself. ### Which problems come first? Kite ranks problems by how many visitors they affect and how close they sit to a conversion, rather than by which signal looks most alarming. It weighs each page's frustration signals against its traffic, so a busy page with a modest problem can outrank a quiet page with a dramatic one. It also gives more weight to the pages on the path to a conversion, such as your pricing page, your signup form, and the landing pages your campaigns send people to. Next, Kite compares the same page across audiences to find problems the overall average hides. Your signup page might look fine overall while visitors on phones rage-click the submit button far more often than visitors on laptops. That points to the mobile layout, not the offer. In the same way, a high quick-back rate among visitors from one paid campaign usually means the ad promised something the landing page doesn't deliver. Kite keeps the list short. It picks the few problems most likely to be costing you conversions and leaves the rest for later, because a page that changes five things at once makes it hard to tell which change helped. ### Why are visitors getting stuck there? Kite opens each page on the list to find what's causing the signal. It reads the page the way a visitor sees it, rendering it in a browser and capturing screenshots, and checks what sits where the trouble shows up. Each signal suggests where to look. Dead clicks often land on plan names, icons, or product images that look clickable but don't link anywhere. Rage clicks often land on a button that responds slowly or not at all. Low scroll depth on a page whose form or call to action sits near the bottom means most visitors never reach the part that asks them to act. Error clicks point to a button or form whose code fails. A quick back from one campaign sends Kite to compare the ad's message with the page's headline. When the page alone doesn't explain the numbers, Kite says so. It tells you which page and which signal to filter for in Clarity's recordings, so you can watch a handful of sessions and confirm the cause before anyone changes the page. ### Fixing the page Kite proposes a specific change for each problem and explains why it should help. It might turn a plan name into a link to the full plan comparison, add a booking button under the opening section of a long page, tighten the copy above a form, rewrite a landing page headline so it matches the ad that sends people there, or repair the code behind a broken button. Kite can make the change itself on a website it hosts, on a site in a GitHub repository you've imported, or on a site that runs on Webflow or another supported CMS. You can preview each change before it goes live. Approve it, and Kite publishes it and checks that the page displays correctly. If Kite can't edit your site directly, it writes up the change, with the exact copy and where it goes, for whoever maintains the site. ### Did the fix work? Kite measures each fix against the page's behavior before the change. Before it publishes, it records the page's rage clicks, dead clicks, error clicks, scroll depth, and engagement time. After the change has been live for a comparable period, it reads the same numbers again. Because each Clarity reading covers only the last few days, Kite can take readings on a regular schedule and save each one in your team's knowledge base. That gives it a running history to compare against, which matters most for pages with modest traffic. Kite also checks the conversion itself, using its built-in analytics on a site it hosts or a connected Google Analytics account, so a fix is judged by whether more visitors convert as well as by whether they struggle less. Kite reports the result in the conversation where you asked. If the signal dropped, it says so and moves to the next problem on the list. If it didn't, Kite tries another explanation. To keep this running, ask Kite to check Clarity every week, and it will tell you when a new problem appears. ## What the finished work contains When Kite finishes, you have a short list of what's going wrong on your site, the changes that address it, and the evidence for whether those changes worked. - **The ranked list.** Each item names a page and the interaction that's going wrong, such as dead clicks on the pricing table or shallow scrolling on the demo page. It shows the Clarity numbers behind it and the audience it affects, such as phone visitors or one campaign's traffic. - **The cause for each item.** Kite explains what on the page is causing the signal, with a screenshot of the spot, or names the recordings to watch in Clarity when the page alone doesn't settle it. - **The proposed changes.** Each change comes with its exact copy or design and the reason it should help, ready for you to preview and approve. - **The before-and-after readings.** Each fix that ships gets the page's Clarity numbers from before and after the change, alongside its conversion rate. - **A running history.** Saved readings build up in your team's knowledge base, so later work starts from what Kite has already learned about your pages. ## Common questions ### Is Microsoft Clarity free? Yes, Microsoft Clarity is free, including its session recordings, heatmaps, and data export. You install it by adding its tracking code to your site, and it starts collecting visits from then on. ### Can Kite watch my Clarity session recordings? No, Kite reads Clarity's summary numbers, not the recordings or heatmaps themselves. It works out the cause by reading the page where the signal clusters. When that isn't enough, it tells you exactly which recordings to watch in Clarity, filtered by page and signal, so a few minutes of viewing settles the question. ### How much data does Clarity need before the numbers mean anything? Clarity's data export covers at most the last three days, so a single reading on a low-traffic site can be thin. Kite handles this by taking readings on a schedule and saving each one, which builds a longer history than any single export provides. It also tells you when a page has too few visits for its numbers to support a change. ### How is this different from Clarity's Copilot? Clarity's Copilot summarizes recordings and dashboard trends inside Clarity, which helps you understand what happened. Kite takes the next steps. It decides which problems matter most for your conversions, finds the cause on the page, ships the fix with your approval, and measures the result. ## Related pages - **Use case:** [Improve website conversion](/use-cases/improve-website-conversion.md) - **Use case:** See how visitors use your pages (coming soon) - **Use case:** Fix your website's mobile layout (coming soon) - **Use case:** Find out why your ads aren't converting (coming soon) - **Integration:** [Microsoft Clarity + Kite](/integrations/microsoft-clarity.md)