Microsoft Clarity Consent Mode

Kukie can automatically send consent signals to Microsoft Clarity when visitors accept or deny cookies on your site. This integration uses the Clarity Consent API v2, so Clarity respects your users' privacy choices without any custom code on your part.

Overview

When it is on, Kukie.io sends each visitor's choice to Clarity as it is made: Analytics sets analytics_Storage and Marketing sets ad_Storage. When a choice leaves both off, Kukie.io also tells Clarity to erase its cookies. It is one switch in the Banner Editor, with no code changes.

Prerequisites

Before you enable this integration, make sure you have:

• A Kukie account with at least one verified site
• The Microsoft Clarity tracking code installed on your site (separately from Kukie)
• The Kukie banner script installed and working on the same site

Tip: Kukie.io does not install Clarity for you. Add the Clarity tracking code to your site separately. If Clarity has not loaded yet when a signal is sent, Kukie.io puts the signal in Clarity's own command queue, and Clarity reads it when it loads. With Auto-block Scripts on, Clarity is held until the visitor accepts Analytics.

How to Enable

1. Go to your site in the Kukie dashboard
2. Open the Banner Editor
3. Navigate to the Integrations tab
4. Toggle on Microsoft Clarity Consent
5. Click Save to publish your banner

Note: After enabling this integration, your banner script bundle will be regenerated automatically. The new version may take a few minutes to propagate through the CDN.

How It Works

Kukie communicates with Clarity at three key moments:

Default Consent State

On page load, Kukie sets Clarity consent defaults based on your site's consent model. For opt-in sites (GDPR), both parameters start as denied. For opt-out (CCPA) or notice-only sites, both start as granted.

User Accepts Cookies

When a visitor clicks "Accept", Kukie calls:

window.clarity('consentv2', {
    ad_Storage: 'granted',
    analytics_Storage: 'granted'
});

Clarity then begins (or continues) collecting session data normally.

User Denies Cookies

When a choice leaves both Analytics and Marketing off, for example Reject all, Kukie.io first calls window.clarity('consent', false) to erase Clarity's cookies, then sends both signals as denied. A later change of mind in the banner works the same way, on the same page.

Returning Visitors

For visitors who have already made a consent choice, Kukie restores their saved preference and sends the appropriate signal to Clarity on page load - no banner interaction required.

Consent Parameter Mapping

Consent Model Behaviour

The integration behaves differently depending on your site's consent model:

Testing the Integration

To verify the integration is working correctly:

1. Open your site with the browser DevTools Console open
2. Check that Clarity's script loaded: in the Network tab, filter for clarity.ms and look for the tag's request
3. Check that the integration is enabled: window.__KUKIE_CONFIG__.integrations.clarity_consent should return true
4. Accept cookies via the banner, then check Application > Cookies for _clck and _clsk
5. Clear your consent (or use a private window), deny cookies, and verify those Clarity cookies are removed

You can also monitor the exact calls Kukie makes to Clarity by pasting this snippet into the Console before interacting with the banner:

// Monitor Clarity consent calls
const origClarity = window.clarity;
window.clarity = function(...args) {
    console.log('[Kukie->Clarity]', ...args);
    return origClarity?.apply(this, args);
};

Troubleshooting

Clarity toggle is enabled but no consent signals are sent

Signals sent before Clarity loads wait in Clarity's command queue, so the order in which the two scripts load does not matter. If Clarity never loads, nothing reads the queue: check that the Clarity tracking code is on the page, and, with Auto-block Scripts on, that the visitor has accepted Analytics.

Clarity cookies appear even after deny

This usually happens when Clarity is loaded more than once on the page. Check your browser Console for the message Error CL001: Multiple Clarity tags detected. Remove any duplicate Clarity snippets so only one instance runs.

Consent signals are sent but Clarity dashboard shows no data

Clarity processes session data asynchronously. It can take up to 2 hours for new sessions to appear in the Clarity dashboard. Wait and check again.

Related Resources

• How to Set Up Microsoft Clarity Consent Mode - full setup guide with screenshots
• Microsoft Clarity Consent API v2 Documentation - official Microsoft reference
• Microsoft Clarity Consent Mode, moment by moment - what Clarity receives for each choice
• Google Consent Mode v2 - similar integration for Google services
• Microsoft UET Consent Mode - consent integration for Microsoft Advertising