Short answer
If you use Google Ads, Google tags should receive a consent state before they collect optional analytics or advertising data. Consent Mode v2 is Google’s mechanism for communicating that state; it is not itself a cookie banner or a legal basis for tracking.
Most SMB advertisers need a clear consent choice, denied defaults before optional Google tags run, and updates after Accept, Reject, or granular preferences. A publisher using AdSense, Google Ad Manager, or AdMob can have additional certified-CMP and TCF requirements.
What to check
- Whether GA4, Google Ads, or GTM loads before a visitor chooses.
- Whether analytics_storage, ad_storage, ad_user_data, and ad_personalization begin denied where applicable.
- Whether Reject keeps optional Google tags blocked across another page view.
- Whether your business is an advertiser or a publisher monetizing with Google publisher products.
Practical steps
- Inventory Google tag paths: GTM, gtag, GA4, Google Ads, and theme or plugin snippets.
- Publish denied consent defaults before optional tags execute.
- Map banner categories to the four v2 parameters and test every visitor choice.
- Open the production site in a private window and inspect pre-consent requests.
- Run a GDPRChecker scan and record any finding before changing campaigns or tags.
Common mistakes
- Treating a visible banner as proof that Google tags are gated.
- Granting advertising consent when a visitor selected analytics only.
- Loading a second hard-coded gtag snippet outside GTM.
- Assuming Consent Mode v2 makes a normal banner or policy unnecessary.
Important boundary
Know the scope
GDPRChecker supports consent behaviour checks and Consent Mode v2 diagnostics. It is not a Google Certified CMP or an IAB TCF CMP. Use a certified CMP when your publisher scenario requires one.