You have a cookie banner and Consent Mode in place, but you cannot tell if it actually works. A Consent Mode v2 audit reviews your signals, your tag gating, UET and your server-side consent, then gives you a written report of exactly what is broken and in what order to fix it.
A review with written findings. The audit reports; it does not change your setup.
present, default denied, updatingdo tags obey consentwhich is liveMeta, TikTok, Pinterestwhat to change, in orderA banner being present is not the same as consent working. An audit checks what the banner actually does to your tags, which a quick glance cannot show.
Your Meta, Google, TikTok or analytics tags load and send data before the visitor has agreed, so the banner is decorative rather than in control.
Consent Mode appears configured, yet the signals are not really updating on choice, or the four values are not all present.
Someone else built the banner and tag setup, and you do not know what it sends, to whom, or whether it still works.
A full review of how consent is captured and whether every tag and the server actually respect it.
Whether ad_storage, analytics_storage, ad_user_data and ad_personalization are all present, set to denied by default, and updated to the visitor's choice, wired correctly in Google Tag Manager.
The core question: do your tags actually wait for consent, or do they fire regardless of what the visitor chose. This is where most setups quietly fail.
Which mode is actually live, and whether it matches what you intended, since the two behave very differently before consent.
Whether Microsoft UET, Meta, TikTok and Pinterest tags respect consent or fire too early.
Where you run a server container, whether the consent state actually travels with the request or is lost at the web layer.
A written report of every finding, ranked by impact, with what to change. The audit reports and plans; it does not change your setup.
Async from start to finish. You always know what happens next, in writing.
Viewer access to your Google Tag Manager and the relevant accounts, plus your site. No passwords or keys in messages.
I follow consent from the banner through the signals to every tag and the server, checking what obeys it and what does not.
A written report of what is broken and why, with the fixes ranked by impact.
Apply the report yourself, or have it built as a separate step through the Consent Mode v2 setup.
Ready to build? See the Consent Mode v2 setup.
The audit reviews your current setup and tells you what is broken, in writing, without changing anything. The Consent Mode v2 setup is where those fixes are actually built.
No. This is a technical review only. Privacy rules differ by country and change over time, so confirm your own obligations with a qualified source. The audit tells you what your signals and tags are doing, not whether you meet the law.
Only after the order is confirmed, and only viewer access to your Google Tag Manager and the relevant ad and analytics accounts, plus your website. Passwords and keys are never shared in messages.
No. The audit includes the report and a ranked list of what to change. Implementing it is a separate step you can do yourself or have me handle through the setup.
Yes, the common ones such as Cookiebot, CookieYes and Complianz, as well as custom setups. What matters is whether consent reaches and controls your tags, whichever tool creates the banner.
Reference: Google's documentation on consent mode.
Send your site, the banner you run and the platforms you use. You get a written report of what is broken and how to fix it, with no calls.