A cookie banner on the page is not proof that Google Consent Mode v2 is doing its job.
If you are running Google or Meta ads next week, what matters is whether the four consent signals — ad_storage, analytics_storage, ad_user_data and ad_personalization — start denied, and then update when someone accepts or rejects. The banner can look fine while the defaults are missing, a new tag ignores consent, or a cached page serves a stale state.
This is a practical check, not a legal lecture. If you have not set Consent Mode up yet, start with my setup guide and WP GCP. If the banner is already live, use the steps below, and do the check in Tag Assistant, not by looking at the front end.
What you are checking
For visitors in the EU, EEA and UK, you want this pattern:
- Before anyone touches the banner, all four signals are denied.
- After Accept, they update to granted.
- After Reject, they stay denied — or they update to denied, and stay there.
- The default is set before any Google tag fires.
WP GCP is built to do that. You still need to confirm it on your site, with your tags.
1. Check the defaults in Tag Assistant
Open a private window, so you are not carrying an old consent cookie, then go to tagassistant.google.com and enter your site URL. If it cannot connect, the container may be blocked until consent — accept once to hook Tag Assistant up, then start again in a fresh private window.
Do not click the banner yet.
In the Summary, select the earliest Consent event. In the API Call section, check that all four signals were set. Then open the Consent tab and look at the On-page Default column. It should read Denied for all four.
If the Consent tab is empty, Consent Mode is not running on the page. If the defaults show Granted, or appear only after a Google tag has already fired, the default was missed or set too late. In WP GCP, that is usually a missing or wrong Google Tag Manager ID, or another script setting its own defaults. Fix that before you test Accept.
2. Accept, then reject, in separate sessions
Still in Tag Assistant, accept the banner. Select the most recent Consent event. The On-page Update column should now show Granted for those four signals. Open the Tags tab and check that your Google tags behaved accordingly.
Then start a new private session and reject instead. This is the path most people skip, and the one that usually breaks. The signals should stay denied. In advanced Consent Mode — the mode WP GCP uses — Google tags may still send cookieless pings. That is expected. What should not happen is a full measurement hit, or Google analytics and ads cookies being written (_ga, _ga_…, _gcl_au and the like).
If Accept works and Reject does not, the banner is talking to the page, but the update is not reaching the tags.
3. Confirm it in the network requests
In the same private session, open the browser’s developer tools, go to Network, and filter for collect. GA4 hits usually go to a URL containing /g/collect. Look for gcs, which carries ad_storage and analytics_storage: G100 means both are denied, G111 means both are granted. A gcd parameter may also be there, covering the v2 signals, but Google has said that encoding can change, so use the Consent tab in Tag Assistant for ad_user_data and ad_personalization. If gcs is missing, the tag is not picking up a consent state.
4. Do a test purchase, twice
If you run ads, a pageview check is not enough.
In a private window, accept the banner, then complete a test purchase or the conversion you will be bidding on. In Tag Assistant, confirm the conversion tag fired with consent granted. If you use GA4, open Admin → Data display → DebugView. With Tag Assistant connected, the purchase should appear there after you accept.
Repeat the journey in a fresh private window, this time with Reject. DebugView does not show events until the visitor consents to Analytics cookies, so an empty DebugView on the reject path is expected. You may still see cookieless pings, which is how advanced Consent Mode feeds Google’s modelling, but you should not see the usual Google cookies, and the conversion should not be treated as consented.
Do not wait for the green “Consent mode is implemented” badge in Google Ads Diagnostics. Google says that status can take 48 hours, sometimes up to two weeks. Use Tag Assistant the day before the campaign.
5. Re-check after you add Black Friday tags
This is the one that catches people out in late November. You add a Meta pixel, a TikTok tag, or a new Google Ads conversion, and the banner still looks fine. The new tag may not be checking consent at all.
After any tag or pixel change, confirm Consent Mode is enabled in GTM under Admin → Container Settings (“Enable consent overview”). Then open the new tag and check Advanced Settings → Consent Settings. Google tags have built-in consent checks, so “No additional consent required” is usually correct for those. For a provider that does not, use “Require additional consent for tag to fire” and add the types it needs. I cover this in the setup guide.
Run the Tag Assistant checks again, including a test conversion if the new tag fires on a purchase. Then purge your page cache and any CDN cache. A cached page can serve an old copy, or even one that already looks consented. Do the final check in a private window after the cache is cleared, not while you are logged in as an admin.
Where WP GCP fits
WP GCP is the plugin I built for this. It is a WordPress cookie banner with native Consent Mode v2, including ad_user_data and ad_personalization. You give it a Google Tag Manager container ID — no Google Partner CMP or Tag Manager template required — and it sets consent to denied, then updates it and reloads Tag Manager after the visitor accepts or rejects.
It costs €19 a year for one domain, VAT included, with lifetime updates. It gives you the consent mechanism. It does not, on its own, make the site “GDPR compliant”. If you need a view on that, speak to a solicitor. I will not pretend otherwise.
If the checks above fail, start with the obvious settings in WP GCP: a valid Google Tag Manager ID, a privacy policy page assigned under Settings → Privacy, and “Show the GDPR/Privacy Policy modal popup” ticked. Leave “Hide Deny/Reject button” unticked while you test Reject — you cannot verify a button that is not there.
Black Friday
If you need the plugin, or any of the others, the getButterfly Black Friday sale runs from 27 to 30 November 2026. Use code BF2026 for 40% off every plugin and the Saturn theme. It applies to the first year only, on new purchases, and the offer ends at midnight Irish time on 30 November. Details are on the Black Friday deals page.