Consent Mode Basic
No pings or cookies until the user makes a choice.
Differences between Basic and Advanced in Google Consent Mode v2: tag loading, cookieless pings, conversion modeling, GDPR, and recommendations for GA4 and Google Ads.
Google Consent Mode communicates consent state to Google tags. In Basic mode tags wait for the user's decision, while Advanced can send cookieless pings when consent is denied. The choice affects the availability and detail of modeling in GA4 and Google Ads.
No pings or cookies until the user makes a choice.
Cookieless pings can support more detailed modeling.
For users in the EEA, Google requires consent choices to be collected and shared for applicable measurement, ad-personalization and remarketing features. Below are four key consent parameters used by Google tags; Consent Mode v2 added ad_user_data and ad_personalization.
| Signal | Description |
|---|---|
ad_storage |
Consent for advertising cookies (remarketing, Ads conversions). |
ad_user_data |
Consent to send user data to Google for advertising (v2 requirement). |
ad_personalization |
Consent for ad personalization (remarketing, audiences). |
analytics_storage |
Consent for GA4 analytics cookies (full tracking vs modeled data). |
Key technical and business differences - from when data is sent to conversion modeling and GTM configuration complexity.
| Feature | Basic | Advanced |
|---|---|---|
| When Google tags load | Tags blocked until CMP updates consent | Tags load immediately; consent defaults to “denied” |
| Cookieless pings on refusal | None - nothing sent before banner interaction | Yes - cookieless pings enable modeling in GA4 and Ads |
| Conversion modeling (Google Ads) | General model without advertiser-specific pings before consent | More detailed model that can also use advertiser-specific pings |
| Behavioral modeling (GA4) | No pings from denied users limits model input | Possible after meeting Google Analytics eligibility requirements and thresholds |
| CMP + GTM requirements | CMP must send update after choice; simpler blocking logic | CMP + default consent (gtag or GTM Consent Initialization) |
| DPO / legal team expectations | Often preferred for “zero tracking before consent” | Requires documenting ping behavior and assessing compliance for the organization |
| No banner decision or refusal | No advertiser pings; Google Ads may use a less detailed general model | Cookieless pings can support modeling; they do not bypass script blocking |
| Piwik PRO / other tools | Similar logic: tags wait for consent | Piwik has its own Consent Manager - separate config alongside Google |
| Ease of implementation | Simpler - block tags until consent | Requires testing: Tag Assistant, DebugView, GTM Consent tab |
Verdict: For companies with active Google Ads, Advanced usually provides more model input - provided configuration, Google eligibility, and cookieless-ping documentation are correct. Basic remains sensible under strict legal requirements or minimal paid marketing.
Pros, cons and typical use cases for each mode. After choosing a mode, validate your setup with the Consent Mode v2 checklist.
Best for: Organizations with strict privacy policies, low paid media spend, or when legal requires fully blocking tags before consent.
Best for: E-commerce, lead gen and companies with Google Ads budgets in the EEA/UK - when report quality and modeling on refusal are priorities.
There is no universally “better” mode - the decision depends on ad spend, legal requirements, and how many users actually interact with your cookie banner.
Recommendation Consent Mode Advanced
Cookieless pings can improve conversion-model inputs at high refusal rates; the outcome depends on meeting Google's requirements.
Recommendation Consent Mode Basic
With low Ads spend, modeling benefits are small, and simpler tag blocking eases privacy compliance.
Recommendation Consent Mode Basic (or Piwik PRO instead of GA4)
Basic is easier to defend under a zero-transmission-before-consent policy. Confirm the final choice with your DPO or legal counsel.
Recommendation Advanced for Google + separate Piwik path
CMP must update both ecosystems. Advanced for GA4/Ads; Piwik PRO has its own consent API - wire in GTM or natively in CMP.
Recommendation Migrate Basic → Advanced
Missing pings can be one cause - run the audit checklist, set default denied, and verify tags and Consent Mode diagnostics.
Choose Basic when zero communication with Google before consent is the priority and you accept weaker modeling. Enough for many informational sites.
Choose Advanced when GA4 reports and Google Ads conversions matter at high refusal rates - it is a common choice in ecommerce and performance marketing.
I help you choose Basic or Advanced, connect your CMP to GTM/GA4, configure default consent states, and verify modeling in reports.