Consent Mode v2 and Modeled Conversions

Consent Mode sends a user's consent state to Google tags so their behavior can adjust accordingly. When direct measurement is unavailable, eligible accounts may receive modeled conversions based on consented and observable data. Modeling does not replace a compliant consent experience, correct tag implementation, reliable conversion definitions, or reconciliation with business outcomes.

What does Consent Mode v2 do?

Consent Mode communicates consent choices through signals such as analytics and advertising storage, plus advertising user-data and personalization settings. The tag must receive the right default state before measurement runs and then update after the user chooses. Your consent platform and legal basis determine how that experience should work.

Google's Consent Mode implementation guide documents the current signals and tag behavior. Treat that technical guide as one input; it is not legal advice for every region or business.

What are modeled conversions?

Modeled conversions estimate advertising outcomes when an individual ad-to-conversion path cannot be observed. Google's consent modeling documentation says eligible modeled conversions are integrated into conversion reporting and downstream bidding. They are estimates at an aggregate level, not recovered user histories.

Observed and modeled are therefore different evidence states. Do not describe a modeled conversion as a known named customer or use it to reconstruct a person who declined consent.

Why might modeling not appear?

• Consent Mode is incomplete, ordered incorrectly, or not active on all relevant pages.
• The account, domain, or country slice does not meet Google's eligibility and confidence thresholds.
• Conversion actions are misconfigured, duplicated, or too unstable to provide a sound observed baseline.
• The implementation is too recent for diagnostics and model training to settle.
• Reports or date ranges hide the distinction the team expects to see.

Do not promise a specific uplift. Eligibility and reported impact depend on the live account and traffic. Start with conversion tracking and the consent diagnostics available to that property.

How do you validate the setup?

Test default and updated consent states in each supported region and choice. Confirm tags behave as intended before and after the choice, the consent banner records it correctly, and the conversion event fires once where allowed. Then compare Ads, GA4, CRM, and consent-platform trends without expecting exact equality.

Use the distinction between GA4 key events and Ads conversions when reconciling reports. A modeled Ads conversion and an Analytics key event are not interchangeable labels.

What should automation be permitted to change?

An AI manager can monitor diagnostics, identify missing signals, and stage a technical fix. It should not silently change a consent default, legal message, region rule, primary conversion, or data-sharing connection. Approval must name the property, tag, regions, signals, and intended behavior, followed by a fresh end-to-end test.

For lead businesses, connect the consent review with enhanced conversions for leads.