The assumption that consent is a single setting, configured once and applied everywhere, has always been fragile. The split between GA4 and Google Ads consent controls makes that fragility visible. Teams that set up consent two years ago and have not revisited it are likely running platforms with inconsistent parameters — and the consequences show up as reporting discrepancies, unexplained audience gaps, and measurement decisions based on data that does not mean what the team thinks it means.

This is not primarily a compliance issue. It is a governance and measurement reliability issue. Here is how to audit it.

What split consent controls means in plain English

GA4 and Google Ads each now have distinct consent configuration points for key parameters including ad_user_data, ad_personalization, analytics_storage, and ad_storage. These parameters control whether data is used for ads measurement, audience building, and personalization within each platform.

Because the platforms are linked but separate, a consent framework built for one does not automatically apply to the other in the same way. A conservative GA4 setup can co-exist with a less restricted Ads setup, or vice versa. Neither platform flags the other's configuration. The conflict is invisible until someone specifically looks for it.

Why this creates governance risk

  • Conversion data imported from GA4 into Google Ads may carry different consent constraints than independently fired Ads tags
  • Remarketing audiences built in GA4 with conservative settings may not populate as expected in Google Ads campaigns
  • Legal teams approving a consent framework in one tool may not realize the other platform has separate settings
  • Platform updates can reset or introduce new consent parameters that were not part of the original configuration
  • Agency handoffs often result in one platform's settings being updated without the other being reviewed

The 8-point audit checklist

  1. Document all active consent parameters in GA4: analytics_storage, ad_storage, ad_user_data, ad_personalization — and their default states by region
  2. Document all active consent parameters in Google Ads: confirm which conversion actions use which consent mode version and whether the parameters match GA4
  3. Confirm Google Signals configuration in GA4 and whether it is enabled or disabled — and whether that decision was intentional or a default
  4. Check whether GA4-imported conversions in Google Ads carry the same consent parameters as the GA4 source data
  5. Audit remarketing audiences: are any audiences built from GA4 data behaving unexpectedly in Google Ads campaigns in terms of population size or match rate?
  6. Confirm the CMP (Consent Management Platform) is passing all required consent signals to both GA4 and Google Ads tags — not just to one
  7. Verify that Consent Mode v2 parameters (ad_user_data and ad_personalization) are correctly implemented in both platforms for EEA-served traffic
  8. Record when the last consent review was done and establish a named owner and quarterly review schedule going forward

Where teams usually get confused

AssumptionRealityRisk
Consent Mode setup in GTM covers both GA4 and AdsGTM routes consent to specific tags — each tag needs its own consent trigger configurationOne platform uncovered while team believes both are configured
GA4 conversion import means GA4 consent applies in AdsGoogle Ads applies its own consent framework to imported conversionsInconsistent measurement between platforms for same events
Existing consent setup is still currentGoogle has added new parameters (v2) that legacy setups do not includeAd personalization and audience features restricted without team awareness
One CMP handles consent for everythingCMP passes consent signals — but only to the tags it is configured to pass them toGaps in consent signal for any tag not included in CMP configuration

How this affects lead gen advertisers

A B2B company running Google Ads for demo requests has GA4 configured conservatively, with ad_personalization denied by default for EEA users. The Google Ads account, configured by a different team, does not have the same restriction applied. The result: GA4 reports one view of audience eligibility while Google Ads attempts to use personalization features that the consent framework was intended to restrict. Reporting looks consistent. Audience behavior does not match expectations.

From a lead quality perspective, the more immediate problem is that Smart Bidding optimizes from conversion data that may carry different consent contexts depending on whether the trigger fired via the GA4 import or the standalone Ads tag, creating a subtle but real inconsistency in what the algorithm learns from.

How this affects eCommerce advertisers

A retailer relying heavily on remarketing and modeled conversions is particularly exposed. If GA4 remarketing audience lists are being built with more conservative consent than the Google Ads campaign expects, list sizes will be smaller than planned. Dynamic remarketing campaigns will appear to underperform against forecast reach without any obvious explanation in campaign-level reporting.

The fix is not to loosen consent — it is to ensure that what the consent framework says is applied consistently and that campaigns are planned around the audience sizes the actual consent coverage produces.

Suggested ownership model

TeamOwnsReviews
Legal / ComplianceConsent policy parameters and regional defaultsAnnually or when regulations change
Analytics / DataGA4 consent implementation and CMP integrationQuarterly
Paid Media / AgencyGoogle Ads consent parameters, Consent Mode v2 in Ads tagsQuarterly
DevelopmentCMP code implementation and consent signal routingAt each CMP or SDK update