Consent Mode Basic
No transmission to Google until the user grants consent.
Implementation comparison
See what actually happens before and after consent, how each implementation affects GA4 and Google Ads data, and which one fits your privacy policy.
No transmission to Google while consent has not been granted.
Cookieless measurements can support more detailed modeling.
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 transmission to Google until the user grants consent.
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 consent is granted through the CMP | Tags load immediately; consent defaults to “denied” |
| Cookieless pings on refusal | None - without granted consent, tags remain blocked and nothing is sent to Google | Yes - cookieless measurements can support modeling in GA4 and Google 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 reliably block tags and load them only after consent is granted | 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 | Tags stay loaded; with denied consent they send cookieless measurements as configured |
| Piwik PRO / other tools | Similar logic: tags wait for consent | Piwik has its own Consent Manager - separate config alongside Google |
| Ease of implementation | Requires testing tag blocking and correct activation after consent | Requires testing default consent, tag order and signals in Tag Assistant |
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.
Neither mode fits every site. The choice depends on Google Ads spend, legal requirements and how many visitors actually click the 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 Audit the setup and consider Advanced
First verify consent, tags and conversion diagnostics. Missing pings can be one cause, but moving to Advanced should follow diagnosis and a privacy assessment.
Choose Basic when zero communication with Google before consent is the priority and you accept less detailed modeling. It is a sensible option 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.
Implementation support
I help you choose Basic or Advanced, connect your CMP to GTM/GA4, configure default consent states, and verify modeling in reports.