Skip to main content
TrackingConsulting

0%

Ga4Google Ads

GA4's 2026 Changes Broke Your Google Ads Conversions? Here's the Fix

AI

Ariful Islam

Founder · Tracking Consultant

Updated

August 8, 2026

Reading time

12 min read

Every time Google ships a measurement update, I get some version of the same message within a week: "Conversions fell off a cliff overnight and we changed nothing." Usually true. Google did. The good part: post-update breakage is boringly predictable, and each failure class has its own fingerprint.

Three columns matching post-update symptoms to causes: a partial drop from a counting shift, a flatline from a renamed key event, and match-rate warnings from missing user data.
The symptom names the fix — read the conversion action's status column before you touch a tag.
Down 20–40%, still firingFlatlined to zeroMatch-rate warnings
Status: Recording conversionsStatus: No recent conversionsUser-data variable returns undefined
Counting or attribution shiftedA GA4 key event was renamedEmail not lowercased, phone not E.164
Check Conversions vs All conversionsThe import listens for a dead namead_user_data denied after a banner change
Re-baseline, then reset tCPA/tROASCreate a new conversion action

What are the symptoms that an update broke your Google Ads conversions?

The symptoms cluster into four patterns, and yours tells you the fix:

  • Conversions dropped 20–40% but didn't die. Purchases still record, just fewer. Smells like a counting or attribution shift, not a broken tag.
  • Conversions flatlined to zero and the conversion action shows "No recent conversions" or "Inactive" in Google Ads. Broken import — very often a key event rename.
  • Enhanced conversions diagnostics started complaining about match rate or missing user data. Your hashed email or phone stopped arriving or stopped matching.
  • Remarketing lists are shrinking or campaigns throw "audience too small." The GA4-to-Ads audience pipe got pinched.
  • Smart Bidding went volatile — CPA up, campaigns back in "Learning." That's the downstream echo of any of the above. Fix the signal, not the bidding.

One thing up front: don't blame a specific changelog entry until you've confirmed it. Google's Ads and GA4 release notes are the primary source — read them before telling stakeholders what happened.

Six diagnostic steps from the Google Ads conversions summary through action diagnostics, GA4 key events, the Ads link and a DebugView test to a seven-day count comparison.
Ads tells you fastest whether data arrives at all; GA4 tells you why it stopped.
  1. Google Ads → Goals → Conversions — Read the status column first: Inactive means the import is dead, lower means a shift
  2. Open the action's diagnostics — Enhanced conversions match-rate warnings live here
  3. GA4 → Admin → Key events — Confirm the event exists, is spelled identically, and is still marked a key event
  4. GA4 → Admin → Google Ads links — The link must be active with personalized advertising switched on
  5. Fire a test purchase in DebugView — If GA4 never sees it, the tag or consent broke and the update is a coincidence
  6. Compare 7 days of GA4 vs Ads — The gap between key events and Ads conversions tells you which class of break you have

Where do I look first to diagnose the problem?

Start in Google Ads, not GA4 — Ads tells you fastest whether data arrives at all. My order on every audit:

  1. Google Ads → Goals → Conversions → Summary. Read the status column. "Inactive" or "No recent conversions" means the import is dead. "Recording conversions" with lower numbers means the pipe works and something upstream shifted.
  2. Open the conversion action's diagnostics. For enhanced conversions, this is where match-rate warnings live.
  3. GA4 → Admin → Key events. Confirm the event exists, has the exact same name, and is still toggled as a key event. Google renamed "conversions" to "key events" back in 2024, and that shuffle alone stranded plenty of Ads imports.
  4. GA4 → Admin → Google Ads links. Confirm the link is active and personalized advertising is on.
  5. GA4 Realtime or DebugView. Fire a test purchase. Does it show up in GA4 at all?
  6. Compare counts. GA4 key events versus Ads conversions for the same 7-day window. The gap shows where the loss sits.

Decision logic: event fires in GA4 but Ads shows nothing — import or link problem. Both down together — your tag or consent setup broke; the update is coincidence. Ads down modestly while GA4 holds — counting change or match-rate drop.

Why did my conversion counts shift without dying?

Because Google changed how conversions get counted or attributed, not whether they get tracked. Updates to data-driven attribution, engaged-view counting, and cross-device modeling all move the conversions column without a single tag misfiring. Google sometimes restates recent data too, which is why last Tuesday's report no longer matches its own screenshot.

The fix is mostly re-baselining, not repair:

  1. Check the action's counting setting — "Every" versus "One" per click.
  2. Check the action's attribution model. If it moved, old comparisons are apples to oranges.
  3. Compare "Conversions" against "All conversions." If All conversions held steady, nothing broke; the primary column's definition moved.
  4. Annotate the date in reporting.
  5. Reset tCPA and tROAS targets, since the number Smart Bidding optimizes toward just changed.

Why did my enhanced conversions match rate drop?

Because the first-party data you send stopped arriving, stopped validating, or stopped being allowed. Enhanced conversions hashes your customer's email or phone with SHA-256 and matches it against signed-in Google accounts. Three common killers after an update:

  • The data variable went empty. A checkout redesign changes the DOM, and the CSS-selector variable scraping the email now returns undefined. The tag still fires — with nothing in it. Number one cause I find.
  • Formatting stopped validating. Emails need lowercasing and trimming before hashing; phones need E.164 format. Lose that step and matches drop silently.
  • Consent started gating the data. Under Consent Mode v2, if ad_user_data is denied, that user's data doesn't go to Google. A banner update that changed defaults will crater your match rate without touching a tag.

