Works with your stack
Cookie consent for Microsoft Clarity
recordings need a yes
The Microsoft Clarity plugin adds Clarity to every page once a project ID is saved. Clarity records how visitors use your pages. The plugin never tells Clarity about the visitor’s choice, so the tag itself has to wait.
By Microsoft · clarity.microsoft.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Microsoft Clarity
WordPress plugin
- Tested version
- 0.10.37
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 0.10.37 tested
- Active installs
- 200,000+
What Microsoft Clarity adds to your visitors’ browser
Trackers it loads
- Microsoft Clarity →Statistics1 browser storage key
Also from your server Logs each front-end page view on the server (IP address, browser, page address) and sends batches to Microsoft by cron, as soon as the site is connected; no setting to turn it off; a banner cannot stop it. A banner holds what runs in the visitor’s browser. What Microsoft Clarity sends from your server is set in Microsoft Clarity itself.
What matters for consent with Microsoft Clarity
Printed in the page
The Clarity loader is written straight into the head of every page, not added as a script WordPress can remove. Holding it means holding it by its address.
No consent call
The plugin never sends Clarity a consent signal and has no WP Consent API code. Clarity starts as if the visitor had agreed.
Page views from your server
Once connected, the plugin also records page views on your server and sends them to Microsoft in batches, with no setting to turn it off. No banner can stop it.
Brand Agents
If you connect Brand Agents, another script loads on every page, and shops get a cookie with session and customer data. It is off until you connect it.
Cookie Rocks with Microsoft Clarity
- Lets it load, and passes the visitor’s choice to it: refusal before, consent after.
What our tests found on Microsoft Clarity
Depends on a setting · Microsoft ClarityClarity's Brand Agents loads a Microsoft script and sets a cookie on stores
setting “Brand Agents” · by default: not connected
With Brand Agents connected and front-end injection on, a script loads from an Azure address on every front page for visitors not logged in. On WooCommerce stores, brandagent_attrs is set for 2 hours.
Read in its code, 16 October 2026, Microsoft Clarity 0.10.35.
Full detail
With Brand Agents connected and front-end injection on, the Microsoft Clarity plugin loads a script module from adsagentclientafd-b7hqhjdrf3fpeqh2.b01.azurefd.net on every front page for visitors who are not logged in. On WooCommerce stores, a REST endpoint called by that script sets the brandagent_attrs cookie for 2 hours (session, customer and conversation IDs, Clarity data, language, currency, country).
Set before the choice · Microsoft ClarityMicrosoft Clarity plugin loads Clarity on every page with no consent signal
Once a project ID is saved, the loader is printed directly in the page head, so it cannot be removed by its handle. The plugin never sends Clarity's consent signal and has no WP Consent API code.
Read in its code, 16 October 2026, Microsoft Clarity 0.10.35.
Full detail
The Microsoft Clarity plugin prints the Clarity loader inline in wp_head (www.clarity.ms/tag/<id>?ref=wordpress) on every front page once a project ID is saved, without wp_enqueue_script, so there is no handle to remove. It never calls clarity('consent') or consentv2 and has no WP Consent API code.
Sent from your server · Microsoft ClarityClarity plugin records page views on the server and sends them to Microsoft
Each page view (IP address, browser, page address) goes in batches to ai.clarity.ms every 5 minutes, with no setting to turn it off. No banner can stop it. Read in the code, not observed.
Read in its code, 14 October 2026, Microsoft Clarity 0.10.35.
Full detail
Once connected, Microsoft's official Clarity plugin records every page view on the site's server (IP address, browser, full page address, and the WordPress session token for logged-in users) and sends them in batches to ai.clarity.ms through a scheduled task every 5 minutes, with no setting to turn it off. No banner can stop it. Read in the code; the sending itself was not observed.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- Microsoft Clarity 0.10.37, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- The visitor’s choice reaches it: refusal before, consent after.
- Settings of the test: Clarity project ID (test value).
- Last run: Microsoft Clarity 0.10.37 on 7 November 2026, with WordPress 7.1.3.
Analytics and ad pixels
Other plugins of the same kind.
Questions
Does Cookie Rocks hold Clarity?
Cookie Rocks holds known trackers such as Microsoft Clarity until consent. What the plugin sends from your server is outside a banner’s reach.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For Microsoft Clarity users
Recordings wait for a yes.
clarity after consent
Every feature of the complete plugin for 30 days, no card.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.