Cookie Consent

What Is the Difference Between Microsoft Clarity ConsentV1 and ConsentV2?

The main difference between Microsoft Clarity ConsentV1 and ConsentV2 is how they handle consent signals for different types of data storage.

Metric	ConsentV1	ConsentV2
Status	Older Consent API; planned for deprecation	Latest and recommended method
Consent granularity	Uses a single consent state	Separates analytics and advertising storage consent
Consent signals	One general consent signal	`ad_storage and analytics_storage`
Analytics consent	Cannot be managed separately	Can be granted or denied independently
Advertising consent	Cannot be managed separately	Can be granted or denied independently
Tracking behavior	The same consent state applies across consent types	Clarity can respond separately to analytics and advertising storage choices
Recommended use	Existing implementations should transition away from it	Recommended for new implementations and CMP integrations

With ConsentV1, a single consent decision is applied across Clarity's consent types. ConsentV2 provides more granular control by allowing websites to send separate consent states for analytics and advertising storage.

For example, a website can grant analytics_storage while denying ad_storage, or apply the opposite combination. Microsoft identifies ConsentV2 as the current recommended method for passing cookie consent status to Clarity.

For new implementations, ConsentV2 should be used instead of the older Consent API.