{"id":12508,"date":"2026-09-10T00:28:16","date_gmt":"2026-09-09T21:28:16","guid":{"rendered":"https:\/\/brandaft.com\/?p=12508"},"modified":"2026-09-10T00:48:38","modified_gmt":"2026-09-09T21:48:38","slug":"consent-mode-v2-conversion-tracking","status":"publish","type":"post","link":"https:\/\/brandaft.com\/en\/consent-mode-v2-cerezsiz-donusum-olcumu\/","title":{"rendered":"Consent Mode v2: What It Breaks in Your Conversion Data (and How to Fix It)"},"content":{"rendered":"

\u201cOur ad conversions have dropped, but sales haven\u2019t changed.\u201d<\/p>\n\n\n\n

That\u2019s the sentence we hear most often after a cookie consent banner goes live. The chart in the ads dashboard goes down while the figures in accounting stay the same. When the two don\u2019t match, the question becomes: which one is right?<\/p>\n\n\n\n

Both are. They just aren\u2019t measuring the same thing.<\/p>\n\n\n\n

What\u2019s missing from the dashboard isn\u2019t sales, it\u2019s the visibility of sales<\/strong>. When a user rejects cookies, the purchase still goes ahead; only the trail linking that purchase to your ad account disappears. The measurement system goes blind, and you mistake that blindness for a drop in performance.<\/p>\n\n\n\n

At this point most articles take you straight to a setup step: add this tag, tick that box. But the setup isn\u2019t the real issue. The real issue is mistaking two separate problems for one.<\/strong><\/p>\n\n\n\n

On one side there is compliance<\/strong> \u2014 what KVKK (Turkey\u2019s data protection law, comparable to GDPR) requires for cookies. On the other side there is measurement<\/strong> \u2014 how much of your ad data you lose when consent is declined. The two appear at the same time, but they are not the same thing, and they are not solved with the same tool.<\/p>\n\n\n\n

There is also a misconception specific to Turkey. In its own documentation, Google defines the Consent Mode v2 requirement for users in the European Economic Area (EEA)<\/strong> ; it states that from March 2024 the consent fields must be \u201cGRANTED\u201d for Customer Match lists to be usable in the EEA (Google Ads Help<\/a>). Turkey is not an EEA member. In other words, Google isn\u2019t forcing you.<\/strong><\/p>\n\n\n\n

That doesn\u2019t mean \u201cthere\u2019s no need\u201d. Because:<\/p>\n\n\n\n

Even if Google doesn\u2019t force it, KVKK does. And even without KVKK, your measurement would already have been broken.<\/p>\n\n\n\n

In this guide we will clarify:<\/p>\n\n\n\n