GA4 Not Recording Conversions? Common Causes to Check

2. Start Here: Is It Really “Not Recording”?

Quick Answer: Before changing anything, open GA4’s DebugView, then complete the action on your own site — submit the form, finish the checkout. If the event shows up but your Key events report stays empty, the event simply isn’t flagged as a key event. If the event never appears at all, the tag isn’t firing. Those are two different fixes.

The phrase “not recording conversions” hides two very different problems, and telling them apart saves you an hour. One is a collection problem, where GA4 never receives the event. The other is a configuration problem, where GA4 receives the event fine but you never told it that event counts as a conversion — so it records the hit but never reports it as a key event.

Run this two-minute test before touching any settings:

• Open Admin → DebugView (or enable debug mode with the Tag Assistant). Then complete the conversion action yourself — the purchase, the form submit, the booking.
• If your event appears in DebugView but the Key events report is empty, collection works. The event just isn’t marked as a key event yet — a config fix, covered below.
• If nothing appears in DebugView, the tag or trigger isn’t firing. That’s a collection problem, and it’s where you start.

Google’s own explainer on conversions vs. key events is worth a read here, because the 2024 rename is behind a lot of these cases. If instead your reports are empty across the board — not just conversions — that’s a wider tracking break, and fixing GA4 showing no data is the right starting point.

3. What Actually Stops GA4 Recording Conversions?

Quick Answer: Across ZenWeb client cases, most GA4 not recording conversions problems come from a handful of causes. An event that was never marked as a key event and an event that isn’t firing together explain almost half. Name mismatches, consent blocking, and a broken Google Ads import cover most of the rest. Knowing the odds tells you where to look first.

Not every cause is equally likely. When you know which ones show up most, you check them first and stop wasting time on rare edge cases. The chart below shows how cases of GA4 not recording conversions break down across the Malaysian accounts our team has diagnosed.

The pattern is reassuring. Nearly half of all cases sit in the first two rows — a flagging problem or a firing problem — and both are fixable in minutes once you spot them. The rename-related “never marked as a key event” case is now the single biggest one, which is why it leads the list. If your digital marketing reporting depends on GA4, it pays to know these odds before you start clicking.

4. Match Your Symptom to the Cause

Quick Answer: The exact shape of your problem is a strong clue. An event that fires but never counts points to a missing key-event flag. Nothing in DebugView points to a broken tag. Conversions in GA4 but zero in Google Ads points to a broken import. Match the symptom first, then check one thing.

When GA4 is not recording conversions, the exact symptom is a strong clue. Read the pattern you’re seeing and go straight to its most likely cause — the table below maps each one to where you should look first.

Notice how often the fix is a single check, not a rebuild. The “zero in Google Ads” row deserves special care — a key event can count perfectly in GA4 yet still show nothing in your ad account if the import was never linked. That mismatch has its own playbook: read why GA4 and Google Ads numbers don’t match when the two platforms disagree.

5. The Fix Workflow: 7 Checks in Order

Quick Answer: Run these seven checks from fastest to rule out to slowest. Confirm the event fires in DebugView, check it’s marked as a key event, verify the event name matches, inspect the trigger, check consent, confirm the Google Ads import, then allow for processing lag. Stop the moment one check explains the problem.

When GA4 is not recording conversions, order matters — some causes take seconds to rule out, others take a day of waiting. Work top to bottom and stop as soon as you find the culprit.

1. Fire the event yourself and watch DebugView. Complete the conversion action on your own site with debug mode on. If the event doesn’t appear here, it’s a firing problem — skip to step 4.
2. Check it’s marked as a key event. Under Admin → Events, confirm the toggle beside your event is on. Google’s guide to marking events as key events shows exactly where. This one setting explains most cases.
3. Verify the event name matches. The name in your tag must match the name GA4 expects, character for character. Purchase and purchase are not the same event. A rename in “Modify event” also breaks the link.
4. Inspect the trigger. In Google Tag Manager, confirm the trigger fires on the right action — the thank-you page load, the button click — and only then.
5. Check consent and cookie settings. If a consent banner blocks analytics until a visitor clicks accept, conversions from anyone who ignores it never send. Confirm your banner still allows measurement.
6. Confirm the Google Ads import. If GA4 counts the conversion but Google Ads doesn’t, the key event must be imported as a conversion. Google’s steps for importing Analytics conversions into Google Ads cover the link.
7. Allow for processing lag. Marking an event as a key event is not retroactive, and new key events can take 24 to 48 hours to settle in standard reports.

This is the same first-hour sequence our team uses. Fix one thing, re-test in DebugView, and only move on if the problem survives. Random poking is what turns a ten-minute fix into a lost afternoon.

