# What is the difference between consent mode and v2?

> For the complete site index, see [llms.txt](/llms.txt). Every page is also available as Markdown: replace the trailing slash with `.md` (`/pricing/` becomes `/pricing.md`), or send `Accept: text/markdown` to the page URL itself.

---

**Category:** Google Consent Mode
**URL:** https://www.cookieyes.com/knowledge-base/google-consent-mode/consent-mode-vs-consent-mode-v2/

---

Consent Mode manages user consent for data collection for Google Analytics and Google Ads. Consent Mode V2 was introduced in response to the European [Digital Markets Act (DMA)](https://www.cookieyes.com/blog/dma-compliance-for-publishers/), which requires more accountability and compliance from core platform services like Google.

> By March 2024, Google Consent Mode (GCM) V2 is mandatory for all websites in the EEA and UK using Google services like Google Ads and Google Analytics. Here's [how to implement GCM V2 with CookieYes](https://www.cookieyes.com/documentation/implementing-google-consent-mode-using-cookieyes/).
>

|  | Consent Mode | Consent Mode V2 |
| --- | --- | --- |
| Functionality | Involves two consent states: analytics_storage (for analytics) and ad_storage (for advertising). | Adds two new consent signals: ad_user_data and ad_personalization for more granular user consent.These signals provide information about user consent for remarketing and ad personalization. |
| Implementation | Requires website owners to ask for consent and communicate the consent status to Google. | Similar to Consent Mode, but with the addition of reporting consent status to Google. |
| Tracking | If a user declines tracking, Google will not track them at all, leading to no data in Google Analytics or Google Ads. | Allows for anonymous tracking of user behaviour even when consent hasn't been granted.  |