# Basic vs. advanced consent mode: which should you use?

> Basic vs. advanced Google Consent Mode compared: tag loading before consent, cookieless pings, conversion modeling, privacy risk and which one to pick.

Source: https://www.cookiesh.eu/blog/basic-vs-advanced-consent-mode  
Published: 2026-07-09

## Key takeaways

- In basic consent mode, Google tags are blocked until the visitor consents, so Google receives nothing from visitors who decline.
- In advanced consent mode, Google tags load with denied defaults and send cookieless pings that Google uses to model lost conversions.
- Google presents both modes as valid Consent Mode implementations; they differ in measurement coverage and privacy exposure.
- Advanced mode sends requests to Google before and without consent, so have your privacy counsel review it for your markets.

Basic consent mode blocks Google tags until a visitor consents, so Google receives nothing from people who decline. Advanced consent mode loads Google tags immediately with consent denied, and they send cookieless pings that Google uses to model conversions and behavior you would otherwise lose. Basic is the lower-risk choice; advanced recovers more measurement but needs legal sign-off.

## What is the difference between basic and advanced consent mode?

The difference is when Google tags load. In basic mode your consent banner blocks them until consent; in advanced mode they load right away and adjust their behavior to the consent state.

Both are implementations of [Google Consent Mode v2](/blog/google-consent-mode-v2-guide) and use the same four signals: `ad_storage`, `analytics_storage`, `ad_user_data` and `ad_personalization`. What changes is what happens for visitors who decline or never interact with the banner.

| | Basic consent mode | Advanced consent mode |
|---|---|---|
| Google tags before consent | Not loaded | Loaded with denied defaults |
| Data sent to Google when consent is denied | None | Cookieless pings |
| Cookies when consent is denied | None | None for the denied storage types |
| Consent signals | Sent only once the visitor consents | Default on page load, update after the choice |
| Conversion modeling in Google Ads | General model, per Google | Advertiser-specific model, per Google |
| GA4 behavioral modeling | Not available | Available once eligibility thresholds are met |
| How it is implemented | CMP blocks Google tags until consent | CMP sets defaults and updates; tags load normally |
| Privacy exposure | Lower | Higher; needs legal review |

## How does basic consent mode work?

In basic mode, your consent management platform (CMP) holds Google tags back until the visitor grants consent. Before that, the browser makes no requests to Google's measurement or advertising endpoints.

Once the visitor accepts, the tags load and receive the granted consent state. If the visitor rejects, nothing loads. According to Google's documentation, basic mode still supports conversion modeling, but with a general model rather than one built from your own site's signals.

Basic mode is easy to reason about because Google tags follow the same rule as every other third-party script you [block until consent](/blog/block-scripts-until-consent). That consistency makes it simpler to explain to a regulator, an auditor or a client's legal team.

## How does advanced consent mode work?

In advanced mode, Google tags load on every page view with your default consent state, usually all denied in the EEA and UK. While consent is denied, the tags don't read or write advertising or analytics cookies, but they do send cookieless pings.

Google describes these pings as carrying functional information, such as a timestamp, user agent and referrer, plus aggregate or non-identifying information, such as the consent state and whether the page URL contains ad-click information. Google uses them to estimate conversions and behavior from visitors who declined, filling gaps in Google Ads and GA4 reports.

When the visitor later accepts, an update call switches the signals to granted and the tags behave normally from that point on.

Google's documentation also ties GA4 behavioral modeling to this setup, with minimum traffic thresholds before modeled data appears. Small sites may implement advanced mode and still see little modeled data.

## What are the privacy risks of advanced consent mode?

Advanced mode sends requests to Google before and without consent. Even without cookies, each request reveals the visitor's IP address and browser details to a third party.

Article 5(3) of the ePrivacy Directive isn't limited to cookies; it covers storing or accessing any information on a user's device. European regulators have signaled a broad reading of that rule that can reach tracking pixels and similar techniques. Under the GDPR, an IP address can also be personal data, so the transfer needs a lawful basis.

Whether cookieless pings require consent is not settled, and views differ by country. Treat it as a question for your privacy counsel, and check current guidance from the regulators in your main markets before you switch.

If you do choose advanced mode, be transparent about it. Describe the pre-consent pings in your cookie policy rather than implying that nothing reaches Google until the visitor clicks accept.

## How do I choose the right mode?

Start from your risk tolerance and how much you depend on Google Ads data, then work through these questions:

1. **Ad spend:** Does a meaningful share of revenue depend on Google Ads bidding and conversion data? If not, basic mode costs you little.
2. **Legal view:** What does your privacy counsel say about requests to Google before consent in your main markets?
3. **Promises:** Do your privacy policy, client contracts or internal standards say no data leaves the browser before consent?
4. **Consistency:** Do you already block every other vendor until consent? Basic mode keeps Google in line with them.
5. **Volume:** Do you have enough traffic for modeling to produce results? Google applies thresholds before modeled data appears.
6. **Transparency:** Can you explain advanced mode clearly to visitors in your cookie policy?

A cautious path is to start with basic mode, measure what you lose in reporting, and move to advanced only if the business case is clear and legal has signed off. Whichever you pick, document the decision and the reasoning.

## Does consent mode replace a cookie banner?

No. Neither mode collects consent; both depend on a banner that asks clearly, stores the choice and gates non-Google tags. Consent mode is only the messenger between that banner and Google's tags.

If you want measurement that depends less on consent, look at [cookieless analytics](/blog/cookieless-analytics) options. They come with their own trade-offs and legal questions, so don't treat them as an automatic exemption.

## Bottom line

Choose basic mode if you want the simplest, lowest-risk setup and can accept less modeled data. Choose advanced mode if Google Ads performance depends on modeled conversions and your legal team is comfortable with pre-consent pings. Tools like Cookiesh include Google Consent Mode v2 support on every plan and can block tagged scripts until consent.

*This article is general information, not legal advice. For decisions about your specific situation, consult a qualified privacy professional.*

## FAQ

### Does advanced consent mode set cookies before consent?

No. While ad_storage and analytics_storage are denied, Google tags don't read or write advertising or analytics cookies. They still send cookieless network requests, which, like any web request, expose details such as the visitor's IP address and browser.

### Can I switch from basic to advanced consent mode later?

Yes. The change is mainly in how tags load: instead of holding Google tags back until consent, you let them load with denied defaults. Modeling needs enough data before it produces results, so expect a ramp-up period after switching.

### Is basic consent mode enough for Google Ads in the EEA?

Google's documentation treats both basic and advanced as ways to implement Consent Mode. Basic mode gives you less modeled data for visitors who decline, but consented visitors are still measured with full consent signals.

## Sources

- [Google: Consent mode overview](https://developers.google.com/tag-platform/security/guides/consent)
- [Google EU user consent policy](https://www.google.com/about/company/user-consent-policy/)
- [Directive 2002/58/EC (ePrivacy Directive), EUR-Lex](https://eur-lex.europa.eu/eli/dir/2002/58/oj)