Google Analytics Not Tracking Conversions: Fixes

Olamide Sule, founder of Dolphin Analytics: a digital analytics expert based in London delivering solutions for agency and in-house clients.

Conversions dropping out of Google Analytics is one of the most common tracking faults we get called in on, and it’s rarely GA4 breaking. Something around the tag changed: a checkout redesign, a new consent banner, a Measurement ID swap, or a Google Ads link that quietly came apart. This walks the usual causes in the order they’re worth checking, splits the GA4 side from the Google Ads side (people mean different things by “conversions”), and shows how to confirm each one before you touch a setting.

Platform behaviour below is checked against Google’s Analytics and Ads Help, 16 August 2026. Menu names move around; the logic underneath them doesn’t.

GA4 or Google Ads: which conversions have actually stopped?

“Conversions not tracking” points at two different systems that people treat as one. GA4 counts key events (Google’s 2024 rename for what it used to call conversions): actions like a purchase or a form submit that you’ve flagged as worth measuring. Google Ads counts conversion actions: the same kind of event, but imported into Ads so it can attribute a sale back to a paid click. A conversion can be firing perfectly in GA4 and still be absent from Google Ads, because those are two separate pipelines with two separate points of failure.

Work out which one is empty before you start. If GA4’s conversions column shows nothing, the fault sits in GA4 collection or key-event setup. If GA4 shows conversions but Google Ads doesn’t, GA4 is fine and the break is in the import or the click ID. Fixing the wrong pipeline is the usual reason a “quick fix” takes a week.

Why is Google Analytics not tracking conversions? The usual causes, in order

Most missing-conversion cases come down to six causes. Ranked by how often they turn out to be the real culprit:

#	Cause	Which side	Fastest tell
1	Event fires but isn’t marked as a key event / imported as a conversion	GA4 and Ads	Event shows in DebugView, conversions column stays empty
2	Tag stopped firing after a site or checkout change	GA4	Tag Assistant shows the tag never fires on the goal page
3	Consent Mode or the banner is blocking the hit	GA4	EU and UK conversions far below actual orders
4	Duplicate or wrong Measurement ID	GA4	Two GA4 tags, or events landing in the wrong property
5	Google Ads and GA4 not linked, or auto-tagging off	Ads	GA4 has the conversion, Google Ads doesn’t
6	Reporting delay, not a tracking fault	GA4 and Ads	DebugView shows the event; reports catch up next day

1. The event fires but isn’t counted as a conversion

This is the single most common cause, and the most missed. In GA4, an event only becomes a conversion once you mark it as a key event in Admin. The event can fire on every checkout, appear in DebugView, and still show nothing in the conversions column, because the toggle was never switched on, or got switched off when someone rebuilt the property. On the Google Ads side, the same trap has a second layer: the GA4 key event has to be imported as a Google Ads conversion action and set as a primary action for it to count in your campaign columns.

Fix: confirm the event name in DebugView, mark it as a key event in GA4 Admin, then check it’s imported and primary in Google Ads. Do this before anything more involved. It costs two minutes and clears a large share of cases.

2. The tag stopped firing after a site change

A conversion that worked last month and stopped this month usually means the page changed underneath the tag. A checkout redesign moves the thank-you page to a new URL, a form plugin update renames the submit event, a developer ships a single-page checkout and the pageview-based trigger never sees the confirmation step. The tag didn’t break; its trigger no longer matches reality.

Fix: open Google Tag Assistant and complete the conversion on the live site. If the tag never fires, the trigger is the problem. Update it to match the new URL, event or DOM element, then retest. This is where a broken trigger after a redesign hides, and it’s worth checking early whenever the timing lines up with a site release.

3. Consent Mode or the banner is blocking the hit

If your conversions look low rather than zero, and the gap is concentrated in EU and UK traffic, suspect consent before anything else. With Google Consent Mode, a visitor who hasn’t granted analytics consent generates no standard GA4 conversion hit. Basic Consent Mode blocks the tag entirely until consent; advanced Consent Mode sends cookieless pings that Google uses to model the gap. A banner that defaults everything to denied, or a Consent Mode setup that never upgrades to granted when someone clicks accept, silently removes a chunk of every campaign’s conversions.

Fix: test the flow with consent denied and again with consent granted, watching DebugView both times. The behaviour you see tells you whether the banner, the Consent Mode wiring, or the default state is the culprit. Google’s own Analytics Help documents the two Consent Mode modes if you need the exact settings.

