How to check Consent Mode v2 is working: a Tag Assistant test and a cookie test.
- “how to check Consent Mode v2 is working”
- “how to verify Consent Mode v2 implementation”
- “Tag Assistant consent tab empty”
- “Tag Assistant On-page Default On-page Update”
- “consent mode status Google Ads diagnostics”
- “is consent mode v2 set up correctly”
- “check consent mode in the network tab gcs”
Baris Asa, tracking consultant, London · Filed 7 November 2026 · Last checked: 7 November 2026
Open Tag Assistant, accept the banner, and read the Consent tab.If any signal is blank, or says granted before you clicked where your policy requires denied, Consent Mode is probably mis-wired. That is F-201 (F-201 , Consent Mode absent or mis-wired).
A correct set-up is what lets Google model conversions from visitors who decline, and it is one place to look when GA4 or Google Ads conversions sit below Shopify’s.
This is a desktop Chrome job. On your phone? Forward this to whoever runs your Google Tag Manager with one line: “Send me a screenshot of the Tag Assistant Consent tab before and after I accept the banner.”
Two terms. The default is each consent switch’s state before the visitor answers the banner. The update is its state after. Consent mode has several types; four of them matter for Google Ads and GA4 under v2: ad_storage, analytics_storage, ad_user_data and ad_personalization (Set up consent mode on websites).
A wrong set-up gives no visible error. The banner shows and the page loads. It only shows in the Consent tab and the cookies. What that costs you is in Conversions dropped after implementing Consent Mode v2. Building it in the right order is in How to implement Consent Mode v2 correctly in GTM. Which mode you run is in basic vs advanced.
How do I verify my Consent Mode v2 implementation in Tag Assistant?
Use a fresh Incognito window. A stored choice from an earlier visit fills in the Update column and leaves cookies behind.
- Open Google Tag Assistant, enter the site’s URL, and let it open your site in a new tab. If it says “Could not connect”, commonly an ad blocker, a pop-up blocker or a tag that is not on the page.
- Do not touch the banner yet. In Tag Assistant, open the Consent tab and read the On-page Default column. (The same information is in the Summary: select the earliest Consent event and read its API Call section.)
- In the banner, accept all. Read the On-page Update column. It should read granted for all four.
- Open a fresh Incognito session, press reject, and read the Update column again. It should read denied, or show no update at all if your banner skips the update on reject. Either way no signal may read granted. Google’s guide uses “accept all”; the reject run is my addition, because declined visitors are a share of your traffic.
If your set-up is meant to start denied, the default column should read denied; Google’s guide shows the same tab (verify consent mode). A good Consent tab, written out:
| Signal | Default | Update after accept |
|---|---|---|
ad_storage | denied | granted |
analytics_storage | denied | granted |
ad_user_data | denied | granted |
ad_personalization | denied | granted |
A failing one is below: a constructed text rendering of one pattern (two signals handled, two never set), not a screenshot of any client. Blank means you have this problem.
| Signal | Default | Update after accept |
|---|---|---|
ad_storage | denied | granted |
analytics_storage | denied | granted |
ad_user_data | (blank) | (blank) |
ad_personalization | (blank) | (blank) |
What the failures mean:
| What you see | What it means |
|---|---|
| Consent tab empty | Google’s guidance: consent mode is not implemented on this page. Check the banner code runs here and the container loads |
| Some signals set, others blank | An incomplete default or update. Each signal needs its own default, and an update for every signal that has one |
| Tag Assistant says a tag read consent state before a default was set | Tag Assistant flags a tag that read consent before any default existed. Check the default fires on Consent Initialization (see below) |
| Reject leaves any signal granted | The banner grants on reject. Wrong for measurement and for the visitor |
| All four denied, then all four granted on accept | Correct. Go on to the cookie test |
Once you have ruled out the wrong container or tab, and a deliberate regional default, the failing rows are F-201 F-201 . Failing? Send the Consent tab screenshot to me via Consent Mode setup and repair. I will tell you if it is a quick fix or a rebuild.
For whoever owns the container. Google says not to set defaults asynchronously and not to call the gtag consent command from a Custom HTML tag (a free-form code tag): use a template tag. In Google Tag Manager the tag that writes consent belongs on the Consent Initialization trigger, which fires before everything else (verify consent mode, consent settings).
Do the Google tags actually follow the answer?
Yes if no Google tag writes cookies while its signal is denied. Google’s own test is whether a tag “behaved according to the consent settings” (verify consent mode). In Tag Assistant open the Summary, select Tags, and click a Google tag, then compare it with the state on the Consent tab. Google does not document a per-tag pass mark beyond that.
The cookie test is my own method, not Google’s. Use a clean Incognito window, in a region where your default is denied. In Chrome DevTools open Application, then Cookies, and look at your domain for names starting _ga (including _ga_<container ID>) or _gcl_ (such as _gcl_au and _gcl_aw). Cookies from other vendors are outside this test. If any appear before you answered, or after you rejected, a cookie with a Google name appeared while its signal was denied. Find which tag or script wrote it (the Tags view in Tag Assistant) before you call it F-201 F-201 ; a consent banner script can write them too. In a reused browser it proves nothing, because the cookies may be left from an earlier consented visit. Cookies set by a server container are a separate fault: Consent Mode v2 with server-side GTM.
What a tag does before the answer depends on the mode: basic vs advanced. If the result is a surprise, the cause is usually wiring: Cookiebot and GTM Consent Mode v2: why the tags still get the wrong consent state has the screenshots and a list of faults.
Does the default work for UK visitors and the rest of Europe?
Ask your developer one question: is the UK written GB, not UK, in the regional defaults? The ISO 3166-2 code for the United Kingdom is GB, and Google’s setup guide says regions use those codes and the more specific region wins (Set up consent mode on websites). A row written UK would not match, and the visitor would fall to the global default. Then read the Consent tab once from a UK location and once from outside Europe. The right result is the default your privacy policy requires, a decision for whoever owns that policy.
For the developer. Google says to set your visitor location in Chrome and repeat the checks for each region (verify consent mode). My route for that is DevTools, Sensors, Location, then reconnect Tag Assistant. It changes only the browser’s reported location, so it will not move a banner that decides the region from the visitor’s IP address; for those, a VPN or the banner tool’s own test option is the reliable route. Check all four signals in every region row: a row that sets only some leaves the rest to the global default.
What does Google Ads Diagnostics say about it?
The checks above are yours. This is Google’s view. In Google Ads, go to Goals, then Conversions, then Summary. Select a website conversion action and open the Diagnostics tab (Set up and manage consent).
| Status | Meaning |
|---|---|
| ”Consent mode is implemented” | Set-up detected. The account has not met the thresholds for modelling (Google estimating conversions from visitors who declined). Google gives 700 ad clicks over 7 days for a domain and country grouping |
| ”Consent mode is implemented and modeling is active” | Modelling has started. Nothing to fix |
| No consent status shown | Google’s page does not say what this means. Tag Assistant is the proof. If it passes, wait out the timing below |
Google says the active status can take 48 hours to appear, and in some cases up to 2 weeks. Tag Diagnostics, under View diagnostics in the Google tag settings, can also raise consent alerts (Tag Diagnostics):
| Alert | Google’s description |
|---|---|
| ”Consent mode installation out of order” | Some pages load consent mode commands in the wrong order |
| ”Verify consent mode set up as 0% consent rate detected” | You always send an ad_user_data denied signal regardless of geo settings |
| ”0% consent rate detected in some regions” | You always send ad_user_data denied in non-EEA regions |
What do I do with the result?
Everything passed: the wiring is right as far as a browser can show. Server containers and banner vendors have their own faults: Consent Mode v2 with server-side GTM.
The Consent tab or the cookies failed: that is F-201. Send the screenshot, as above.
Only Google Ads failed: if Tag Assistant passed, a missing status inside Google’s 48 hours to 2 weeks is consistent with delay. After that window, treat it as a fault.
Common questions
Can I check Consent Mode with only the network tab?
As a quick signal, yes, not as proof. In Chrome DevTools, Network, filter for GA4 collect requests. The gcs parameter appears to cover only ad_storage and analytics_storage; gcd appears to carry all four v2 signals. Both are community-documented, not Google’s, and Ads requests go to other hosts. If they disagree with Tag Assistant, trust Tag Assistant.
What does it mean if the Tag Assistant Consent tab is empty?
Google’s guidance is that consent mode is not implemented on that page. Check the banner code runs there and Tag Assistant connected to the right container.
How long does the Consent Mode status take to appear in Google Ads?
Google says up to 48 hours, and in some cases up to two weeks. If Tag Assistant already shows a correct default and update, a missing status in that window is consistent with delay.
The wider picture, with every Consent Mode question in one place, is in Google Consent Mode v2 explained.
Sources
Read on 7 November 2026:
- Google for Developers, verify consent mode (Tag Assistant steps; On-page Default and Update; empty tab; regional checks; update mechanism; async and Custom HTML warnings)
- Google for Developers, set up consent mode on websites (ISO 3166-2 regions; more specific region wins; region-less default)
- Tag Assistant Help, consent state in Tag Assistant (blank Consent tab; “A tag read consent state before a default was set”)
- Google Ads Help, set up and manage consent (Diagnostics statuses; 48 hours, up to 2 weeks; 700 ad clicks over 7 days)
- Google Ads Help, troubleshoot tag issues with Tag Diagnostics (consent alerts)
- Tag Manager Help, consent settings (Consent Initialization fires before all other tags)