Consent Mode Basic vs Advanced: What Actually Changes
The technical difference between basic and advanced consent mode, what each one sends before consent, and how to decide which one belongs in your setup.
Fabian Weiss Teams switch on advanced consent mode because it sounds better, without understanding what it sends before consent
Understand the four consent signals, what each mode does before and after the decision, and decide deliberately
The choice is not technical, it is a policy decision with a technical implementation
Consent Mode v2 is often reduced to a toggle in a consent management platform. That framing hides the actual question. The two modes differ in one thing: what happens before the visitor has decided anything.
Everything else, the four signals, the update mechanism, the testing, applies to both.
The four signals
Consent Mode v2 separates at least four states, and they are independent of each other:
| Signal | Governs |
|---|---|
analytics_storage | Storage used for analytics, for example the GA4 client ID |
ad_storage | Storage used for advertising, for example conversion cookies |
ad_user_data | Whether user data may be sent to Google for advertising purposes |
ad_personalization | Whether the data may be used for personalised advertising |
The two ad_ signals introduced with v2 are the ones most setups get wrong, because a banner that only offers “analytics” and “marketing” has to map two categories onto four signals. That mapping needs to be a written decision, not an accident of the CMP defaults.
Basic mode
In basic mode, the Google tags do not load until the relevant consent has been granted.
Before the decision:
- no measurement events are sent
- no Google tag executes
- nothing is stored on the device by these tags
After acceptance:
- the tags load and measurement starts from that point
- there is no retroactive replay of what happened before the decision
- the current page view is measured, but the entry page view before the banner was answered is gone
Consequence: basic mode produces a clean, easily explainable data set with a visible hole. The hole is the size of your rejection rate plus everyone who left before deciding.
Advanced mode
In advanced mode, the Google tags load immediately, but they respect the denied state by sending cookieless signals instead of storing identifiers.
Before the decision:
- the tags are present and can send a signal without device storage
- the signal carries no identifier that persists across the visit
On rejection:
- the tags keep sending cookieless signals rather than nothing
- Google can use those signals as an input to conversion modelling
Consequence: advanced mode produces more complete reporting, at the cost of transmitting something in a state where basic mode transmits nothing at all. That is exactly why the decision is not purely technical.
What neither mode does
Both modes are frequently oversold. To be precise:
- Neither mode replaces a consent banner. Accessing or storing information on a device still requires consent.
- Neither mode makes a setup compliant on its own. Compliance depends on the banner, the privacy policy, the legal bases and the processing agreements.
- Neither mode recovers the data of users who rejected. Advanced mode enables modelling; modelling is an estimate, not the raw event.
- Modelling is not guaranteed. It has volume thresholds. A small site may see no modelled conversions at all, which makes advanced mode a lot less attractive than the marketing suggests.
How to decide
Work through these questions in order. The first “no” usually settles it.
1. What does your legal assessment say? This is the gate. If your counsel or your data protection officer has taken a position on cookieless pings before consent, that position decides the question. Everything below only matters if advanced mode is on the table at all.
2. Do you have the volume for modelling to do anything? Modelled conversions need enough traffic and enough conversions to be produced at all. Below that threshold, advanced mode adds transmission without adding reporting.
3. What is your actual rejection rate? If most visitors accept, the gap that advanced mode addresses is small. Measure it before you optimise it.
4. Does the ad spend justify it? The commercial argument for advanced mode is better bidding signals. With little or no ad spend, that argument does not exist.
5. Is the rest of your measurement correct? This is the one people skip. Advanced mode on top of a broken purchase event produces more complete transmission of the wrong number. Fix the web tracking foundation first.
Implementation checklist
Whichever mode you land on, these have to hold:
- The default state is set before any Google tag executes, not after.
- The update state is sent after the decision, and you have verified it in the network request rather than in the banner UI.
- All four signals are mapped from your banner categories, with the mapping written down.
- Rejection is tested and produces the expected behaviour.
- Partial consent is tested. Analytics-only is the case most setups fail.
- Withdrawal is tested. A visitor who revokes mid-session must stop being measured.
- Later acceptance is tested. A visitor who accepts on page three must be measured from page three.
- No first-party customer data is sent for enhanced conversions without the required consent.
- The behaviour is documented, including known limits, so the next person does not have to reverse-engineer it.
The Shopify and WordPress case
If you run a WordPress main site and a Shopify shop, you almost certainly have two consent systems. Shopify has its own Customer Privacy API; WordPress typically has Borlabs, Cookiebot, Usercentrics or similar.
Two systems mean two decisions to reconcile. Either you unify them, or you document why a visitor who accepted on one surface may be treated differently on the other. Leaving it undocumented is how audits get uncomfortable.
The Shopify tracking checklist covers the shop side of this in detail.
Where this fits
Consent handling is one block of a measurement setup, not the whole of it. It belongs alongside a correct event model, working conversion actions and reliable transaction IDs. The GA4 and Consent Mode v2 service covers the consent layer in depth; the web tracking service covers the full measurement foundation around it.
FW Delta implements the technical consent handling. The legal assessment of the texts and legal bases stays with the client and their advisers. This guide is a technical explanation, not legal advice.