Google Consent Mode, Microsoft UET and Clarity: Which Signals Control What?
ON THIS PAGE
- Understanding Consent Signals: Google Consent Mode, Microsoft UET, and Clarity
- Google Consent Mode Signals: What Do ad_storage, analytics_storage, ad_user_data, and ad_personalization Control?
- Microsoft UET Consent Signals: How Does ad_storage Affect Tracking and Advertising?
- Microsoft Clarity Consent Signals: How Do ad_storage and analytics_storage Affect Session Tracking?
- How to Manage Google and Microsoft Consent Signals with CookieScript
- Frequently Asked Questions
Google Analytics, Google Ads, Microsoft Advertising, and Microsoft Clarity use cookies and other website trackers to provide analytics and digital advertising functionalities.
However, the collection and handling of individuals’ Personal Information is regulated by data privacy laws, such as GDPR and the eprivacy Directive in Europe, CCPA/CPRA and other state laws in the U.S. Managing user consent is essential for compliance with privacy regulations.
Although Google Consent Mode, Microsoft UET Consent Mode, and Microsoft Clarity Consent Mode use similar consent signals, they manage consent differently. Each platform controls different tracking activities and uses different signals.
Understanding these differences helps you configure your Consent Management Platform (CMP) correctly, respect user privacy choices, and maintain reliable analytics and advertising measurement.
This guide explains how the three platforms handle user consent, which consent signals control what, and how to manage consent signals using a CookieScript CMP.
Understanding Consent Signals: Google Consent Mode, Microsoft UET, and Clarity
Consent signals are technical parameters that communicate a website visitor's privacy preferences to analytics and advertising platforms.
Data privacy laws require websites to get user consent before collecting users' personal data. When users interact with a Cookie Banner, they can accept or reject different categories of cookies, such as analytics or marketing cookies. A CMP translates these preferences into consent signals that supported tracking technologies can understand.
Each consent signal typically has two possible values:
- Granted: The user has provided consent for a certain category of cookies.
- Denied: The user has not provided consent or has rejected that category of cookies.
When websites obtain consent, they send consent signals to advertising platforms that use customers’ data for advertising and analytics purposes. Without consent, advertising and analytics functionalities are limited. Without consent, advertising platforms must respect user privacy, which limits the collection of user data; but to deliver advertising and analytics functionalities, they need user data.
Google Consent Mode, Microsoft UET Consent Mode, and Microsoft Clarity Consent Mode address this challenge using different approaches, scopes, and parameters.
Google’s approach
Google implemented Google Consent Mode v2, which has four consent parameters and offers two consent modes:
- Basic consent mode: Tags are blocked until consent is granted.
- Advanced consent mode: Tags fire with anonymized, cookieless pings. User data is not collected, but Google uses conversion modeling to model the data if consent is denied.
Google Consent Mode v2 communicates corresponding user consent preferences to Google services, including Google Analytics 4 (GA4) and Google Ads.
Microsoft’s approach
Microsoft Consent Mode also adapts tag behavior based on user consent, using Universal Event Tracking (UET). Microsoft UET is used for conversion measurement, campaign optimization, and remarketing in Microsoft Advertising. It supports two modes:
- Basic consent mode: Tags are blocked until consent is granted.
- Advanced consent mode: UET sends anonymized signals even without consent, though it lacks conversion modeling.
Microsoft Clarity Consent Mode manages consent for Clarity's behavioral analytics capabilities and advertising-related data sharing. Clarity helps website owners understand user interactions through features such as session recordings and heatmaps.
Although these platforms use some identical signal names, their consent implementations are separate. Enabling Google Consent Mode does not automatically mean that Microsoft UET or Clarity receives the appropriate consent signals.
Importantly, the same signal name does not necessarily control the same functionality across platforms.
Scan your website for free to see all your website cookies, including analytics and advertising cookies:
Google Consent Mode Signals: What Do ad_storage, analytics_storage, ad_user_data, and ad_personalization Control?
The key takeaway: Google uses separate signals for advertising cookies, analytics cookies, advertising-related user data, and ad personalization. Users can grant permissions separately for some of them while rejecting others.
Google Consent Mode v2 allows websites to communicate visitors' consent preferences to Google services. This helps Google tags adjust their behavior based on users' preferences. Consent Mode v2 contains four consent signals:
ad_storage: Controls ad-related storage.analytics_storage: Controls storage related to analytics.ad_user_data: Indicates consent for ad data collection.ad_personalization: Manages consent for personalized advertising.
Before user consent is given, set a denied consent state by default:
gtag('consent', 'default', {
ad_storage: 'denied',
analytics_storage: 'denied',
ad_user_data: 'denied',
ad_personalization: 'denied'
}); Once the user consents, the tag updates automatically.
ad_storage: Advertising cookie storage
The ad_storage signal controls whether Google advertising technologies can read and write advertising-related cookies and other trackers.
When ad_storage is granted, Google tags can use advertising cookies for advertising purposes such as conversion attribution and campaign measurement.
When ad_storage is denied, advertising cookies must be blocked. Advanced Consent Mode still allows sending certain cookieless signals for measurement purposes.
analytics_storage: Analytics cookie storage
The analytics_storage signal determines whether Google Analytics can use analytics-related cookies and identifiers.
When analytics_storage is granted, GA4 can use cookies to help measure website visits, user interactions, and sessions.
When analytics_storage is denied, Google Analytics cannot read or write analytics cookies.
However, the exact measurement depends on the Consent Mode implementation. With Basic Consent Mode, Google tags are blocked until the required user consent is obtained. With Advanced Consent Mode, Google tags may still load before consent and send cookieless measurement signals even when consent is denied.
ad_user_data: User data for advertising
The ad_user_data signal controls consent for sending user data to Google for advertising purposes.
It is particularly important for advertising measurement features that involve user-provided information, such as enhanced conversions.
When ad_user_data is granted, supported Google advertising features may process relevant user data, when other required consent conditions are satisfied.
When ad_user_data is denied, Google can’t use user data for the relevant Google advertising purposes.
This parameter is different from ad_storage. When consent for advertising-related user data is denied, advertising cookie storage allows cookieless pings when using Advanced Mode (consent for ad_storage), while sending Personally Identifiable Information (e.g., email, phone) must be fully restricted (consent for ad_user_data).
ad_personalization: Personalized advertising
The ad_personalization signal determines whether Google can use data for personalized advertising.
When ad_personalization is granted, Google can use personalized advertising features, such as remarketing.
When ad_personalization is denied, personalized advertising features are not allowed.
Read more about Google Consent Mode on Google’s site to verify the technical information.
Microsoft UET Consent Signals: How Does ad_storage Affect Tracking and Advertising?
Microsoft Advertising uses Microsoft Universal Event Tracking (UET) to measure conversions, understand campaign performance, and create remarketing audiences. Unlike Google Consent Mode v2, which uses four main consent signals, Microsoft UET uses just one consent mode: ad_storage.
What does ad_storage Control in Microsoft UET?
The ad_storage parameter determines whether the UET tag is authorized to read and write cookies on a user's device.
It supports two consent states:
- Granted: UET can read and write permitted advertising cookies to support conversion measurement and other advertising functionality that are used for remarketing.
- Denied: UET cannot read or write First-party advertising cookies, and third-party advertising cookie use is restricted.
In the European Economic Area (EEA), the UK, and Switzerland, ad_storage must be set to denied by default via the window.uetq push command before the tag loads.
When a user interacts with a Cookie Banner and grants marketing consent, the site updates ad_storage to granted, allowing tracking users through cookies.
Basic vs. Advanced Microsoft UET Consent Mode
Microsoft UET offers two consent modes to manage user tracking before consent.
- Basic Consent Mode blocks the UET tag until the user provides the required consent. Before consent, the tag doesn’t transmit any tracking requests.
- Advanced Consent Mode allows the UET tag to load even without consent. Like Google, Microsoft uses modeled data: if
ad_storageremains denied, Microsoft blocks non-essential cookies, but limited, anonymized signals are still send to Microsoft to support modeled conversions.
To support measurement and modeling while respecting user cookie preferences, Microsoft recommends setting the correct default consent state and update it whenever a visitor changes their preferences.
Without appropriate consent signals, conversion measurement and remarketing could be limited. Implementing UET Consent Mode helps website owners communicate advertising preferences correctly and maintain the measurement features available under each consent state while complying with data privacy laws.
Importantly, Microsoft UET's ad_storage parameter is separate from Google's ad_storage parameter. Microsoft’s UET uses ad_storage as its sole consent parameter to govern all advertising cookies and tracking behavior at once. In contrast, Google uses ad_storage as just one consent signal to separate cookie access from user data sharing and retargeting.
Websites must configure and test the behavior of Google Ads and Microsoft Advertising consent states separately.
Microsoft Clarity Consent Signals: How Do ad_storage and analytics_storage Affect Session Tracking?
Microsoft Clarity is a privacy-focused behavioral analytics tool that helps website and mobile app owners understand how visitors interact with their websites. Its implementation emphasizes user transparency and aligns with GDPR.
Its features include session recordings, heatmaps, and behavioral insights that can help identify usability problems and improve website performance.
Unlike Microsoft UET, which focuses on advertising consent, Clarity asks users for analytics consent. It separates analytics-related consent from advertising-related data sharing.
Microsoft Clarity Consent Mode uses two consent types:
analytics_storagead_storage
analytics_storage: session tracking and analytics cookies
The analytics_storage signal controls whether Clarity can use cookies for behavioral analytics.
When analytics_storage is granted, Clarity can set analytics cookies and track user interactions across pages and sessions, which is needed for its functionality.
When analytics_storage is denied, Clarity operates in no-consent (cookieless) mode. In this mode, the Clarity script still loads on your website; data collection is strictly limited to comply with privacy regulations.
When users don’t grant consent, Clarity does not write or read any First-party or third-party analytics cookies on the visitor's browser to persist session information. Clarity uses unique per-page identifiers: instead of tracking a user across their visit, it assigns a temporary, one-off identifier to each individual page view.
Because cookies are disabled and IDs reset on every page load, Clarity cannot link multiple page views together into a continuous user journey. Thus, analytics features become limited. But businesses still receive basic, anonymous page-level insights.
This distinction is particularly important for session recordings and behavioral analysis. For example, when a visitor rejects analytics cookies, Clarity may still collect limited cookieless information, but it can’t recognize returning users and reconstruct sessions.
Ad_storage: advertising-related data sharing
In Clarity, ad_storage determines whether Clarity can share relevant user information with Microsoft Advertising for advertising-related purposes.
When ad_storage is granted, Clarity can share supported data with Microsoft Advertising for remarketing and campaign measurement.
When ad_storage is denied, Clarity does not share data with Microsoft Advertising for advertising purposes.
Two separate consent states mean that a visitor can permit behavioral analytics without consenting to advertising-related data sharing.
What happens when users accept only analytics cookies?
When users accept only analytics cookies but reject marketing cookies, Clarity sets only analytics cookies to enable tracking features needed for behavioral analytics. Advertising-related data sharing with Microsoft Ads is disabled.
In Clarity, analytics_storage determines whether individuals allow to set analytics cookies on their websites, while ad_storage controls advertising-related data sharing.
On October 31, 2025, Microsoft started enforcing Clarity consent signal requirements for visitors from the EEA, UK, and Switzerland. Microsoft's current Clarity Consent API v2 supports separate analytics and advertising consent choices, providing more granular control over user tracking.
If the visitor rejects both analytics and marketing cookies, Clarity doesn’t set any cookies on users’ devices. It can operate in limited cookieless mode to provide just basic functionalities.
If the visitor rejects both analytics and marketing cookies, Clarity sets tracking and advertising cookies to enable corresponding functionalities.
Read more about Microsoft Clarity Consent API v2 to verify the technical information.
How to Manage Google and Microsoft Consent Signals with CookieScript
A Consent Management Platform (CMP) such as CookieScript helps centralize user consent collection and manage Google and Microsoft Consent signals, sending the appropriate preferences to supported platforms.
Managing consent separately for Google Analytics, Google Ads, Microsoft UET, and Clarity can get complicated, especially when a website uses all these technologies at once.
Therefore, businesses should use a CMP to manage consent for analytics and advertising signals of different platforms.
CookieScript provides integrations for Google Consent Mode v2, Microsoft UET Consent Mode, and Microsoft Clarity Consent API, and helps website owners manage consent preferences across multiple tracking technologies through a centralized cookie banner.
To manage Google and Microsoft Consent signals, perform the following steps:
Step 1. Implement a CMP
Implement a Consent Management Platform (CMP), that supports Google Consent Mode v2, Microsoft UET, and Clarity. CookieScript CMP supports all three platforms and could be used to collect and centrally manage consent signals.
Read the guide on how to implement Google Consent Mode with CookieScript.
Step 2: Configure your cookie banner
Next, create and configure your CookieScript cookie banner. The banner should clearly communicate what cookies and tracking technologies your website uses, what data is collected, and allow visitors to accept or reject specific categories of cookies.
Use a granular cookie banner so users can accept or reject non-essential categories independently.
Step 3: Enable Google Consent Mode v2
CookieScript supports Google Consent Mode v2 and allows website owners to map consent categories to Google's consent parameters.
CookieScript supports the four main Google Consent Mode v2 signals:
ad_storageanalytics_storagead_user_dataad_personalization
It also supports additional storage-related consent types, so you can configure the mapping between your cookie categories and Google consent types to reflect Google consent requirements.
Read the guide on how to enable Google Consent Mode v2.
Step 4: Enable Microsoft UET Consent Mode
CookieScript also supports Microsoft UET Consent Mode. For most websites, this corresponds to a marketing or targeting category.
When a visitor accepts the relevant cookies, CookieScript communicates the corresponding advertising consent state (granted or rejected) to Microsoft UET.
To enable Microsoft Consent Mode, go to your CookieScript user account > Settings > Frameworks, and check ENABLE MICROSOFT UET CONSENT MODE:
Step 5: Enable Microsoft Clarity Consent API
CookieScript also provides an integration for Microsoft Clarity's consent API.
To enable Microsoft Clarity Consent API, go to your CookieScript user account > Settings > Frameworks, and check ENABLE MICROSOFT CLARITY CONSENT API.
Configure the relevant analytics and advertising consent categories so Clarity receives the appropriate permissions. Users should be able to make separate consent selections for Clarity's analytics tracking and advertising-related data sharing.
Step 6: Test Your Consent Signals
After configuring the integrations, test whether your website communicates the correct signals.
Check the following scenarios:
- No user interaction with your cookie banner
All Cookie Consent states should be set to denied by default, and non-essential cookies should not be stored. - Accept all cookies
Confirm that analytics and advertising signals change to granted when users accept cookies on your cookie banner. - Reject all cookies
Verify that Google, UET, and Clarity respect the denied states and that restricted cookies are blocked from loading. - Accept analytics only
Check that analytics permissions are granted while advertising cookies remain blocked from loading. - Withdraw consent
Confirm that the platforms receive updated consent states and stop the loading of relevant cookie types.
You can use Google Tag Assistant, Microsoft UET Tag Helper, and browser developer tools to examine consent behavior or check CookieScript settings to check whether Google Consent Mode v2 is activated.
Test each platform separately because they use different and unrelated consent signals. Successfully configuring one of them, such as Google Consent Mode, does not guarantee that Microsoft UET or Clarity has been configured correctly.
CookieScript supports Google Consent Mode v2, Microsoft UET Consent Mode, Microsoft Clarity Consent Mode, and the latest version of IAB TCF. It is a Google-certified CMP and is in the GOLD Tier in Google's tiering system. It also offers affordable pricing.
Frequently Asked Questions
What is the difference between Google Consent Mode, Microsoft UET Consent Mode, and Microsoft Clarity Consent Mode?
All three platforms help websites communicate user privacy preferences, but their consent signals control different activities. Google Consent Mode v2 uses four main signals to distinguish between analytics storage, advertising storage, advertising-related user data, and personalized advertising. Microsoft UET primarily relies on ad_storage to control advertising cookie access and consent-dependent tracking functionality. Microsoft Clarity uses analytics_storage for analytics cookie access and ad_storage for advertising-related data sharing.
Why does Microsoft UET consent mode matter?
Microsoft UET offers two consent modes to manage user tracking before consent: Basic and Advanced. Implementing UET Consent Mode helps website owners communicate advertising preferences correctly and maintain the measurement features available under each consent state while honoring user privacy choices.
What happens when a user denies consent in Google Consent Mode, Microsoft UET, or Clarity?
When a user denies consent, the affected platform restricts its tracking activities. Google Consent Mode prevents the use of cookies associated with denied storage permissions but may still send cookieless signals in Advanced Consent Mode. Microsoft UET restricts advertising cookie access but may use cookieless measurement. Microsoft Clarity limits analytics cookie use when analytics_storage is denied and restricts advertising-related data sharing when ad_storage is denied.
How to manage Google Consent Mode, Microsoft UET, and Microsoft Clarity Consent Mode?
Use a Consent Management Platform (CMP), such as CookieScript, to manage consent preferences across multiple tracking technologies through a centralized cookie banner. A CMP centralizes user consent collection and manages Google and Microsoft Consent signals, sending the appropriate preferences to supported platforms.
Compare CMP prices and features side by side
Pick up to 4 consent platforms, set your number of websites and see yearly prices, pageview limits and features in one view.
- Yearly prices for 1 to 200 domains
- Pageview limits and extra fees
- Features and customer reviews