UC WidgetsBlog

What is Google Consent Mode v2 and how do you set it up?

Consent Mode v2 is the technical bridge that passes a visitor's cookie choice to Google's tools. What it is, how it relates to KVKK/GDPR, what happens when consent is denied, and how to set it up without code.

19.08.2026 7 min read consentkvkkgeo
What is Google Consent Mode v2 and how do you set it up?

What is Google Consent Mode v2?

Google Consent Mode v2 is a technical bridge between the cookie banner on your website and Google's tools (Google Ads, GA4, Google Tag). It takes the visitor's "accept / reject" choice and passes that preference to Google's tags in machine language, so Google behaves in a way that respects the user's consent.

Released at the end of 2023, v2 added two new signals to the previous version: ad_user_data and ad_personalization. Without these, remarketing and conversion measurement for European users are restricted.

How it relates to KVKK and GDPR

KVKK and GDPR require explicit consent before processing personal data. Consent Mode v2 makes this principle technically enforceable: the default state is set to "denied"; until the user consents, Google tools drop no cookies and use no personal data. Once the user chooses, that preference is passed to Google.

What happens when consent is denied?

A common misconception is "if they reject, no data comes at all." With Consent Mode v2 the tags do not shut down completely; they send cookieless, anonymous signals with no personal data. Google models from these aggregated signals to partly fill the measurement gap. The result: compliance is preserved, but you are not left completely blind.

How do you set it up without code?

With UC Consent the steps are:

  1. Create a free account and enable UC Consent.
  2. Set your cookie categories (necessary, analytics, marketing) and banner texts in the panel.
  3. Add one line of code to your site; the banner goes live automatically.
  4. The visitor's choice is automatically turned into a Consent Mode v2 signal and passed to Google Tag / GA4 / Google Ads.

It also includes script blocking before consent and a provable consent log (who consented to what, and when, for audits).

Verifying the setup

  • Check that gtag('consent', ...) calls run, using Google Tag Assistant or the browser console.
  • Confirm that analytics/marketing cookies are not dropped when you reject on the banner.
  • Watch the consent state change per page in GA4 DebugView.

Frequently asked questions

Is Consent Mode v2 mandatory?

If you use Google Ads and GA4 for remarketing and conversion measurement for users in the European Economic Area, Consent Mode v2 is effectively required; without it, data collection and personalization for those users are limited.

Is Consent Mode v2 the same as a cookie banner?

No. The cookie banner collects consent from the visitor; Consent Mode v2 passes that consent to Google's tags. They work together: the banner says "granted/denied" and Consent Mode carries it to Google.

Can it be set up without code?

Yes. With UC Consent you add the banner to your site with one line of code; the visitor's choice is automatically turned into a Consent Mode v2 signal and passed to Google Tag / GA4. You manage categories and texts from the panel.

Manage everything in this article from one panel

WhatsApp, booking, cookie consent and SEO tools on one platform; all Pro features free for 14 days.

Create a Free Account