--- title: See how visitors use your pages description: Find out how far visitors scroll, where they lose interest or get stuck, and whether they ever reach the part of the page that asks them to act, then change the page so more of them get there. slug: /use-cases/visitor-behavior page_type: use-case lead_prompt: How do I see how visitors use my pages with AI? target_prompts: - Can an AI marketing agent show me how far visitors scroll on my pages? - How do I see how far people scroll on my landing page? - How do I use Microsoft Clarity heatmaps to improve a page? - How do I use session recordings to find where visitors get stuck? - Are visitors reading my page or leaving before the important part? entity: Kite category: AI marketing agent author: Devon Wells and Kite date_published: '2026-11-12' date_modified: '2026-11-12' related_integrations: - /integrations/microsoft-clarity.md related_playbooks: - /how-to/find-where-website-visitors-get-stuck-with-microsoft-clarity.md --- # See how visitors use your pages ## Key Takeaways - To see how visitors use a page, you need a behavior analytics tool such as Microsoft Clarity, which is free. It records how far each visitor scrolls, where they click, and how long they stay engaged, and it adds heatmaps and session recordings on top. - Whether visitors reach the important part of a page depends on two things together: how far they scroll, and how far down the page that part sits. An average scroll depth of 45 percent is fine when the signup form is near the top and a serious problem when the form starts 70 percent of the way down. - Kite reads your Clarity data for each page, broken down by device, traffic source, and campaign, and compares it with where your pricing, customer proof, and calls to action actually sit on the page. - Kite separates visitors who lose interest from visitors who get stuck, using Clarity's counts of quick backs, rage clicks, dead clicks, and frantic scrolling, and then reads the page itself to find the cause. - Kite proposes a change, publishes it once you approve, and reads Clarity again to see whether visitors get further down the page. Heatmaps and session recordings stay in Clarity, and Kite tells you which ones are worth opening. ## How do you see how visitors use your pages? You see how visitors use your pages with a behavior analytics tool, which records what people do on a page rather than only whether they arrived. Regular analytics, such as Google Analytics, tells you how many people came to a page, how long they stayed, and whether they converted. It doesn't tell you whether they read past the headline. Microsoft Clarity is free and fills that gap, and Hotjar and similar tools do the same job. A behavior analytics tool gives you three ways to look at a page: - **Scroll depth** shows how far down the page visitors get before they leave. - **Heatmaps** lay visitors' clicks and scrolling over the page itself, so you can see where attention gathers and where it fades. - **Session recordings** replay one visitor's visit, including their scrolling, their clicks, and the moment they left. Collecting the data is the easy part. Knowing what it means for your page takes more work. Say your landing page has an average scroll depth of 50 percent. That number can't tell you whether you have a problem until you know where your form, your pricing, or your strongest customer quote sits on the page. An average across every visitor can also hide a problem that only affects phone visitors or the people who arrived from one ad. So the real job has several parts. You find where the important part of each page sits, compare it with how far visitors get, and split the result by device and traffic source. Then you work out whether people are bored or stuck, read the page at the point where they stop, change it, and check again. Watching recordings one at a time is a slow way to do this, because an afternoon of recordings still won't tell you whether what you saw is typical. Reading the numbers for every page and every audience at once, and repeating the reading after each change, is work an AI agent does well. Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Here's how it shows you how visitors use your pages and gets more of them to the part that matters. ## How Kite shows you how visitors use your pages Kite starts with what it already knows about your business. Its research covers your products, pricing, customers, and what counts as a conversion for you, so it knows which pages matter most and which part of each page is supposed to turn a visitor into a lead or a customer. Next, it makes sure the behavior data is being collected and connected. Then it reads how far visitors scroll on each page and compares that with where the important part sits. It separates the pages where visitors lose interest from the ones where they get stuck, and it reads each page at the point where visitors stop to work out why. Finally, Kite changes the page so more visitors reach the important part. Once the change is live, it reads Clarity again to see whether visitors get further, and it checks whether more of them convert. ### Get the behavior data in place Kite needs Microsoft Clarity running on your site and connected to Kite before it can see how visitors behave on a page. When Kite researches your website, it detects which analytics tools are already installed, so it can tell you whether Clarity is running. If it isn't, you create a free Clarity project and add its tracking code to your site. If Kite hosts your site or works in your GitHub repository, Kite can add the tracking code as part of a site change. Then you connect Clarity to Kite with an API token from your Clarity project's settings. Kite's access is read-only, so it reads your data and changes nothing in Clarity. Clarity needs a few days of visits before there's much to read. If Kite hosts your site, its built-in analytics already record visits, clicks on calls to action, form submissions, and the steps visitors take toward converting. Those numbers tell Kite whether visitors convert. Clarity adds how far down the page they got and what they did there before they left. ### How far do visitors scroll on each page? Kite reads Clarity's scroll depth and engagement time for each page and sets them against where the important part of that page sits. Scroll depth shows how far down the page the average visitor gets. Engagement time shows how long visitors actively spend on the page, rather than how long a tab sat open in the background. To know where the important part sits, Kite opens the page on a desktop screen and a phone screen and notes how far down each key section begins. That usually means the pricing table, the customer quotes, the signup or booking form, and the main call to action. Then it compares the two. Here's an example. Your demo landing page has an average scroll depth of 62 percent on desktop and 34 percent on phones, and the booking form starts about 70 percent of the way down. Most desktop visitors stop just short of the form, and most phone visitors never get near it. The form isn't failing. Most people simply never see it. Kite breaks these numbers down by up to three things at a time, such as the page, the device, and the traffic source or campaign. That's how it finds the problems an overall average hides. A page that holds desktop visitors well can lose phone visitors halfway down, and visitors from a newsletter often read further than visitors from a paid ad. ### Are visitors losing interest or getting stuck? Visitors who lose interest and visitors who get stuck both leave, but they need different fixes. Kite reads Clarity's counts of frustration alongside scroll depth so it can tell the two apart. Shallow scrolling, short engagement time, and a high number of quick backs usually mean visitors lost interest or didn't find what they expected. Clarity's frustration counts point to visitors who wanted to keep going and couldn't: - A **rage click** is several fast clicks on the same spot, which 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. - **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 sets off a JavaScript error, such as a "Start trial" button whose code fails. - A **quick back** is a visitor who opens a page and heads straight back to where they came from. Kite reads these counts for each page alongside its traffic, so a busy page with a modest problem can rank above a quiet page with a dramatic one. It also breaks them down by campaign. When quick backs are high for visitors from one ad and normal for everyone else, the page usually doesn't deliver what that ad promised. **Related Playbooks** - [How to find where website visitors get stuck with Microsoft Clarity](/how-to/find-where-website-visitors-get-stuck-with-microsoft-clarity.md): Rank your pages and audiences by rage clicks, dead clicks, quick backs, and scroll depth, find the likely cause on each page, and choose the first fix to ship. ### Find out why visitors stop where they do Once Kite knows where visitors stop, it reads the page at that point to work out why. The numbers show where interest fades, and the page itself usually explains the reason. Some causes come up again and again. The section just above the drop-off may be a long grid of features that gives the visitor no reason to keep reading. A wide image or a block of white space can look like the end of the page, so visitors assume there's nothing below it. The important part may sit inside a tab or a collapsed panel that most people never open. Or the opening of the page may not match what the visitor came for, so they leave before they scroll at all. Kite checks the page against those patterns and against what it knows about your customers. Then it decides what to change. If the pricing page loses visitors at a long comparison table, the fix is different from a homepage that loses phone visitors before the first customer quote. Kite explains what it found and what it plans to change before it does anything. ### Move the important part to where visitors are Kite changes the page so more visitors reach the part that asks them to act. Often that means bringing the important part up to where visitors already are, rather than hoping they scroll further. Depending on what it found, Kite might add a booking button to the opening section, move a customer quote above the point where visitors stop, shorten or cut the section that loses them, or take the key details out of a collapsed panel. When visitors are stuck rather than bored, it fixes the cause directly. It turns a dead-clicked plan name into a real link, for example, or repairs the button that throws an error. On a site Kite hosts, it publishes the change once you approve it. If your site runs on Webflow, Contentful, Sanity, or Storyblok, or lives in a GitHub repository, Kite makes the change through that connection. For broader conversion work beyond scroll and attention, see [Improve website conversion](/use-cases/improve-website-conversion.md). ### Check whether visitors get further down the page After a change goes live, Kite reads Clarity again to see whether visitors now reach the part that matters. It compares scroll depth, engagement time, and the frustration counts for the page with the readings it took before the change. Each reading from Clarity covers only the last one to three days. So Kite takes readings on a regular schedule and saves each one, which builds a history it can compare against. It compares like with like, such as the same weekdays before and after, so a busy Monday doesn't pass for an improvement. Getting further down the page only matters if more people act. On a site Kite hosts, it checks the conversion numbers in its built-in analytics, and it can run the new version as an experiment, sending part of your traffic to each version and asking you before it makes the winner permanent. Kite tells you what changed, and if visitors still stop in the same place, it tries the next explanation. ## What you get - **A reading of each important page.** How far visitors scroll and how long they stay engaged, set against where your form, pricing, proof, and calls to action sit on the page. - **The audiences a page loses.** Where the page works for some visitors and fails others, broken down by device, traffic source, and campaign. - **A verdict on each problem page.** Whether visitors are losing interest or getting stuck, with the frustration counts that show it and the cause Kite found on the page. - **A short list of what to watch in Clarity.** The pages, devices, and campaigns whose heatmaps and recordings are worth your time, so you open the ones that explain the problem. - **The change itself.** A revised page ready for your approval, published to a site Kite hosts or through your connected website platform. - **A before-and-after comparison.** How far visitors get after the change compared with before, whether more of them converted, and what Kite would try next. ## How to get started Tell Kite what you want to know, in plain language. You might ask, "Are people actually reading our pricing page?" or "Find out where visitors give up on our demo landing page." You can work with Kite in your browser or in Slack. Kite proposes the pages it plans to look at first and explains why it chose them, so you can adjust the list before it starts. If Microsoft Clarity isn't connected yet, Kite sends you a connection link the first time it needs it. If Clarity isn't on your site yet, Kite tells you, and on a site Kite hosts or in your GitHub repository, it can add the tracking code for you. Kite comes back with what it found on each page and the first change it recommends. It asks before it publishes a change or starts an experiment, and you can give it more room to act on its own as you come to trust its judgment. ## Integrations used to see how visitors use your pages This job depends on a behavior analytics tool that records what visitors do on each page. Kite reads that data, compares it with the page itself, and uses its own analytics or your website platform for the conversion numbers and the changes. ### Read how visitors behave on each page - [Microsoft Clarity + Kite](/integrations/microsoft-clarity.md): Kite reads scroll depth, engagement time, quick backs, rage clicks, dead clicks, excessive scrolling, and error clicks for each page, broken down by device, traffic source, and campaign. Its access is read-only. ### Measure conversions and publish changes If Kite hosts your site, its built-in analytics record visits, calls to action, form submissions, and conversions, and Kite publishes changes there directly. If your site runs elsewhere, Kite makes changes through your connected Webflow, Contentful, Sanity, or Storyblok account, or in your GitHub repository. ## Common questions ### How do I use Microsoft Clarity heatmaps to improve a page? Open the page's scroll heatmap first. It colors the page from warm to cool to show what share of visitors reached each point, so you can see exactly where attention fades and what sits just above that line. Then open the click heatmap to see what visitors try to click. Clicks clustered on text or images that aren't links mean visitors expected them to do something, and very few clicks on your main button mean they either never reached it or didn't notice it. Filter both heatmaps by device, because the phone version of a page often tells a different story. Kite reads Clarity's numbers rather than the heatmap images, so it tells you which page and device to open. If you're still choosing a tool, see The best free heatmap tools for small websites (coming soon). ### How do I use session recordings to find where visitors get stuck? Filter the recordings before you watch any. In Clarity, narrow them to one page and to sessions with rage clicks, dead clicks, or quick backs, then watch a handful and look for the moment each visitor hesitates, hunts, or leaves. Unfiltered recordings are mostly ordinary visits, so watching them at random takes a long time and rarely shows the problem. Kite doesn't watch recordings itself. It reads Clarity's counts across every visit and tells you which page, device, and campaign to filter on, so the recordings you open are the ones most likely to show where visitors get stuck. ### What is a good scroll depth? There's no single good number, because scroll depth only means something next to the layout of the page. A short page with its form near the top can convert well with shallow scrolling, while a long page with its form near the bottom needs visitors to scroll almost all the way. The useful question is whether most visitors get past the part that asks them to act. Kite answers it by comparing each page's scroll depth with how far down that part sits on desktop and on phones. ### Can Google Analytics show how far visitors scroll? Only roughly. Google Analytics 4 records a scroll event when a visitor reaches 90 percent of the way down a page, so it tells you how many people reached the bottom but not where everyone else stopped. Tracking other depths means setting up your own scroll triggers in Google Tag Manager. A behavior analytics tool such as Microsoft Clarity measures scroll depth for every visit without that setup, which is why Kite reads scroll depth from Clarity. ### Can I see who visits my website? Behavior analytics tools show what visitors do, not who they are. Clarity records visits without names, and Kite reads summary numbers for each page and audience rather than individual visitors. If you want to know which leads came from which campaign, the place to look is your forms, your CRM, and the campaign tags on your links.