6. How Long Until Conversions Show Up?

Quick Answer: Recovery time depends on the fix. Marking an event as a key event counts from the next event on — it never backfills the past. Repairing a tag shows in DebugView within minutes but standard reports still need a processing cycle. A fresh Google Ads import can take up to a day to appear in the ad account.

When GA4 is not recording conversions, the most common mistake after a fix is expecting the report to fill instantly, then fixing again when it doesn’t. The table below sets realistic expectations by fix type.

7. Why the “Key Events” Rename Broke So Many Setups

Quick Answer: In 2024 GA4 renamed “conversions” to “key events,” and the change quietly broke a lot of setups built around the old label. A growing share of no-conversion cases now trace to this rename — people looking for a “Conversions” toggle that moved, or guides that no longer match the interface.

When Google renamed conversions to key events, the metric didn’t disappear — but the menus, toggles, and half the tutorials online stopped matching what business owners saw on screen. The result is a steady rise in cases where conversions go quiet not because tracking broke, but because the setup was following instructions for an interface that no longer exists.

The fix is not complicated once you know the label changed: what you’re hunting for is the key-event toggle, not a “Conversions” button. Keeping your tracking current with GA4’s interface keeps your digital marketing reporting honest, and stops GA4 not recording conversions the next time Google moves a menu.

8. Fix It Yourself, or Call in a Team?

Quick Answer: When GA4 is not recording conversions, simple causes — an unflagged key event, a name typo, a stray filter — are safe to fix yourself. Get help when the event lives inside a complex tag manager setup, when consent mode is involved, or when ad budgets and bidding depend on the conversions being right.

You don’t need an agency for every no-conversion case. Use this rough line to decide:

• Fix it yourself when the cause is obvious and contained — one toggle, one name, one trigger you can correct and re-test in DebugView in minutes.
• Call for help when the event sits in a layered Google Tag Manager container, consent mode needs configuring, or the same conversions feed Google Ads Smart Bidding and the reports you spend real money against.

A wrong guess here is quietly expensive. While GA4 is not recording conversions, your Smart Bidding is optimising on blanks and you’re flying blind on every campaign — the same blind spot that makes a sudden ranking drop so costly when you can’t see what changed. For most Malaysian SMEs, getting conversion tracking watertight once pays for itself many times over. Our digital marketing service sets up and audits GA4 conversions as standard.

9. Conclusion

When GA4 is not recording conversions, speed comes from order, not effort. Confirm whether the event fires with the DebugView test, then work the seven checks from fastest to slowest: fires, flagged as a key event, named right, trigger, consent, Google Ads import, and processing lag. Most cases reveal themselves inside an hour.

Resist the urge to rebuild everything at once — that only hides the real cause. Fix one thing, re-test, and mark your events as key events the moment you deploy them so history never goes missing. If your setup is complex or your campaigns depend on the numbers, the team at ZenWeb can get your conversion tracking clean and keep it that way.

10. Frequently Asked Questions

1. Why is GA4 not recording conversions even though I’m getting sales?

The most common reason is that the event fires fine but was never marked as a key event, so GA4 collects it without reporting it as a conversion. Open DebugView and complete the action — if the event shows there but your Key events report is empty, just toggle it on under Admin → Events. If nothing shows in DebugView, the tag isn’t firing.

2. How do I mark an event as a key event (conversion) in GA4?

Go to Admin, then Events under Data display, find your event in the list, and switch on the “Mark as key event” toggle beside it. If the event isn’t listed yet, complete the action once so it appears, or create it under Create event. Marking is not retroactive, so it only counts conversions from that point forward.

3. Why do my GA4 conversions not match Google Ads?

GA4 and Google Ads count conversions differently and use different attribution windows, so some gap is normal. A total zero in Google Ads usually means the key event was never imported as a conversion, or the accounts aren’t linked. Check Admin → Google Ads Links, then confirm the import. Our guide on GA4 versus Google Ads mismatches covers the full reconciliation.

4. How long does GA4 take to show a new conversion?

DebugView shows the event within seconds, and the Realtime report within a minute or two. Standard reports like Key events are different — a newly marked key event can take 24 to 48 hours to settle. If DebugView shows the event but the standard report is still blank on day one, that gap is normal and just needs time.

5. Can a cookie consent banner stop GA4 recording conversions?

Yes. If a consent banner blocks analytics until a visitor clicks accept, conversions from anyone who ignores or declines it never send. When consent mode isn’t configured, this can hide a large share of real conversions. The fix is to set up consent mode so measurement resumes on acceptance, not to remove the banner.