4. A duplicate or wrong Measurement ID

Two GA4 tags on the same page, or the wrong Measurement ID after a migration, scatters conversions. Events land in a property nobody’s looking at, or fire twice and get deduplicated in ways that make the totals look wrong. This one hides well because the reports aren’t empty; they’re just off.

Fix: use Tag Assistant to list every GA4 tag firing on a page and the Measurement ID each one sends to. One clean tag per property per page is the target. If you find two, work out which is the live one and remove the other. The GA4 audit checklist covers this data-stream pass in more detail.

5. Google Ads and GA4 aren’t linked, or auto-tagging is off

When GA4 records the conversion but Google Ads shows nothing, the break is between the two products. Either the accounts aren’t linked, the GA4 key event was never imported into Ads, or auto-tagging is switched off so the GCLID (the click ID Google Ads stamps on every ad click) never reaches your landing page. No GCLID, no way for Ads to tie a conversion back to the click that paid for it.

Fix: confirm the GA4 to Google Ads link, import the key event as a conversion, and check auto-tagging is on in your Google Ads account settings. Google’s Ads Help covers auto-tagging and the GCLID if a redirect or a landing-page platform is stripping the parameter, which is a frequent offender on sites that route paid traffic through a redirect first.

6. It’s a reporting delay, not a tracking fault

Before you rebuild anything, rule out timing. GA4 can take up to 24 to 48 hours to fully process conversion data on standard properties, and Google Ads applies its own conversion window and modelling, so today’s numbers keep moving for a day or two. A conversion that looks missing at 9am can appear by tomorrow with nothing changed.

Fix: use DebugView for the real-time check. It confirms the event fired within seconds, so you’re not chasing a configuration ghost that’s really just processing lag. If DebugView shows the event but the standard reports still show nothing after 48 hours, then it’s configuration, and one of causes 1 to 5 above is in play.

How to confirm which cause it is

Don’t guess and change settings at random; each change you make blind hides the next clue. Run this sequence instead:

1. Reproduce it live. Complete the conversion yourself on the real site, not a staging copy, with DebugView and Tag Assistant open.
2. Watch Tag Assistant. Did the tag fire on the goal page? No means a trigger problem (cause 2) or a consent block (cause 3). Yes moves you on.
3. Watch DebugView. Did GA4 receive the event, with the right name and parameters? No with a firing tag points at the wrong Measurement ID (cause 4). Yes moves you on.
4. Check key events. Is the event marked as a key event in GA4 Admin? If not, that’s cause 1.
5. Check the Google Ads side. Is the key event imported as a conversion, the accounts linked, and auto-tagging on? Gaps here are cause 5.
6. Give it 48 hours. If everything above checks out, the last suspect is processing delay (cause 6).

Working the pipeline in order, rather than jumping to the setting you suspect, is what turns a week of trial and error into an afternoon.

GA4 side vs Google Ads side: a quick reference

The two pipelines fail differently, so the fixes live in different places:

Symptom	Look here first
GA4 conversions column empty, event in DebugView	Key event toggle in GA4 Admin
No event in DebugView at all	Trigger broken, or consent blocking the tag
EU and UK conversions far below real orders	Consent Mode and the banner default
Events split or doubled	Duplicate tag or wrong Measurement ID
GA4 has conversions, Google Ads doesn’t	Account link, conversion import, auto-tagging
Numbers keep changing for a day or two	Processing and attribution windows, not a fault

If the discrepancy is the other way round, with Google Ads or Meta claiming more conversions than your store confirms rather than fewer, that’s a separate problem worth reading up on: why Meta Ads over-report conversions walks through view-through inflation and how to reconcile it.

When to get a second pair of eyes on it

If you’ve walked the sequence and conversions are still missing, the fault is usually somewhere the dashboards don’t show you: a tag that fires on the wrong event, a consent state that never upgrades, a redirect stripping the GCLID before the pixel loads. Sonar, our free tracking checker, scans any site and shows what GA4, Google Tag Manager and ad pixels are actually firing from the outside, which is often the fastest way to see the gap between what you think is installed and what really is.

For anything past that, the free data audit is built for exactly this. Send us the property and the conversions you’re missing, and we’ll find where the pipeline breaks and tell you how to fix it, before you rebuild tracking you might not need to touch. Broken conversion tracking is the first thing our tracking work is designed to catch.