Most teams treat Consent Mode v2 as a banner problem. It is not. It is a tag-sequencing problem, and the teams losing the most GA4 and Google Ads data are the ones who installed a consent banner, saw the green checkmark in their CMP, and moved on.
If your consent-denied traffic looks like it vanished from reporting, the banner is probably fine. Your defaults, your load order, or your choice of Basic versus Advanced mode is what is eating the data.
Basic and Advanced are not a UI choice
In Basic mode, Google tags do not load at all until a visitor consents. Denied visitors send nothing. No pings, no signal, no modeling input from that session. In Advanced mode, tags load immediately with all storage defaulted to denied, and send cookieless pings that carry no identifiers. Google uses those pings, plus consented traffic, to model the conversions and sessions it cannot observe.
The practical difference: Basic gives you clean, legally conservative data with a hole in it. Advanced gives you a modeled estimate of the hole. Modeling requires enough consented traffic and enough ping volume to train on, so a low-traffic site may never see modeled data in either mode.
Our position: if you run paid media in Google Ads and your audience includes regulated regions, run Advanced and get legal sign-off in writing. If you cannot get that sign-off, run Basic on purpose and stop expecting modeled conversions. The worst setup is Basic mode with the expectation of Advanced results, which is the most common one we audit.
| Area | Basic | Advanced |
|---|---|---|
| Tag loading | Blocked until consent | Loads immediately, storage denied |
| Denied visitors | Zero data sent | Cookieless pings only |
| Modeling in GA4 and Ads | Limited, no ping input | Full behavioral and conversion modeling |
| Risk posture | Most conservative | Needs explicit legal approval |
| Best for | Low traffic, strict regions | Paid media teams with volume |
The three failures we see in every audit
The default fires after the tags. Consent Mode only works if the default consent state is set before any Google tag executes. If your Google tag or GTM container loads first and the CMP script sets defaults a few hundred milliseconds later, the first hit goes out with undefined consent. Fix it by putting a gtag consent default call in the head, above the GTM snippet, not inside a tag that fires on page view.
The update never arrives for returning visitors. A returning visitor with a stored choice needs the CMP to push an update call immediately on load. If the CMP restores the choice asynchronously, the page view fires first under denied defaults and you permanently undercount your most loyal users. Set a wait_for_update value in your default so tags hold briefly for the stored state. Keep it short, a few hundred milliseconds, so you do not tank your load metrics.
v2 signals are missing. Version 2 added ad_user_data and ad_personalization alongside ad_storage and analytics_storage. If your CMP template only maps the original two, Google Ads treats you as non-compliant for EEA audiences and audience features quietly stop populating. Check all four in the debugger, not just the two you remember.
Verify it in ten minutes
Open GTM preview or the Tag Assistant and load the site in a clean browser profile. Do not accept the banner at first. Look at the consent tab on the very first message, the Consent Initialization event. Every one of the four signals should show denied there, in the default row, before any page view tag appears.
Then accept, and confirm an update row appears and the signals flip to granted. Reload and confirm the update appears again without clicking anything. Finally, in the network tab, filter for collect requests on a denied session and look for the gcs parameter. Its value encodes the consent state of each hit, and it is the fastest way to prove what Google actually received.
Consent
- Default consent call sits above the GTM snippet in the head
- All four signals are defaulted: analytics_storage, ad_storage, ad_user_data, ad_personalization
- wait_for_update is set to a short value, not left at zero
- CMP pushes an update on load for returning visitors
- Region-specific defaults match your legal requirements
- Mode (Basic or Advanced) is written down with legal sign-off
- gcs parameter verified on denied and granted hits
- Consent-denied share monitored weekly in GA4
Monitor it like a production system
Consent configs rot. A CMP vendor ships an update, someone adds a tag above your defaults, a redesign changes the banner. Track the share of sessions with consent denied as a weekly metric. A sudden swing from 35 percent to 5 percent means your update call is firing too eagerly. A swing the other way means your banner broke.
Pair that with a synthetic test that loads your top landing page, asserts the gcs value on the first request, and alerts on drift. It takes an hour to build and catches the failure that would otherwise cost you a quarter of attribution data before anyone notices.
Consent Mode is infrastructure. Treat it like infrastructure: pick the mode deliberately, order the tags correctly, and test it on a schedule.
Tags
LETSGROW Dev Team
Marketing Technology Experts
Ready to Apply This Insight?
Schedule a strategy call to map these ideas to your architecture, data, and operating model.
Schedule Strategy Call