Microsoft Clarity Consent Mode
Turn it on, read the behaviour per consent model and test it, with troubleshooting.
Clarity follows each visitor's choice.
Clarity asks for a consent signal on visits from the EEA, the UK and Switzerland.1 Kukie.io sends both of Clarity's signals from your cookie banner and clears Clarity's cookies after Reject all.
Microsoft Clarity Consent Mode is available on the Pro, Agency and Unlimited plans.
Watch the explainer
The two signals Clarity reads, the one switch that sends them, and a visitor's choice reaching Clarity on the same page.
2 minutes 30 seconds, narrated, with captions in the player. The sites and rules in it are examples.
What the signals do
Clarity reads two consent signals. Kukie.io sets each one from its own category, so a visitor can allow analytics and still refuse advertising.
analytics_Storage
Follows Analytics
ad_Storage
Follows Marketing
Read Microsoft's description of each signal (opens in a new tab)
How it decides
The default comes from your region rule, and each choice updates both signals. Choose a moment to see the call Clarity receives and what happens to its cookies.
The call Clarity receives
clarity('consent', false)
clarity('consentv2', { analytics_Storage: 'denied', ad_Storage: 'denied' })
Clarity's cookies, _clck and _clsk
Not setThe default under an opt-in rule, sent as the page loads. Clarity sets no cookies while analytics_Storage is denied.
In any order
Clarity can load before the banner, after it or only once a visitor accepts Analytics. The signals reach it each time.
Kukie.io puts each signal in Clarity's own command queue, so none is lost while the script is on its way.
Clarity reads the queue when it starts, so it begins with the visitor's current choice.
Reject all in the banner later erases Clarity's cookies and sends denied, on the same page.
With Auto-block Scripts on. Clarity is a known Analytics script, so Kukie.io holds it until the visitor accepts Analytics. The queued signals reach Clarity when it loads.
Check it yourself
You need your site and your browser's developer tools. Nothing here needs a Clarity account.
Select Accept all, then open Application, then Cookies. Select Reject all in the banner and both are gone:
Use a private window, so an earlier choice does not answer for you.
Open Console and check that Clarity is on the page and that the switch reached your banner:
New sessions can take up to 2 hours to show in your Clarity dashboard.
Before you start
Microsoft Clarity Consent Mode is one switch. These make sure Clarity reads the signals Kukie.io sends.
Kukie.io does not install Clarity. Add its tracking code once, because a second copy on the page can set cookies again.
Microsoft turns it on for visits from the EEA, the UK and Switzerland. For other regions, turn it on in your Clarity project's settings.
The default before a choice comes from each region rule: denied under opt-in, granted under opt-out or notice only.
Microsoft Clarity Consent Mode is available on the Pro, Agency and Unlimited plans.
Setup
There are no changes to your Clarity code and nothing to write.
Works on its own or beside the other consent signals
Documentation
Step-by-step guides in the Help Centre, and the other signals Kukie.io sends.
Turn it on, read the behaviour per consent model and test it, with troubleshooting.
Send the same choice to the UET tag of Microsoft Advertising.
Run your own Matomo with tracking that follows each choice.
Turn on Microsoft Clarity Consent Mode in a few minutes, with no change to your Clarity code.
Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.