The fix: fire a test conversion with GTM preview open and confirm the user-data variable actually contains an email when the tag fires. Move the source from DOM selectors to a dataLayer push from your own code, let the Google tag handle hashing, and check your banner's default consent state for EEA traffic.

Why are my remarketing audience lists shrinking?

Because the pipe feeding them got pinched somewhere between GA4 and Ads. Lists depend on a chain: ads personalization signals in GA4, consent, an active property link. Break any link in that chain and new users stop entering your lists while existing members age out. That's why lists shrink gradually instead of dropping to zero — and why people notice this class last.

  1. In GA4 Admin, confirm ads personalization signals are enabled, including per-region controls.
  2. Confirm the Google Ads link is active.
  3. In Ads Audience Manager, open the shrinking list and check its source. If the GA4 property shows disconnected, relink and rebuild.
  4. Check the audience definition in GA4 itself — if it references a renamed event, it's filling from an empty query.
A renamed GA4 key event leaves the Google Ads action listening for a name that gets no data, so it goes silent until a new import is created and the old action demoted.
You can't repoint an existing import — Google Ads matches a key event by its exact name.
  1. GA4 key event renamed — A migration or cleanup renames the event
  2. Ads keeps old name — Import listens for a name with no data
  3. Silent, not an error — Status shows No recent conversions
  4. New import, new name — Mark it a key event, set the action Primary
  5. Old action Secondary — History kept — never delete the old one

How do I fix a key event rename breaking my Ads import?

You create a fresh import for the new event name — you can't repoint the old one. Google Ads imports a GA4 key event by its exact name. Rename the event, or let a migration rename it for you, and the imported action keeps listening for a name that no longer receives data. It doesn't error. It goes silent.

  1. In GA4, confirm the new event fires and mark it as a key event.
  2. In Google Ads, create a new conversion action importing the new key event.
  3. Set the new action as Primary so it feeds bidding.
  4. Demote the old action to Secondary. Don't delete it — that throws away your conversion history.
  5. Watch for double counting while both fire, and confirm value and currency settings on the new action.

How do I stop the next update from breaking my tracking?

Shrink the surface area Google's changes can touch, and make breakage page you instead of hiding for weeks:

  • Own your dataLayer. Push events with your own names and parameters from your own code, and map them to platforms inside GTM. When a platform changes, you change one mapping. Highest-value move on this list.
  • Set drop alerts. Google Ads custom rules can email you when conversions fall past a day-over-day threshold, and GA4 custom insights flag anomalies on key events. Two alerts, ten minutes.
  • Read the release notes. Skim Google Ads and GA4 release notes monthly and annotate reporting when a counting change lands.
  • Consider server-side GTM. sGTM gives you a control point between site and Google, so you can remap event data without touching site code. Week-long fixes become hour-long ones.
  • Document the mapping. One page of GA4 event to Ads conversion action turns diagnosis from archaeology into a checklist.

The accounts that survive updates without drama have a boring, documented dataLayer and alerts.

Is server-side tagging part of this fix or a separate project?

Everything above fixes configuration — the settings that break attribution even when the data arrives. But arrival is its own problem. A meaningful share of your conversions never reach Google because the browser tag was blocked, the consent state delayed it, or the cookie expired before the return visit. Config fixes can't recover signal that never left the device.

That's what a first-party server-side layer adds. Your tags load from your own subdomain instead of Google's, which takes them off the blocklists; conversions can be sent from the server with the stored click ID even when the thank-you page tag fails; and first-party cookies extend attribution windows that ITP would otherwise cut to days. Fix the settings first — it's free and fast. Then fix the signal, because Smart Bidding can only optimize toward conversions it can see.

Frequently asked questions

Why did my Google Ads conversions suddenly drop when I changed nothing on my site?

Most likely a platform-side change: a counting or attribution shift, an enhanced conversions match-rate drop, or a key event rename that broke your GA4 import. "No recent conversions" on the action's status means a broken import; lower-but-present numbers point to counting or matching.

How do I know if a GA4 update broke my conversions or my tag did?

Compare GA4 and Google Ads for the same window. Event fires in GA4 but Ads records nothing: the import or link broke. Both dropped together: your tag or consent setup broke, and the update is probably coincidental.

Should I delete the old conversion action after a key event rename?

No. Demote it to Secondary and keep it. Deleting destroys your conversion history and your ability to compare performance across the rename.

No. Lists refill going forward only, so a 30-day audience takes up to 30 days to repopulate. Missed users aren't added retroactively.

How long until Smart Bidding recovers after I fix a conversion break?

Expect roughly one to two weeks of recalibration after conversion data stabilizes. Avoid large budget or target changes during that window.

Yes. If ad_user_data is denied, that user's hashed email and phone don't go to Google at all, so a banner change that shifts defaults lowers your match rate without any tag breaking.

Does server-side tagging prevent Google updates from breaking my tracking?

It can't prevent platform-side changes like counting shifts, but it gives you a control point to remap event data without touching site code, turning most breakage into a quick fix instead of a redeploy.

ga4google adsenhanced conversions

Need help implementing this?

We help brands fix server-side tracking, consent mode, attribution, and conversion validation so reporting becomes easier to trust.

Keep reading

Related articles

WhatsApp