Diverse team collaborates on a business project with charts and laptops in a modern office setting.

Consent Mode v2 + Enhanced Conversions: Reduce Modeled Drift

BySplinternet Marketing

Seeing Google Ads conversions drift from GA4 and your CRM? In 2026, that’s usually a consent and signal configuration issue—not a demand problem.

Google formally documents that Consent Mode adjusts how tags behave based on user consent, and when identifiers aren’t available, Google Ads can use conversion modeling to estimate missing conversions. That’s expected platform behavior. But a large share of reporting instability I see on WordPress and WooCommerce builds is avoidable signal loss: late consent updates, duplicate tags, or incomplete enhanced conversions.

Before you question traffic quality or cut budget, audit your consent stack.

What Consent Mode v2 and Conversion Modeling Actually Change

According to Google Tag Platform documentation, Consent Mode uses four consent signals:

  • ad_storage
  • analytics_storage
  • ad_user_data
  • ad_personalization

The newer ad_user_data and ad_personalization signals matter for advertising features and downstream use of data in Google Ads. Tags must receive a default consent state before firing, and then an updated state after user interaction. If consent is denied, Google tags can send limited, cookieless pings instead of full measurement data (Google Tag Platform: Consent Mode Overview).

When identifiers are unavailable, Google Ads may use modeled conversions to fill measurement gaps (Google Ads Help: About Conversion Modeling). Modeled conversions are estimates—not direct observations. They are designed to reduce undercounting when consent or browser restrictions limit observable data.

This is where many teams misread performance. A jump in reported conversions after fixing consent or enhanced conversions often reflects measurement recovery, not sudden demand growth.

Enhanced conversions sit on top of this stack. Google documents that enhanced conversions use hashed first-party data (such as email) to improve match rates for conversions that would otherwise be difficult to attribute (Google Ads Help: Enhanced Conversions). Formatting and hashing requirements are strict—values must be normalized and hashed correctly, or match rates silently degrade (Google Ads Developer Docs: Enhanced Conversions Web Setup).

Done correctly, enhanced conversions reduce reliance on modeling. Done incorrectly, they give you a false sense of coverage.

Where WordPress and WooCommerce Signal Loss Happens

Across U.S. small-business builds, these are the recurring failure points:

  • No true default consent state in GTM. Tags fire before consent is set. Google’s documentation is explicit: default consent must be established before any tag reads or writes storage.
  • Late consent updates. The consent banner updates state after conversion events have already fired on checkout or lead submit.
  • Duplicate tagging. Hardcoded gtag.js in the theme plus Google Tag Manager plus a WooCommerce plugin. Conflicting behavior = inconsistent signals.
  • Checkout events firing pre-consent. Especially in AJAX-heavy WooCommerce flows.
  • Improperly formatted enhanced conversion data. Email not normalized (lowercase, trimmed) before hashing, or sent in the wrong field.
  • Google Ads and GA4 not properly linked. Linking is required for aligned attribution and data sharing (Google Analytics Help: Link Google Ads and Analytics).

Each of these increases modeled reliance and destabilizes Smart Bidding. If your CPA or ROAS swings after a site update, consent sequencing is often the root cause.

Modeled conversions themselves are not errors. Misconfiguration that forces excessive modeling is.

What to do next

  1. Confirm GTM consent defaults. In Tag Manager, set default consent for all four signals before any tag fires. Then verify updated consent triggers after user action.
  2. Remove duplicate tags. Audit theme files, header injections, and WooCommerce plugins. One deployment path per tag.
  3. Validate enhanced conversions. Check normalization and hashing against Google’s documented requirements. Use diagnostics in Google Ads to confirm receipt and match quality.
  4. Inspect tag sequencing on checkout. Ensure conversion events fire after consent state is resolved.
  5. Verify Google Ads–GA4 linking. Confirm linking in both platforms to align attribution inputs.
  6. Watch Smart Bidding inputs for 2–4 weeks. Expect short-term volatility after fixes. Treat improvements as measurement normalization, not instant efficiency gains.

Consent Mode does not override your legal obligations, and server-side tagging does not bypass consent requirements. But technically correct implementation reduces unnecessary signal loss, stabilizes bidding inputs, and makes your reporting closer to operational reality.

If Ads, GA4, and your CRM numbers drift, start with consent sequencing and enhanced conversions before you blame traffic quality.

Sources

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

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.

Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.

Related Posts

Splinternet Marketing