The final phase of cookie consent enforcement for page visits originating from the European region (EEA, UK, and Switzerland) will go into effect on October 31, 2025. Going forward, site owners will need to send valid consent signals to Clarity to ensure full functionality of Clarity features for traffic from these regions.
Why This Matters
Starting October 31, all website owners that receive traffic from affected regions must send a valid user consent signal to Clarity before Clarity will collect analytics data or sets cookies on your visitor’s browser. Cookie consent is managed at the website level.
If cookie consent is not provided to Clarity by a website owner, Clarity will not place a cookie. As a result, certain Clarity features, such as session recordings, heatmaps, and funnel tracking, may be limited, incomplete, or unavailable.
These changes won’t impact the experience of the end user, who won’t see any visible changes or interruptions on your site.
How to Pass Consent
Each Clarity project operates independently and requires separate consent signal handling. Clarity supports several methods for passing consent signals to Clarity once consent mode is enabled. You can choose the one that best fits your Clarity project’s setup and compliance strategy:
1. Clarity Consent API
For custom websites or in-house consent solutions, the Clarity Consent API offers the flexibility to programmatically send consent signals based on your own logic or user interface.
2. Consent Management Platform (CMP)
If your CMP has a supported Clarity integration, you can automatically collect and pass valid consent signals without additional code. Check the Clarity-supported CMP list to confirm compatibility with your provider.
3. Third-Party Platforms
If you’re running Clarity through a third-party platform—such as a website builder, analytics suite, or tag manager—you can use their built-in consent handling to pass the appropriate consent signal to Clarity.
4. Google Consent Mode
Most CMPs now include built-in support for Google Consent Mode, allowing Clarity to automatically receive consent status from your existing implementation. Recommended for sites already implementing Google Consent Mode.
Next Steps
- Evaluate your current consent implementation to ensure you’re properly managing user consent. Clarity’s consent mode will automatically be enabled for all users originating from the European Economic Area (EEA), United Kingdom (UK), and Switzerland (CH), but it’s worth verifying its implementation in your project settings.
- Implement one of the supported methods for sharing consent signals (Clarity Consent API, CMP integration, third-party platforms, or Google Consent Mode).
- Test your configuration to confirm that consent signals are correctly received by Clarity.
- Review the Clarity Consent documentation for detailed setup instructions and code samples.
Taking these steps before the enforcement date will ensure a smooth transition and help prevent a reduction in your Clarity experience.
To learn more, please visit the Cookie Consent FAQs and our Consent Management documentation. If you have any questions or need assistance, you can contact our support team at clarityms@microsoft.com.