Skip to main content
Web Design

Copilot in Clarity: What It Got Right and Wrong

KD

Kaleb Dickhaut

Founder, ClickWerxs

October 19, 2026
10 min read
A brass magnifying glass resting on a short stack of index cards on a concrete table, a few pencil tick marks on the top card and a pencil lying in front.

TL;DR: Copilot in Microsoft Clarity is worth using, as long as you check it. On our project, its Chat answer matched the dashboard exactly. Its grouped recording summary said a quote form went unsubmitted, while Copilot's own summary of that same recording called it a successful submission. Open the evidence before you act on any of it.

The one-sentence answer: Copilot in Clarity summarizes your dashboard, recordings and heatmaps with generative AI, and the way to use it safely is to check every answer against the number, recording or page-view count it came from.


Copilot's summary of our recordings said some users "initiated form filling for quotes but did not complete submission." It cited two recordings. We opened the first one.

The event log shows a visitor on mobile Safari typing into our quote form, about 35 "Entered text" events in all. At 01:41, they tap "Get My Free Quote →", and Clarity logs a Submit form smart event in the same second. A second later, the replay shows the button reading "Sending…". Then we opened that recording's Insights tab, where Copilot's summary of the single session says the tap "indicates successful completion of the intended action."

Same tool, same session, opposite conclusions. And our CRM has no contact from that visit. That's the problem with AI summaries in analytics. They sound like findings, and they arrive faster than you can check them. This guide walks through the Copilot features we tested on our own Clarity project, where each one held up, and the check that tells you whether to trust it.

Last verified: October 18, 2026. Copilot is labeled BETA in our project, so expect changes.

Prerequisites: Clarity installed on your site (see our guide to installing it without hurting PageSpeed). Microsoft says Copilot is only available on sites where the Clarity tracking code is installed. Some recorded traffic (our test used the last 30 days). About 30 minutes, by our estimate.


Step 1: Turn on Copilot and learn what each feature reads

Copilot in Clarity is a set of generative AI features inside your Clarity project. Each one reads a different slice of your data, and that slice decides what it can get right. Turn them on under Settings, then Copilot, then Copilot features. Ours was already on.

Clarity Settings, Copilot page with the Copilot features toggle switched on

Here's what Microsoft's documentation says each feature works from:

FeatureWhere it livesWhat it reads
ChatCopilot icon on the DashboardYour dashboard data only
Session insightsGenerate session insights icon on a recording, or More details, then the Insights tabOne recording
Grouped session insightsSummarize recordings button on the Recordings pageSeveral recordings at once, from your current filters
Heatmaps insightsSummarize heatmaps button on a page's heatmapThat page's last click, first click, rage click, dead click and scroll heatmaps

Microsoft also lists Ad Campaign Insights, which we haven't tested. Each of the five Copilot pages we read carries the same note: generative AI models "can sometimes misinterpret or generate incorrect information."

If you don't see Copilot features in Settings: check that your tracking code is installed and recording sessions. Microsoft's overview also mentions an onboarding checklist under Settings, then Copilot, and says Clarity notifies you when Copilot is available.

Step 2: Test Chat against a number you can see

Clarity's Chat answers questions about your dashboard in plain language, and it's the easiest Copilot feature to check, because the dashboard is on the same screen. Ask it something with a numeric answer, then compare. We asked: "How many sessions had dead clicks in the last 30 days, and which pages had the most?"

Clarity dashboard with the Copilot chat panel answering that the site had 10 sessions with dead clicks in the last 30 days, next to the Dead clicks card showing 10 sessions

It answered "10 sessions with dead clicks," then listed the top five pages. The dashboard's Dead clicks card for the same 30 days showed 6.80%, or 10 sessions. Exact match. Microsoft's FAQ explains why Chat's counts can match: Chat doesn't do calculations itself, but passes specific functions to Clarity's database to run.

The answer also showed the filters it applied: dead clicks present, and a date range of September 18 to October 18, 2026. That's the part that makes Chat checkable. Microsoft says that when a response contains filters, you can select the Dashboard icon to apply them to your dashboard, or the Recordings icon to open the matching recordings.

If Chat's number doesn't match your dashboard: compare the filters it applied with the ones on your screen, starting with the date range. Then rephrase the question with an explicit range ("in the last 30 days"). If it still doesn't match, give the answer a thumbs-down so the feedback reaches Microsoft, and trust the dashboard.

If you ask about a specific recording or a design change: Microsoft says Chat works only from your dashboard data, so it can't link to specific recordings or heatmaps, or make suggestions based on your site's design. Use the other features for those.

Step 3: Test recording summaries by opening what they cite

Copilot's recording summaries turn a list of sessions into a few bullet points, and each bullet cites recording numbers you can open. Opening those citations is the whole check. Skip it and you're taking a language model's word for what your visitors did.

We used the Summarize recordings button on our Recordings page with the Top recordings option, over the last 30 days. Microsoft's documentation describes this option as summarizing the top 10 recordings. Ours summarized 144 of the 146 recordings in the list. The panel was titled "Session insights."

Clarity Recordings page in summary mode, showing Summarized recordings (144) and a Session insights panel with bullet points and citation numbers

