Download websites that use Microsoft Clarity

About Microsoft Clarity

Analytics tools that cost nothing spread differently from analytics tools that cost money. Microsoft Clarity was released in 2020 by Microsoft and given away, and the adoption pattern reflects that: the tag turns up on personal blogs and on enterprise marketing sites alike, because nobody had to justify a line item to add it.

As of September 2026 the Analytics snapshot carries Microsoft Clarity on 628,832 sites. United States accounts for 343,386 of those, and .com is common across the group. We also record 40 distinct build strings for the JavaScript tag, with 0.7.59 in wide circulation at the same date.

Build numbers on a hosted tag deserve a caveat that rarely gets stated. The Clarity script is served and updated by its vendor rather than pinned by the site owner, so the version we capture describes where a site sat in a rollout wave at crawl time, not how diligently anyone maintains the page. Version spread here is a fact about release cadence. For a self hosted library the same field would be a maintenance signal, and treating the two identically produces confident but wrong conclusions.

Read the right way, the build spread is still useful. A long tail of older strings marks pages that are cached hard, served from a stale template, or sitting behind a proxy that pins an old copy of the snippet, and pages like that tend to be the neglected corners of otherwise active estates. Grouping the population by build also separates recent installs from installations that have been sitting in a footer for years, which is a distinction that matters if the question is whether adoption is still growing or merely persisting.

Presence carries more weight on the behavioural side. A site running Clarity is a site whose owner accepted session recording, heatmapping, and click capture by a third party, which is a decision with consent, privacy notice, and cross border data transfer consequences attached to it. Privacy engineers, regulators, and journalists care about that population for reasons that have nothing to do with marketing. Vendors of paid session replay care about the same population for reasons that have everything to do with marketing, because a free tool running on a large commercial site is a qualified prospect rather than a closed door. Co-occurrence is informative in the same way, since a page carrying both a free replay tool and a paid analytics suite is a page where somebody is already paying for measurement.

A per-domain check confirms a single tag on a single page. The downloadable list reaches questions a lookup cannot: which industries and markets adopted a free replay tool at all, how far the population overlaps with paid analytics installed on the same pages, whether uptake in one country runs ahead of another, and what the whole group looked like a snapshot ago. Filtering by suffix and by country turns a raw tag count into a segment somebody can actually work.

Two limits are worth stating plainly. Tags loaded through a consent manager may never fire for a crawler that declines cookies, which pushes the true population above what we publish rather than below it. And a tag in a template proves installation, not use, because an account can sit dormant for months while the snippet stays in the page.