Consent management for Microsoft Clarity
Clarity watches how people actually use your site, which means storage, which means consent. Consent Studio speaks Clarity’s own consent API: denied before your visitor answers, updated the moment they do. Nothing to block, nothing to rewire.
- Clarity’s own consent API
- Denied until they choose
- Built in, no code
From €10 a month. No credit card, no per-visitor billing.
A cookie banner that works with Microsoft Clarity
Clarity has a consent API of its own, so none of this works by stopping a script from loading. We tell Clarity what was decided and Clarity adjusts itself.
We signal Clarity, we do not block it
Clarity accepts a consent call of its own, so Consent Studio sends it the decision rather than preventing the script from running. Clarity stays exactly where Microsoft’s instructions put it and keeps behaving the way Microsoft designed it to.
- Clarity consent API
- Nothing to move
Analytics and advertising are separate signals
Clarity takes two, and Consent Studio maps them to two different categories: analytics storage follows your analytics consent, advertising storage follows marketing. A visitor who accepts measurement but refuses advertising gets exactly that, instead of one switch for both.
- Two consent signals
- Mapped per category
Denied before anyone answers
Both signals are sent as denied while the banner is still on screen, so Clarity knows where it stands before your visitor has decided anything. If you serve regions where opt-out is the standard, either signal can be set to start granted instead, per site.
- Denied by default
- Opt-out configurable
One answer controls every tool on your site
A banner that only governs the platform leaves everything you added on top of it running. Consent Studio speaks to the tools around it as well, and by default holds anything it does not recognise until the visitor says otherwise.
Discover All Integrations
How to set up cookie consent for Microsoft Clarity
Clarity is not something you install the banner into, so this is switching a signal on rather than putting code anywhere.
Install the banner
Add Consent Studio to your site, either as a script in your template or as our official tag in Google Tag Manager. Leave Clarity exactly where Microsoft’s own instructions put it. Nothing about this integration asks you to move, wrap or delay the Clarity tag, and doing so is more likely to break it than to help.
Switch the Clarity integration on
Open Web CMP and go to Integrations, then enable Microsoft Clarity. It is one of the built-in integrations, so there is no key to copy, no snippet to paste and no account to connect. From that point the banner sends Clarity a consent state on every page load, before your visitor has answered and again once they have.
Decide where the two signals start
Analytics storage and advertising storage each start denied, which is the right position anywhere prior consent is required. Both are settings rather than fixed values: if you deliberately run opt-out for some of your audience, either one can start granted instead. Change these on purpose, not by default, because it is the setting that decides whether Clarity stores anything before the banner is answered.
Confirm it in Monitoring
Consent Studio’s weekly crawl recognises clarity.ms as a tracking technology, so Clarity shows up in your scan results and in the cookie declaration your visitors can read. That turns the integration from something you trust into something you can check, and it is where you would notice if a second copy of Clarity were being loaded by a tool you had forgotten about.
A cookie banner alone is not enough
Most sites are leaking before anyone notices. Not through malice, but through a tag somebody added in a hurry, a vendor that changed its script, a plugin that phones home.
- Unconsented tracking
- Unwanted overseas transfers
- Consent records you cannot produce
- Scripts you never approved
The Full Consent Stack.
Three products, one consent record. What a visitor agreed to in the banner is what every downstream tag sees.
Which plan Microsoft Clarity needs, and why
Essential covers this. The Clarity integration is identical on every plan, so what changes as you grow is how many you run at once.
Essential is enough
€10/month
- The Microsoft Clarity integration
- Three integrations included, then charged
- Unlimited pages, 200,000 consent actions a month
What Professional adds
€36/month
Worth it once Clarity is one tool among many.
- More depth: HTTP consent cookies, accessibility, re-prompting
- Unlimited integrations, Essential includes three
- On-demand scans, not the weekly crawl
- Sitemap scanning, for unlisted pages
Every plan includes
Trusted by organisations that care about privacy
Frequently asked questions about Microsoft Clarity
Does Microsoft Clarity need cookie consent?
Yes, wherever prior consent is required, including the EU and the UK. Clarity records how visitors move, click and scroll, and it stores data on their device to do it. None of that is necessary to deliver your site, so it sits in the analytics category and needs an answer before it starts.
Does Microsoft Clarity have a consent API?
Yes. Clarity accepts a consent call that carries analytics storage and advertising storage as two separate values, which is what Consent Studio uses. That is why this integration signals Clarity rather than blocking its script, and why nothing about your Clarity setup has to change.
What does Consent Studio send Clarity if a visitor refuses?
Both signals go out as denied, and they go out before Clarity has been given the chance to store anything. If your visitor later changes their mind, the update follows immediately. What Clarity does once it has a denied signal is Clarity’s own documented behaviour, and Microsoft is the right source for it.
Do I need to remove or delay the Clarity script?
No. Leave it exactly where Microsoft’s installation instructions put it. Consent Studio does not depend on the Clarity tag being moved, wrapped in a placeholder type or held back, because it works through Clarity’s consent API rather than by stopping the script from running.
Does this work if I load Clarity through Google Tag Manager?
Yes. The integration calls Clarity’s consent API on the page rather than intercepting how the tag arrived, so it makes no difference whether Clarity came from Tag Manager or from a script in your template. Load it the normal way rather than holding it back behind the banner, so the signal has something to reach.
Get Started with the Full Consent Stack
Everything you need in one bundle. Consent Studio provides you with a consent banner, scanner and client-side tag manager that guarantees no data ever gets transferred overseas.
Read the documentation
Our help center walks through every integration, plugin and template step by step, with screenshots. It is written and kept current by the people who build Consent Studio.