The summary came back in three sections: successful achievements, unsuccessful attempts and key takeaways. All six bullets cited two recordings each, and the takeaways cited them again.

We checked the bullet about unfinished quote forms by opening its first citation, recording 22. The event log shows the typing on the get-a-quote page, then a click on "Get My Free Quote →" at 01:41, with Clarity's Request quote and Submit form smart events in the same second.

Clarity recording event log showing Smart event Request quote, a click on Get My Free Quote and Smart event Submit form, all at 01:41, next to the replay with the form button reading Sending

Smart events are Clarity's own inference, so we checked the replay too. The button reads "Sending…" at 01:42. By 01:46 the form area has collapsed and the footer has moved up the screen. On our site, a successful submission replaces the form with a short confirmation panel, and a failed one keeps the form on screen with an error line. The confirmation never scrolls into view, so we checked our CRM. No contact was created or updated on October 13. Clarity shows a sent form; our CRM shows no new contact.

Then we opened the Insights tab on recording 22. Copilot's summary of that one session says the tap was "submitting the form" and "indicates successful completion of the intended action." The grouped summary and the single-recording summary reached opposite conclusions about the same session.

Notice what came next in the grouped summary. One of its three key takeaways, to streamline form fields and reduce friction, cited the same two recordings. But this visitor filled in the form and pressed send. The single-recording summary called that a success, yet our CRM has no contact from it. Neither summary can see past the browser.

If a cited recording doesn't show what the bullet says: treat the bullet as a lead to check. Compare it with that recording's own Insights tab, note the recording number, check your CRM for a lead at that time, and give the bullet a thumbs-down. Microsoft's FAQ says Copilot's takeaways "shouldn't be treated as expert recommendations."

If you want a tighter summary: filter first. Microsoft says grouped summaries work on any group of recordings you can filter, by events, device type, UTM campaign and more. A summary of 20 quote-page sessions is easier to check than one of 144 mixed sessions. Our guide to session recordings covers how to choose them.

Step 4: Check the page-view count before reading heatmap insights

Heatmaps insights summarize one page's heatmaps into user behaviors and key takeaways. The summary doesn't open by telling you how much data it read. Check the page-view and click counts under the heatmap first, because a takeaway from five page views looks just as confident as one from five thousand.

We ran it on our homepage, desktop view, with a three-day range. The counts under the desktop heatmap: 5 page views and 5 clicks. Microsoft says the summary reads the page across all three devices, so we rechecked the other views the same day: mobile held 1 page view, tablet none.

Clarity heatmap of the clickwerxs.com homepage with the Heatmaps insights panel open, and counts of 5 page views and 5 clicks under the heatmap

Copilot still produced three key takeaways, including encouraging "deeper scrolling beyond the average fold of 721px" and refining the "Chevron down button" interaction. One behavior bullet read: "Desktop users mostly stayed above 50% scroll depth, with only one reaching that point." That sentence can be read two ways, and five page views is a thin base for either reading.

Microsoft is upfront about part of this. Its FAQ says heatmap insights don't perform mathematical computations and instead "analyze different heatmap data comparatively," and it asks you to "double check the outputs and verify takeaways before applying them."

If the counts are low: widen the date range before you ask. We don't use heatmap insights on a page until its heatmap holds at least a few dozen page views. That threshold is our own rule of thumb; Microsoft doesn't give one. For reading the heatmaps yourself, see our guide to Clarity heatmaps.

If a takeaway names a specific element: select the link Copilot attaches to it. Microsoft says heatmap insights include built-in links to highlighted elements and heatmap views, so you can check the element before changing it.

Step 5: Use Copilot to choose what to watch, not what to change

Our position after testing: Copilot is good at pointing and unreliable at concluding. Use its summaries to choose which recordings to watch, and Chat to get dashboard numbers faster. Make changes to your site only after you've watched the sessions behind them.

In practice, that looks like this:

  1. Ask Chat for the number, then open its Recordings link.
  2. Run a grouped summary on that filtered set.
  3. Open every recording it cites in a bullet you plan to act on.
  4. Write down what you saw, in your own words, before you change anything.

The fair counterargument: checking every citation erases the time Copilot was supposed to save. Partly true. But opening two cited recordings takes minutes, and it's still faster than watching 144 sessions to find those two. Our frustration signals guide explains why we watch the recording before changing anything.

How do you know it's working?

You can trust your Copilot workflow when:

  1. Every Chat number you act on matches the dashboard with the same filters.
  2. Every summary bullet you act on has at least one cited recording that you opened yourself, and that recording shows what the bullet says.
  3. Every heatmap takeaway you act on came from a page with enough page views to mean something, and you checked the element it names.

If you can't tick all three for a change you're about to make, you're acting on the summary alone.

