Google Ads Consent Mode v2 and Enhanced Conversions: Where Signal Loss Still Happens (and How to Fix It in WordPress)

GA4 says 42 purchases. Google Ads says 51 conversions. Your CRM shows 37 closed orders.

In 2026, that reporting drift is often a configuration issue—not a demand problem.

Consent Mode v2, enhanced conversions, and Google’s documented conversion modeling now interact in ways that can quietly distort ROAS, Smart Bidding inputs, and remarketing pool size. If you run WordPress or WooCommerce, plugin stacking and checkout fragmentation make signal loss more likely than most teams realize.

Where signal loss still happens in 2026

1. Default vs. updated consent states

Google’s Consent Mode documentation defines four signals: ad_storage, analytics_storage, ad_user_data, and ad_personalization. Tags adjust behavior based on the default state and any subsequent update after a user interacts with your banner.

If your default is set to granted before the banner loads—or your update fires too late—Google tags may initialize in the wrong state. In WordPress, this often happens when:

A consent plugin loads after GTM or gtag.
The theme hardcodes a Google tag and GTM also deploys one.
Consent updates are tied to a click handler that doesn’t fire on mobile.

Result: inconsistent identifiers, reduced remarketing eligibility, and more reliance on modeled conversions.

2. Partial consent and ads signal reduction

Google Ads Help makes clear that consent affects ad measurement and personalization. If users allow analytics but deny ads-related signals (ad_storage or ad_user_data), you may still see sessions in GA4 while losing ad click identifiers and remarketing eligibility.

That doesn’t mean conversions disappear. It means Google may use documented conversion modeling when direct observation is limited. Modeled conversions are estimates derived from observable data patterns—not fabricated numbers—but as modeling share rises, Smart Bidding has less deterministic input to optimize against.

In practice: higher volatility in cost per lead and wider swings in reported ROAS.

3. Enhanced conversions that “work” but don’t match well

Enhanced conversions use hashed first-party data (such as email) to improve match rates in Google Ads, as described in Google Ads documentation. Common WooCommerce failures:

Email not normalized (extra spaces, uppercase issues) before hashing.
Phone numbers not formatted to E.164 standard.
Tags firing before user data is available in the DOM.
Checkout success handled via AJAX without pushing a clean event.

The conversion records, but match rate drops. Lower match quality means less durable attribution and weaker signals for bidding.

4. Duplicate tags and fragmented checkout flows

I routinely see all of the following on the same site:

Theme-level gtag.
WooCommerce Google plugin.
GTM container.
Manual hardcoded remarketing snippet.

Duplicate conversion actions inflate counts in Ads while GA4 deduplicates differently. Add a thank-you page that sometimes fails to load due to payment redirects, and now you have undercounting in one system and double-counting in another.

From Google’s perspective, when identifiers are unavailable or inconsistent, modeling fills the gap. From your perspective, forecasting becomes unstable.

What to do next

Validate consent state timing.
Use Tag Assistant to confirm the default consent state fires before any Google tag initializes, and that the update event triggers immediately after user choice. Check all four signals—not just analytics.
Audit enhanced conversion diagnostics.
In Google Ads, review conversion action diagnostics and enhanced conversion status columns. Look for low match rate warnings. If match quality is weak, inspect formatting and hashing logic.
Standardize tag deployment.
Choose one primary method: GTM or a single well-managed plugin. Remove duplicate global site tags and remarketing snippets. In WooCommerce, verify that purchase events fire once and only once.
Test checkout reliability.
Simulate real transactions across payment gateways. Confirm the conversion event fires on successful order creation—not just on a fragile thank-you page view. For higher control, evaluate server-side tagging as documented by Google Tag Manager, understanding it still respects consent signals.
Measure modeled vs. observed share before changing bids.
Google Ads documents when modeling is applied. If modeled conversions represent a growing share, expect more volatility. Stabilize implementation before tightening tCPA or tROAS targets.
Re-baseline after fixes.
Once consent timing, enhanced conversions, and duplication issues are corrected, allow bidding strategies to relearn. Document the before-and-after modeled share and match rate.

Consent Mode does not replace your legal obligations, and enhanced conversions do not bypass consent. But misconfigured consent and weak first-party data handling will absolutely distort bidding inputs.

If GA4, Google Ads, and your CRM don’t align, audit consent states and match rates before blaming creative, keywords, or seasonality. For most small-business accounts, this diagnostic is now quarterly maintenance—not a one-time setup task.

Sources

Know someone who would benefit from this update? Share this article with them.

This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.