Consent Mode Advanced vs Basic: Which to Implement
One recovers far more data than the other, and the difference is not obvious from the docs. Here is how to choose.
Consent Mode has two implementation modes and the documentation does not make the difference obvious.
One of them recovers a substantial share of the conversions you lose to consent rejection. The other recovers none. They take about the same effort to implement.
Worth ten minutes to understand which one you have.
The difference in one paragraph
In basic mode, Google tags do not load at all until the user consents. No consent, no tag, no data, nothing for Google to model with.
In advanced mode, Google tags load immediately with consent defaulted to denied. They send cookieless pings that contain no identifiers but do tell Google that something happened. When users later consent, full data flows. Google uses the relationship between the two groups to model the conversions it could not observe.
That modelling is the entire value, and basic mode does not get it.
What the modelling actually recovers
Google observes the behaviour of consenting users and the anonymous signals from non consenting ones, then estimates the conversions in the second group.
How much it recovers depends on your consent rate and your volume. Sites with reasonable volume typically see a meaningful share of otherwise invisible conversions restored, and the effect is largest where consent rates are lowest.
Those modelled conversions appear in your Google Ads reporting and are used by Smart Bidding, which is the part that matters commercially.
The threshold nobody mentions
Modelling requires volume. Google needs enough data to build a reliable model, and there are minimum thresholds for ad clicks and conversions over a period.
Below those thresholds, advanced mode collects the cookieless pings and no modelling happens, so you see no recovery.
This is worth knowing before you promise anyone a result. A small site implementing advanced mode correctly may see nothing for months until volume builds.
Which one do you have?
Easy to check.
Open your site in a fresh browser profile with developer tools on the network tab.
Do not interact with the consent banner.
Filter network requests for google-analytics or googletagmanager collect requests.
If you see requests going out with a parameter indicating denied consent, you are in advanced mode. If you see nothing at all until you accept, you are in basic mode.
Most implementations I check are in basic mode, usually because the consent tool blocks scripts by default and nobody changed it.
Moving from basic to advanced
Three changes.
Stop your consent tool from blocking the Google tags outright. They must be allowed to load.
Set consent defaults to denied through the consent API, using the Consent Initialization trigger in GTM.
Update consent when the user chooses, rather than loading the tags at that point.
The conceptual shift is that the tags always load and their behaviour is governed by consent state, instead of the tags being withheld.
Your consent platform needs to support this properly, which is the main reason to check before choosing one: choosing a consent management platform.
The objection, addressed honestly
People reasonably ask whether loading a tag before consent is compliant.
The position, as Google presents it and as the certified consent platforms implement it, is that a cookieless ping containing no identifiers and setting no storage is not the kind of processing that requires consent.
That reasoning is broadly accepted and it is not universally settled, and interpretations differ by jurisdiction. If your organisation has a strict position on this, that is a legitimate reason to stay in basic mode, and it should be a documented decision rather than an accident of configuration.
I am not a lawyer and this is not legal advice. What I can tell you is the measurement consequence, which is that basic mode costs you visibility into a real share of your conversions.
The parameters to get right
Consent Mode v2 added two parameters to the original two, and both are required for Google advertising features.
analytics_storage. Analytics cookies and measurement.
ad_storage. Advertising cookies.
ad_user_data. Whether user data may be sent to Google for advertising purposes.
ad_personalization. Whether data may be used for personalised advertising.
Missing the last two is a common problem after the v2 update, and the symptom is remarketing audiences that stop filling. Check all four are being set.
Server side does not exempt you
A persistent misunderstanding worth correcting. Moving to server side tracking does not remove the consent requirement.
Consent applies to processing personal data, not to which server sends the request. Pass consent state through to your server container and gate destination tags on it there.
What server side does give you is one place to enforce it: feeding every ad platform from one server container.
The summary
Advanced mode, correctly implemented, with all four parameters, defaults set through the Consent Initialization trigger, and a certified consent platform that supports it natively.
Then verify it yourself in the network tab rather than trusting the vendor’s checklist.
Need this built properly?
Two modes, similar effort, very different amounts of data at the end of it. I set up and repair tracking for ecommerce stores and lead generation businesses, so the numbers in your ad accounts match the money in your bank account.
Have a look at what I do, or book a call and we can go through your setup together.