Where this setup fails

  • Our test is small. We checked one Chat answer, one cited recording, one single-recording summary and one heatmap summary. That's enough to show the checks matter. It isn't enough to rate Copilot's accuracy, and we don't.
  • The interface and the documentation differ. Our Top recordings summary covered 144 recordings where the documentation describes 10, and its panel was titled Session insights. Expect more drift while Copilot is in BETA.
  • Summaries blur counts. Our recording summary used "some users," "several users" and "a few users" without saying how many. Chat gives numbers; the summaries mostly don't.
  • We can't say what recording 22 was. It shows a sent form, and our CRM has nothing from that day. That could be a test, a bot or a lead that never arrived. Clarity can't tell those apart. If a cited recording matters, check it against your server logs and CRM before you act.

Frequently Asked Questions

Does Copilot in Clarity work for mobile apps?

Not for three of the four features we covered. Microsoft's documentation says Session insights, Grouped session insights and Heatmaps insights aren't currently supported for mobile apps. Its Chat page doesn't mention mobile apps.

Can I share or download Copilot's insights?

Microsoft says sharing and downloading aren't supported for any of the four features. Session insights and heatmap insights have a Copy icon, and Chat has a Clipboard button, so paste the text into your own notes with the date and filters you used.

Why is the insights icon greyed out on some recordings?

Microsoft says Session insights aren't available for sessions shorter than five seconds, because they're too short to produce meaningful sentences, so those show greyed out.

Can I turn Copilot off?

Yes. Microsoft's FAQ says Clarity offers an off toggle in Settings for anyone who doesn't want to keep using Copilot features.


Copilot told us a quote form went unsubmitted. The event log, the replay and Copilot's own summary of that session said it was sent, and our CRM has no contact from it. Gaps like that are why we check AI output against the data before anyone acts on it. If you want help putting AI tools to work in your business with that kind of checking built in, see how we approach AI services or get in touch.


Sources

  1. Microsoft Learn, "Copilot Overview": features (Chat, Session Insights, Grouped Session Insights, Heatmaps Insights, Ad Campaign Insights); generative AI "can sometimes misinterpret or generate incorrect information"; onboarding checklist; Settings, Copilot, Copilot features toggle. learn.microsoft.com (page dated 2025-05-12, retrieved 2026-10-18)
  2. Microsoft Learn, "Session Insights": two places to view; not available for sessions under five seconds; not supported for mobile apps; sharing and downloading not supported; Copy icon; Copilot only available where the tracking code is installed. learn.microsoft.com (page dated 2025-10-23, retrieved 2026-10-18)
  3. Microsoft Learn, "Grouped Session Insights": Summarize recordings button; top 10 recordings or custom select; works on filtered groups (events, device type, UTM campaign); citation numbers; not supported for mobile apps; sharing and downloading not supported. learn.microsoft.com (page dated 2025-12-01, retrieved 2026-10-18)
  4. Microsoft Learn, "Heatmap Insights": Summarize heatmaps icon; Copy icon; doesn't use Area or Conversion heatmaps; not supported for mobile apps; sharing and downloading not supported. learn.microsoft.com (page dated 2025-12-01, retrieved 2026-10-18)
  5. Microsoft Learn, "Clarity Copilot Chat": Dashboard and Recordings icons for responses with filters; based solely on dashboard data, so no links to specific recordings or heatmaps and no design suggestions; thumbs up/down feedback; Clipboard button; sharing and downloading not supported. learn.microsoft.com (page dated 2025-12-01, retrieved 2026-10-18)
  6. Microsoft Learn, "Frequently asked questions" (Clarity): heatmap insights cover last clicks, first clicks, rage clicks, dead clicks and scroll; no mathematical computations, "analyze different heatmap data comparatively"; "double check the outputs and verify takeaways before applying them"; takeaways "shouldn't be treated as expert recommendations"; built-in links to highlighted elements; Chat doesn't perform calculations directly but provides specific functions for the database to execute; off toggle in Settings. learn.microsoft.com (page dated 2026-09-08, retrieved 2026-10-18)
  7. ClickWerxs, Clarity project for clickwerxs.com, October 18, 2026: Copilot features on, panel labeled BETA; Chat answer of 10 dead-click sessions matching the dashboard's 6.80% / 10 sessions, filters applied September 18 to October 18, 2026; Summarize recordings, Top recordings, last 30 days: 144 of 146 recordings summarized, panel titled Session insights; recording 22 (October 13, 2026, mobile Safari): about 35 Entered text events, then Request quote smart event, click on "Get My Free Quote →" and Submit form smart event at 01:41, button reading "Sending…" at 01:42, form area collapsed by 01:46, confirmation panel not in view; that recording's Insights tab: "indicates successful completion of the intended action"; ClickWerxs Command Center, both ClickWerxs accounts, checked October 18: no contact created or updated on October 13, 2026; homepage Heatmaps insights, desktop, three-day range, 5 page views and 5 clicks; same-day recheck of mobile (1 page view) and tablet (none). Operator data.

Kaleb Dickhaut — Founder, ClickWerxs. Kaleb built ClickWerxs from the ground up, from payment processing ISO to the Command Center platform to the AI SEO methodology the blog runs on. He has onboarded hundreds of small businesses onto payment and CRM systems. linkedin.com/in/kaleb-dickhaut

Ready to Stop Overpaying on Payment Processing?

Get a free rate comparison and see how much you can save with interchange-plus pricing.