Data Protection, Digital Compliance & Data Security

How to Set Up Cookie Management with Consent Mode v2 Under KVKK

Google’s Consent Mode V2 update has opened a new chapter in cookie management and data transfers. It controls data collection technically according to user consent and aims to support compliance…

Digital compliance and cookie management • 2025

How to Set Up Cookie Management with Consent Mode v2 Under KVKK

Google’s Consent Mode V2 update has opened a new chapter in cookie management and data transfers. It controls data collection technically according to user consent and aims to support compliance with KVKK and GDPR requirements.

Summary: It is no longer enough to show only the cookie banner; user preference should be dynamically synchronized with Tag Manager and Google Ads / Analytics.

1. What is Consent Mode V2?

Consent Mode V2 is an API protocol governing whether Google services collect data based on user consent. The new version adds functionality_storage to categories such as ad_storage, analytics_storage and personalization_storage.



“Permission to process data is now a technical action as well as a legal one.”

2. Google Tag Manager and CMP integration

Consent Management Platform (CMP) systems record user consent and send it to Tag Manager. Without correct integration, cookies can run in the wrong category or without permission.

  • Create a Consent Initialization trigger in Tag Manager.
  • Connect the CMP, such as Cookiebot, OneTrust or iubenda, to GTM.
  • Update the Tag Manager signal whenever user preferences change.
Storage TypeGoogle Tag Manager parameterConsent status
Advertising / Marketingad_storage'granted' or 'denied'
Analytics / Performanceanalytics_storage'granted' or 'denied'
Personalizationpersonalization_storage'granted' or 'denied'
Functionalfunctionality_storage'granted' or 'denied'

3. Distinguishing performance and marketing cookies

The new cookie policies require functional classification, going beyond the "essential" and "optional" cookie distinction:

  • Necessary cookies: Required for site security and session management, for example PHPSESSID.
  • Performance cookies: Collect statistics such as page-load times and click rates anonymously.
  • Marketing cookies: Analyse user behaviour and support remarketing campaigns.
  • Personalisation cookies: Suggest content based on the user’s past preferences.


“Every cookie leaves a trace; that trace must be managed in accordance with KVKK.”

4. Balance Between KVKK and Technical Infrastructure

KVKK prohibits cookies that process personal data from running without explicit consent. Consent Mode V2 implements that consent technically. Cookie management is therefore a legal and technical process.

Compliance recommendations:
  • Consent wording should be simple, clear and separate for each category.
  • Start every cookie category as inactive by default.
  • When the user selects Accept, Tag Manager should automatically send granted.
  • Keep consent records, including timestamp, IP and category, for 12 months.

5. B10 Consent Mode integration model

B10 Digital Agency manages the technical and legal integration of Consent Mode V2 for brands:

  • GTM integration and event mapping,
  • CMP configuration for cookie categories,
  • KVKK-compliant consent wording and banner design
  • Logging and consent-record management
  • Preparing audit reports and test scenarios


“Proper consent enables accurate data collection; accurate data supports secure growth.”

Need guidance on adopting Consent Mode V2?
B10 Digital Agency offers end-to-end support for brands with KVKK compliant cookie policy, Tag Manager integration and CMP installation.

Request Consent Mode V2 integration Tags: cookie policy • Consent Mode V2 • Google Tag Manager • CMP integration • KVKK compliance • B10 Digital Agency

Sources and related documents

These documents provide references for the methods and rules discussed in this article.

B10 Digital Agency

How to Set Up Cookie Management with Consent Mode v2 Under KVKK