The choice between Basic and Advanced Consent Mode determines what happens when a user declines consent. It directly affects conversion modeling quality, the volume of data in GA4 BigQuery exports, and the gap between GA4 interface numbers and warehouse numbers.
Basic Mode: Nothing Fires Without Consent
Basic mode blocks all Google tags until the user grants consent. When someone lands on your site and dismisses or declines the cookie banner, nothing happens from a measurement perspective:
- No pings sent to Google
- No cookies set
- No cookieless signals collected
- The user is completely invisible to your analytics
When consent is granted (the user clicks Accept), tags fire normally with full measurement capabilities.
The implication for conversion modeling: Google can still model conversions for your account, but it uses a general industry model rather than one trained on your specific traffic patterns. It looks at broad behavioral patterns across similar advertisers and estimates what your unconsented traffic likely did. This is better than nothing, but it’s a coarse approximation.
Advanced Mode: Cookieless Pings Before Consent
Advanced mode loads Google tags immediately, regardless of consent state. When consent is denied, tags send cookieless, anonymous pings — no cookies are set, no identifiers are attached, but the ping itself transmits:
- Page URL
- Timestamp
- Basic browser metadata
- Consent state parameters
These pings carry no user identity. They can’t be used for remarketing, attribution, or user-level analysis. But they provide Google with aggregate traffic pattern data specific to your site.
When consent is later granted (user returns and accepts, or accepts on a subsequent page), full measurement activates: cookies are set, identifiers attach to events, and the user becomes trackable.
The modeling advantage: those cookieless pings let Google build an advertiser-specific conversion model. Instead of estimating from industry averages, Google can observe that X% of anonymous sessions on your site tend to convert based on patterns it sees from consented users. Advertisers typically see 15 to 25% more reported conversions with Advanced mode’s site-specific modeling compared to Basic mode’s industry modeling.
Traffic Thresholds: Where Advanced Mode Falls Short
The modeling advantage of Advanced mode has minimum traffic requirements that many sites don’t meet:
| Platform | Minimum requirement |
|---|---|
| Google Ads conversion modeling | 700+ ad clicks over 7 days per country and domain |
| GA4 behavioral modeling | 1,000+ daily events with analytics_storage denied for 7 consecutive days AND 1,000+ daily users with analytics_storage granted for 7 of the previous 28 days |
At a 50% consent rate, you need roughly 2,000 daily visitors to qualify for GA4 behavioral modeling. The Google Ads threshold is even harder to reach — 700 ad clicks per week per country means you need substantial paid traffic concentrated in specific markets.
If your site doesn’t hit these thresholds, the modeling advantage of Advanced mode largely disappears. You still get the benefit of cookieless pings for aggregate trend data (Google can see your traffic volumes even from non-consenting users), but the conversion modeling falls back to industry-level estimates similar to Basic mode.
The BigQuery Data Gap
This choice has a direct, measurable impact on the gap between your GA4 interface and BigQuery numbers.
With Advanced mode, GA4’s interface includes modeled data for non-consenting users. Your BigQuery export contains only events from consenting users. A European site with 40% consent rejection will see the GA4 interface report roughly 40% more sessions and users than BigQuery can account for. This modeled data never reaches BigQuery — there’s no way to reconcile the gap from the warehouse side.
With Basic mode, the gap is smaller because GA4’s modeling is less confident (no site-specific signals to train on), so the modeled additions are more conservative. But you also have less total data flowing into BigQuery because there are no cookieless pings at all.
Privacy Trade-offs
Advanced mode is more aggressive from a privacy perspective. It transmits data to Google’s servers before the user has consented. The data is anonymous (no cookies, no identifiers), but it’s still a data transmission. Some privacy-conscious organizations and DPAs (Data Protection Authorities) may consider this incompatible with strict interpretations of GDPR, particularly the principle that consent must be obtained before any data processing begins.
Basic mode is the safer choice from a strict compliance standpoint. Nothing fires until consent is explicitly granted. The trade-off is less data for modeling.
Most implementations in practice use Advanced mode. Google’s own documentation recommends it, and the major CMPs default to it when Consent Mode is enabled. But the choice should be documented and reviewed by your legal or privacy team, not made purely on technical grounds.
Choosing Between Them
The decision framework is straightforward:
Choose Advanced mode when:
- Your site meets the modeling traffic thresholds (or is close to them)
- Your legal/privacy team is comfortable with cookieless pings before consent
- Conversion modeling accuracy is important for your advertising spend decisions
Choose Basic mode when:
- You operate under strict privacy requirements or DPA guidance that prohibits pre-consent data transmission
- Your site traffic is low enough that modeling thresholds won’t be met anyway
- You don’t run Google Ads and conversion modeling isn’t relevant
For sites with moderate traffic, some advertising, and no strong legal opinion either way, Advanced mode is the common default. The additional data signals benefit conversion modeling, and the privacy risk of cookieless pre-consent pings is widely accepted in industry practice.
December 2025: An Additional Layer
In December 2025, Google added data transmission controls to Google Tag settings that Simo Ahava described as “basically a Basic Consent Mode type control on top of an Advanced Consent Mode setup.” This means Google is layering additional server-side consent enforcement over what client-side implementations send. Even if your implementation uses Advanced mode, Google may apply additional server-side restrictions.
The direction is clear: consent controls will get stricter, not looser. An implementation that works today needs ongoing maintenance as Google tightens enforcement.