How Consent Mode Affects Your GA4 Conversion Modeling

What Consent Mode Actually Sends to GA4

With Consent Mode v2, when a user declines analytics_storage, GA4 receives a cookieless ping, a stripped event that carries no user identifier, no session data, and no event parameters beyond what is needed to infer aggregate behavior patterns.

Google uses these pings alongside consented user data to train a machine learning model that estimates conversion rates for non consenting users. The output of this model fills in the gaps in your reported conversions.

This means your GA4 conversion count is a blend of directly observed conversions and statistically inferred ones. The ratio depends on your consent acceptance rate.

The challenge is that GA4 does not expose which conversions are measured and which are modeled in the standard reporting interface.

The Accuracy of Modeled Conversions

Google's conversion modeling is generally reliable in aggregate, but it has known limitations.

The model performs best when you have a large volume of consenting users to train on. Lower traffic or lower consent rates can make modeled conversions noisier.

The model also assumes that consenting and non consenting users behave similarly, which may not hold if consent acceptance correlates with demographics, device type, or geography.

B2B sites often have lower consent rates among corporate users browsing with privacy focused browsers, which can cause the model to undercount certain conversion segments.

Additionally, conversion modeling only applies to Google's own reporting and attribution layers. It does not flow into BigQuery raw exports, which means your BigQuery data will usually show fewer modeled conversions than your GA4 reports.

Auditing the Impact on Your Property

To understand the modeling gap in your property, compare total conversions in GA4 against your CRM or backend order system for the same period.

If GA4 reports more conversions than your CRM records, and you have Consent Mode active, the difference is likely modeled conversions that were never actual orders.

You should also check your consent acceptance rate in the CMP dashboard and compare it against your analytics coverage rate (the ratio of GA4 sessions to actual site visits from server logs).

Properties with low consent rates that have not validated their consent mode implementation often have modeling artefacts that inflate reported performance, leading to over investment in channels that look better than they actually are.