madmasel.hu / 12 September 2026
Consent Mode v2: a cookie banner is not a measurement strategy
For a live Google Ads campaign, a polished consent UI was not enough. Measurement commands had to follow the actual consent state, including phone-click and page-view conversions.
Situation
madmasel.hu was receiving paid traffic, so a tracking error could directly distort campaign decisions. The legacy site carried several historical scripts and measurement approaches, while Google Ads Consent Mode v2 required explicit state handling. A banner asking for consent does not prove that the tag behind it is initialized correctly or that updates happen in the right order.
Approach
I handled the default consent state separately from the post-acceptance update, then connected Google Ads conversion events to that runtime. Phone clicks and views of the relevant car-purchase page were tracked as separate events. I finished by checking the actual tag behaviour in the browser, not just by reviewing the source code.
Outcome
The campaign measurement chain became consent-aware and remained verifiably functional after the Engine migration. Tracking was no longer an isolated snippet embedded in HTML; it became a documented and testable part of the site's runtime behaviour.