A laptop shows a detailed financial graph with a clear reflection on a glossy surface.

Enhanced Conversions + Consent Mode v2: Why Ads Look Stable but Data Isn’t

If your Google Ads conversions look steady but GA4 and your CRM show flat or inconsistent lead volume, you likely have a signal problem — not a sudden performance gain.

In 2026, the common driver is the interaction between Consent Mode v2, Enhanced Conversions for Leads, and conversion modeling. Google Ads can report stable totals because it may combine observed data, hashed first‑party matches, and modeled conversions. Your CRM only records actual submitted leads.

For WordPress and WooCommerce operators running GTM or gtag, this is now an operational discipline, not a set‑and‑forget configuration.

What Google Documents vs. What You’re Seeing

Google’s documentation distinguishes three measurement states:

  • Observed conversions: A Google tag fires with consent and required identifiers available.
  • Enhanced conversions for leads: First‑party user data (such as email or phone) collected at conversion is normalized and hashed (SHA‑256) before being sent to Google to improve match rates.
  • Modeled conversions: When user-level signals are unavailable due to consent choices or technical limits, Google may use modeling to estimate conversions in aggregate.

According to Google Ads Help: About consent mode and About conversion modeling, when consent is denied, tags can send limited cookieless pings and Google may apply modeling to reduce undercounting. Modeled conversions are documented as statistical estimates — not user-level recorded events.

Consent Mode v2 adds two documented parameters — ad_user_data and ad_personalization — that signal whether user data can be used for ads measurement and personalization (Google Ads Help: Consent Mode v2 updates; Google Tag Platform: Set up consent mode). If these signals are missing or misconfigured, tags may not behave as intended.

Separately, Google Ads Help: About enhanced conversions for leads explains that properly formatted and hashed first‑party data can improve match quality when identifiers are limited.

The reporting gap forms here:

  • Google Ads can report observed + enhanced + modeled conversions.
  • GA4 may show fewer user-level events depending on consent state, attribution settings, and configuration.
  • Your CRM shows only completed submissions or imported offline events.

Stable Google Ads conversions do not automatically mean stable lead volume or lead quality. They may reflect improved match rates or modeled lift rather than an increase in real‑world form submissions.

Where WordPress and WooCommerce Setups Lose Signal

Across U.S. SMB audits, these failure patterns repeat:

  • Late consent defaults. Google’s tag documentation specifies that a default consent state should be set before tags fire. If your CMP loads after GTM initializes, early pageviews or conversions may fire under the wrong state.
  • CMP not pushing updates. The banner updates its UI, but no consent update reaches GTM or gtag. In Preview mode, consent state never changes.
  • Duplicate tagging. GA4 via GTM plus GA4 via a plugin. Or a hardcoded gtag plus GTM. This fragments attribution and can distort counts.
  • Broken enhanced conversion preprocessing. Enhanced Conversions require proper normalization and SHA‑256 hashing before transmission. Formatting errors (extra spaces, inconsistent casing, missing country codes) can silently reduce match rates.
  • No CRM reconciliation. Google Ads “All conversions” includes modeled conversions. Your CRM does not. Without monthly reconciliation, forecasting drifts.

Modeled conversions are not a bug, and Google does not present them as fabricated events. But Smart Bidding optimizes on the conversion signals it receives. If those inputs mix partial consent states, duplicate tags, and inconsistent enhanced conversion data, CPA and ROAS reporting become less reliable for forecasting.

Also note: GA4 and Google Ads use different attribution models and reporting scopes. Differences alone are not proof of an error. The issue is unexplained drift tied to signal loss.

What to do next

1. Verify consent sequencing in GTM.

  • Use GTM Preview to confirm a default consent state fires before any Google tag.
  • Confirm ad_user_data and ad_personalization update correctly after banner interaction.

2. Audit for duplicate tags.

  • Search your theme and header for hardcoded gtag scripts.
  • Disable overlapping measurement in WordPress plugins if GTM is your control layer.

3. Check Enhanced Conversions diagnostics.

  • Review status and match rate indicators inside Google Ads.
  • Validate normalization before hashing in your form or GTM workflow.

4. Reconcile Ads vs. CRM monthly.

  • Compare CRM-submitted leads to Google Ads “All conversions.”
  • Document the delta and track whether modeled conversions are widening the gap.

5. Align bidding with qualified outcomes.

  • If revenue or sales qualification matters, import offline conversions.
  • Avoid assuming modeled top‑funnel conversions equal revenue‑qualified leads.

Consent Mode does not override legal obligations, and modeling does not replace first‑party data governance. In 2026, paid media performance depends as much on measurement hygiene as on creative or targeting.

If your Google Ads dashboard looks stable, verify that stability at the CRM and revenue layer. Don’t assume it.

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.