EU privacy rules hit Clarity users

In partnership with

Microsoft Clarity just made compliance more complicated.

Starting October 31st, 2025, Clarity will enforce consent signals for page views from the EU, UK, and Switzerland. Even if you don't have traffic from these regions, they recommend implementing this anyway.

Here's what's happening and how to fix it.

The Problem

Clarity sets two cookies by default: clck and clsk. These fire immediately when someone hits your site, before they've given any consent.

That's a problem under EU privacy regulations.

The solution? Turn off Clarity's automatic cookie setting and only fire them after someone grants analytics consent.

The Simple Fix

Why Usercentrics Makes This Easier

Usercentrics sends separate consent signals for different types of tracking. Instead of just "consent granted" or "consent denied," you get specific signals:

  • cookie_consent_preferences

  • cookie_consent_statistics

  • cookie_consent_marketing

This granular control lets you fire different tags based on exactly what someone consented to.

For Clarity, you only need the statistics consent signal. That's analytics consent.

The Testing Process

The video demonstrates the complete testing workflow using Chrome's Cookie Editor extension and Tag Manager's preview mode.

The test sequence:

  1. Clear all cookies

  2. Load the site without granting consent

  3. Check that Clarity cookies aren't set

  4. Grant analytics consent

  5. Verify Clarity cookies fire

  6. Test edge cases (partial consent, denial)

Each step confirms the setup works correctly.

Why This Matters Beyond Compliance

This isn't just about avoiding regulatory issues. It's about respecting user choice.

When someone visits your site and sees a consent banner, they're making a conscious decision about data collection. Honor that choice.

Plus, getting consent implementation wrong can break your analytics entirely. Better to do it right the first time.

The Deadline Reality

October 31st, 2025 is not far away. It’s next week!

These implementations take time to test properly. You need to verify the setup works across different consent scenarios. You need to coordinate with your development team or agency.

Start now. 

Beyond Clarity

This same principle applies to all your tracking tools. Google Analytics 4, Facebook Pixel, any tool that sets cookies.

Each needs proper consent management. Each needs testing. Each needs documentation.

The good news? Once you understand the pattern for one tool, the others follow similar logic.

Getting Help

If consent mode feels overwhelming, you're not alone. But good news, our team is here to help. Book a call with me to learn more about our services.

The Bigger Picture

Privacy regulations aren't going away. They're expanding.

What starts as EU requirements often becomes global standards. Get ahead of this curve instead of constantly reacting to new requirements.

Build consent management into your standard operating procedures. Make it part of every new site setup, every tracking implementation.

Your future self will thank you.

To Your Measured Success!

--Jeff Sauer
Co-Founder of MeasureU

The Gold standard for AI news

AI keeps coming up at work, but you still don't get it?

That's exactly why 1M+ professionals working at Google, Meta, and OpenAI read Superhuman AI daily.

Here's what you get:

  • Daily AI news that matters for your career - Filtered from 1000s of sources so you know what affects your industry.

  • Step-by-step tutorials you can use immediately - Real prompts and workflows that solve actual business problems.

  • New AI tools tested and reviewed - We try everything to deliver tools that drive real results.

  • All in just 3 minutes a day

More Content From MeasureU

Reflections from London's Prompt Engineering Conference - context, libraries & more