Is Microsoft Clarity web analytics or session recording?
Microsoft Clarity is a behavior analytics tool built around session recordings and heatmaps; invisit is web analytics without recordings. Clarity’s FAQ lists its features as session recordings, heatmaps and ML insights, and adds a dashboard with traffic, frustration signals, funnels and Copilot summaries around them.
invisit starts from the other end: where visitors came from, what they read, what converted and what it earned, with heatmaps of clicks, rage clicks, dead clicks and scroll depth on the side. It never records a session, so it cannot show you the mouse path behind a rage click. If your team watches recordings, invisit does not replace Clarity, and running both is a reasonable answer.
For the full field of recording tools, see our Microsoft Clarity alternatives guide.
Does Microsoft Clarity need a cookie banner?
Yes, for visitors from the EEA, the UK and Switzerland. Since October 31, 2025, Clarity enforces consent signals for visits from those regions, and its cookie list says Clarity’s typical use requires non-essential cookies. invisit sets no cookies and stores nothing on the device, so it needs no banner for analytics.
With consent, Clarity sets _clck for a year and _clsk to stitch page views into one session, plus third-party Microsoft cookies such as MUID, which Microsoft lists as used “for advertising, site analytics, and other operational purposes”. Your banner passes the answer through the Consent API or a supported consent platform.
Without consent, Clarity keeps collecting but changes how it reports:
| Report | Clarity, visitor without consent | invisit, every visitor |
|---|---|---|
| Sessions | Every page view is a new session | Visits end after 30 minutes without activity |
| Pages per session | Always 1 | Counted per visit |
| Funnels | Full drop-off at every page-view step | Steps within a visit |
| Returning users | None; every user is unique | Not tracked across days, by design |
| Source and referrer | More Direct, more of your own domain as referrer | Source of the visit’s first page |
invisit tells visitors apart with a hash that uses a new salt every UTC day, deleted about 25 hours after the day ends (privacy). Global Privacy Control and Do Not Track can be honoured with respectGpc and respectDnt; Clarity supports Global Privacy Control and does not respond to Do Not Track. Sites that want consent anyway can turn on invisit’s consent mode.
Who controls the data: Microsoft as controller, invisit as processor
Clarity’s terms of use make you and Microsoft independent controllers of the personal data, and say neither is a processor; the FAQ says Clarity “operates as a data controller”. invisit processes visitor data for you under its DPA.
As of November 2026, section 4.4 of the terms lets Microsoft use the personal data to improve its products and services and to “create user profiles for purposes that include advertising”, and non-personal data for training and evaluating machine learning models. Your privacy notice must say that Microsoft collects personal data to provide Microsoft Advertising.
The terms also rule some sites out. Clarity may not be used with “health care, financial services or government-related information”, and Microsoft says it “shouldn’t be used on any websites/apps targeting users under the age of 18”.
Clarity data is stored in Microsoft Azure. EU customers contract with Microsoft Ireland Operations Limited, which transfers data to Microsoft Corporation in the US under standard contractual clauses. invisit stores analytics data in Falkenstein, Germany, with Cloudflare (a US company) in front for DNS and CDN.
How long does Clarity keep data, and can you get it out?
Clarity keeps recordings for 30 days and heatmaps for 9 months; invisit keeps everything forever. The bigger gap is getting data out: Clarity’s API returns a few days of aggregates, while invisit’s REST API reads any report.
From Clarity’s data retention and Data Export API pages, as of November 2026:
| Microsoft Clarity | invisit | |
|---|---|---|
| Recordings | 30 days; favorited or labeled ones 9 months | No recordings |
| Heatmaps and clicks | 9 months | Forever |
| Visits | Visitor profiles show 9 months; playback 30 days | Every visit, step by step, at any age |
| API window | The last 1, 2 or 3 days | Any range, up to 400 days per request |
| API rate | 10 requests per project per day, 1,000 rows, no paging | 50 requests a minute per key |
| Deleting one visitor | Delete the whole project | No visitor ID kept across days |
Clarity’s MCP server runs locally on the same Data Export API, so it shares those limits. invisit’s REST API and hosted MCP server read the same reports as the dashboard, visits and heatmaps included (visits).
Clarity smart events, custom tags and funnels compared with invisit events
Clarity tracks actions as smart events: it detects nine kinds by itself, such as Purchase, Sign Up and Download, and you can define up to 20 more without code or send them with clarity("event", name). An event carries only its name. invisit events are sent with track() and carry up to 32 properties each (events).
Clarity’s custom tags, set with clarity("set", key, value), label the whole session for filtering recordings and heatmaps, with no limit on how many. Funnels are built without code from smart events and page visits, and each step opens its recordings. invisit builds funnels from pages or events too, and splits them by source, country or device.
Money is where they part. Clarity’s e-commerce insights show the share of sessions that purchased, on Shopify sites only, and checkout abandonment on Shopify Plus; no amounts. invisit reads revenue from Stripe, Paddle, Polar, Lemon Squeezy, Creem or Dodo Payments with no code in the checkout (connect a provider), and paid plans split it by source, campaign and landing page.
Heatmaps, frustration signals and script size
Both tools draw click heatmaps with rage clicks, dead clicks and scroll depth. Clarity adds area, conversion and attention maps and links each click to recordings; invisit keeps heatmap data forever and bills none of it.
Clarity’s heatmaps cover up to 100,000 page views each, overlay a screenshot taken from a random recording, and keep 9 months of data. Its rage and dead clicks are described in words, “in a clustered area in rapid succession”, and it also flags excessive scrolling and quick backs. invisit’s heatmaps are drawn over your live page, and give exact thresholds: a rage click is the third click within 30 pixels inside one second.
The cost of recordings shows in the script. Clarity’s clarity.js 0.8.77, recorder included, measured about 26.5 KB gzipped on November 16, 2026. invisit’s core script is about 9.8 KB gzipped, and its heatmap module loads only on sites that turn heatmaps on.
Does Clarity track AI traffic, crawlers and Google searches?
Clarity covers AI referrals and AI crawlers, but not Google search queries. invisit covers all three.
- AI referrals. Clarity’s AIPlatform channel counts visits from ChatGPT, Claude, Copilot, Gemini and Perplexity, with paid placements in a PaidAIPlatform channel apart. invisit recognises 19 assistants in their own AI tab.
- Crawlers. Clarity’s Bot Activity reads your CDN or server logs once you connect Cloudflare, CloudFront, Fastly, Azure Front Door or Akamai, and Microsoft warns the CDN may charge for it. Its Citations dashboard shows when AI answers cite your pages. invisit records crawler reads with
@invisitdev/serverand never bills them. - Google searches. Clarity uses Search Console only to verify a domain for citations. invisit connects a Search Console property on every plan, Free included, and shows queries, clicks, impressions, CTR and position by page.
invisit also sends traffic alerts for spikes, drops, silence and error spikes to Slack, Discord, ntfy or a webhook. Clarity emails project admins when page views fall more than 50% against the previous week.
When Microsoft Clarity is the better choice
Clarity is the better choice when you watch recordings, or when free at any volume decides it.
- Session recordings. Up to 100,000 a day per project, with live playback, visitor profiles across sessions, and Copilot summaries of single sessions, groups of sessions and heatmaps. invisit has none of this.
- Price. Clarity is free with no traffic limits. invisit is free to 20,000 events a month, then $14 for 100,000 and $199 for 10M.
- More map types. Area, conversion and attention maps, and heatmap comparison.
- Mobile apps. Clarity has SDKs for iOS, Android, React Native, Flutter and Cordova; invisit measures websites only.
- AI visibility. Bot activity read from your CDN logs with no server SDK, and a Citations dashboard showing which AI answers cite your pages.
- Your tools. Integrations with Google Analytics, Shopify, HubSpot, Optimizely and AB Tasty, and an advertising dashboard for Microsoft Ads and Google Ads campaigns.
If your visitors are mostly outside Europe, or you already pass consent from your banner, and 30 days of recordings answers your questions, keep Clarity. If you want traffic, revenue and history next to it, add invisit beside it rather than instead of it.
Switching from Clarity to invisit, or running both
Add invisit next to Clarity, move your events, then decide whether Clarity’s recordings still earn their banner.
- Install invisit next to the Clarity tag, or add
@invisitdev/webto your bundle (frameworks). - Turn on heatmaps for the site in the dashboard, with no code change (heatmaps).
- Move your events.
clarity("event", ...)becomestrack(), and a custom tag you want to report on becomes an event property, since invisit has no session tags:
import { identify, init, track } from '@invisitdev/web'
// Before: Microsoft Clarity
clarity('set', 'plan', 'pro')
clarity('event', 'signup')
clarity('identify', user.id)
// After: invisit
init({ site: '<site id>' })
track('signup', { plan: 'pro' })
identify(user.id) // stored as a hash- Rebuild your funnels from the same pages and events (funnels), and connect your payment provider in place of a Purchase smart event.
- Save what Clarity will delete. invisit cannot import history. Favorite or label the recordings you need, which keeps them 9 months, download the heatmaps you want as CSV or PNG, and download the dashboard for the ranges you report on.
- Compare page views, not sessions, while both run: Clarity counts every page view as a session for EEA, UK and Swiss visitors without consent.
If nobody on your team plays recordings, remove the Clarity tag, take Clarity and Microsoft Advertising out of your banner and privacy notice, and delete the project once you no longer need its data. If they do, keep Clarity for recordings and use invisit for the rest.