Skip to content
whitead

EEA conversion drop after Consent Mode v2 enforcement

playbook google ads updated 2026.04.30 5 min read
// contents · 9 sections
  1. What "EEA conversion drop" actually means
  2. Top 5 root causes
  3. Diagnostic checklist
  4. Fix paths
  5. When to escalate
  6. "Drop is >50% across all conversion actions and all sources — what now?"
  7. "My GA4 shows conversions but Google Ads does not — same Consent Mode wiring?"
  8. "We are Basic by legal mandate — can we recover anything without flipping to Advanced?"
  9. Sources

EEA conversion drops post-2025-07-21 rarely have one cause — five suspects compete: tag break, conversion-action edit, DDA swap, Consent Mode v2, seasonality.

What "EEA conversion drop" actually means

"EEA conversion drop" — when an account serving EEA/UK/Switzerland sees reported conversions fall 20-60% with no change in spend, creative, or pages. Inflection point: 2025-07-21, when Google began silently enforcing Consent Mode v2 — accounts without the protocol stopped receiving modeled conversions and remarketing growth (PPC Land, 2025-07-21). Scope: 27 EU states + Iceland, Liechtenstein, Norway, UK, Switzerland.

The drop is real (modeling stops) and silent (no UI warning) — and overdetermined: the same week often brings a tag rebuild or DDA promotion that independently disturbs the curve.

Top 5 root causes

In order of frequency we observe across audited accounts:

  1. Tag/tracking break. A GTM publish, GA4 migration, or Cookiebot template update silently disconnects the Google tag. Conversions stop firing entirely on one or more pages. Symptom: 0 conversions for one source, not a percentage drop. See fix-conversion-tracking-missing.
  2. Conversion-action edit forces re-learning. Editing a conversion action's category, value, or counting rule resets Smart Bidding's model. Google warns: "Editing a conversion action may affect bidding performance for up to two weeks" (Google Ads Help). Drop appears 24-72h post-edit, recovers ~14 days later.
  3. DDA model swap. Accounts auto-promoted to Data-Driven Attribution from Last Click typically see reported conversions shift -10 to -20% as credit redistributes across the path. Total business value is unchanged; the reporting baseline is.
  4. Consent Mode v2 misconfig (EEA). The 2025-07-21 enforcement target. Either Consent Mode v2 is absent, or it is present in Basic mode — which loses ~40% of modeling capacity vs Advanced (Simo Ahava, 2024). With 60-70% of EEA visitors declining cookies (Dataslayer, 2025), Basic leaves most modeled conversions on the table.
  5. Seasonality. Q1 post-holiday lull, August EU vacation, Ramadan in mixed-market accounts — match the drop window against last year's same week before escalating.

Diagnostic checklist

Run top to bottom; stop at first match.

Order Check Tool Signal of root cause
1 Did any conversion source go to 0? Google Ads → Conversions Tag break (cause 1)
2 Was a conversion action edited in the last 14 days? Conversions → Change history Re-learning (cause 2)
3 Did attribution model change recently? Conversions → Attribution model DDA swap (cause 3)
4 What is gcs= parameter in GA4 DebugView with cookies declined? GA4 DebugView G100=Basic, G110=Advanced (cause 4)
5 Compare same-week YoY spend/conversions Google Ads report Seasonality (cause 5)
6 None match — Escalate (see below)

The gcs check is the highest-leverage one for EEA accounts post-enforcement — it takes 90 seconds and isolates Consent Mode v2 misconfig from the four other suspects.

Fix paths

  • Cause 1 (tag break): see fix-conversion-tracking-missing for the GTM + tag assistant + page-source verification sequence.
  • Cause 2 (re-learning): freeze conversion-action edits, wait 14 days, do not change bid strategy mid-recovery.
  • Cause 3 (DDA swap): not a fix — recalibrate baselines. See data-driven-attribution.
  • Cause 4 (Consent Mode v2 misconfig): wire the protocol or flip Basic → Advanced via your CMP. See consent-mode-v2. Layer enhanced-conversions on top to recover 5-10% more via first-party hashed identifiers.
  • Cause 5 (seasonality): document the YoY pattern and move on.

In EEA audits since 2025-07-21: roughly half of "sudden drop" tickets blamed on Consent Mode v2 turn out to be cause 1 or 2 — a tag rebuilt the same fortnight, or a relabelled conversion action. The enforcement date became a convenient narrative anchor. Discipline: run the checklist in order — tag → edit → attribution → consent → seasonality. When consent IS the cause, it is almost always Basic-mode misconfig (CMP shipped Basic by default and nobody flipped the switch) rather than absent v2. Basic→Advanced recovery typically lands in two weeks — same window as Smart Bidding re-learning.

When to escalate

"Drop is >50% across all conversion actions and all sources — what now?"

That is a tag-layer or account-suspension event, not Consent Mode v2. Check Google Ads policy notifications, GTM container publish history, and whether the conversion linker is still firing. A misconfigured Consent Mode v2 degrades gradually in EEA only — it does not zero out a global account.

Different gates. GA4 uses analytics_storage and models conversions independently of Ads. If GA4 sees them and Ads does not, check the GA4→Ads link, primary-conversion flag, and attribution window before blaming consent.

Partially. Layer enhanced-conversions on top of Basic — hashed email/phone fires only after consent, respecting the same legal posture while recovering 5-10% of the delta. Combined with offline conversion imports, Basic accounts can close roughly half the gap to Advanced.

Sources

← Back to Wiki