Google mandates Consent Mode v2, do we have it right.
Consent Mode v2 has been required since 2024 if you use Google Ads or Analytics for EEA visitors. Without it, you lose conversion data.
Try this first
- 1Check your banner: does Cookiebot, CookieFirst or Complianz explicitly support Consent Mode v2? Recent versions yes, old ones no.
- 2In Google Tag Manager set a Consent template and attach it as a precondition to every tag (GA4, Ads, Floodlight).
- 3Defaults: ad_storage=denied, analytics_storage=denied, ad_user_data=denied, ad_personalization=denied. Only update after consent.
- 4Test in incognito with devtools > Network: pre-consent you see a gtag/js call with gcs=G100 (denied). After accept it becomes G111 (granted).
- 5In GA4 under Configuration > User-data settings, check that consent-mode data actually flows through.
- 6Document the implementation. Regulators and Google's compliance team can ask for evidence independently.
When to bring us in
Complex consent flows (per-country, server-side tagging, own CDP)? A GTM specialist or martech agency pays back. Misimplemented you lose data and compliance.
See also
- WordPress, plugins and theme have gone 6+ months without updatesOut-of-date WP is the number-one entry for malware. Don't just hit 'update all', back up first.
- Theme update broke the layout or threw a fatal errorThemes overwrite custom CSS on update unless you use a child theme.
- WordPress shows a blank screen after a plugin install or updateWSOD (white screen of death) is usually one crashing plugin. You isolate it.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.