Registered as a key event, still reporting zero

Symptom

generate_lead is plainly there under Admin → Key events. Someone registered it last month. The conversion count in reports has been zero ever since, and there is nothing to import into your ad platform.

There is a half-broken version too. Conversions do arrive, but at a figure that makes no sense against sessions. Sales knows the form brings in dozens a day; GA4 shows three or four.

Cause

Flipping a toggle in GA4 Admin and firing that event on your site are entirely separate pieces of work. The Admin screen only declares "count this name as a conversion when it arrives". If the name never arrives, nothing happens — and GA4 does not tell you.

Four causes come up repeatedly in real scans.

1. The tag was never built. The name was typed into Admin and the implementation ticket is still in a backlog.
2. The names differ. The site sends lead_submit while Admin has generate_lead. GA4 event names must match exactly, case included.
3. The trigger never fires. A form-submit trigger was set up, but the form lives in an iframe, or the page navigates away before the tag gets to fire.
4. A consent platform blocks it. After a CMP change, the tag no longer runs until analytics consent is granted.

An empty list is a different conversation. A GA4 property with no key events at all is a traffic counter that does not count conversions, and it cannot feed ad optimisation either.

How to check in GA4

Worked in order, this usually narrows the cause within half an hour.

1) Does the name arrive at all? In Reports → Engagement → Events, set the range to the last 28 days and search for the registered name. Absent from the list means cause 1 or 2.

2) Is a similar name there? On the same screen, scan for fragments like lead, submit or form. A near-identical name with a real count settles it as cause 2, and renaming the registration is the fastest fix.

3) Does it fire right now? Open Admin → DebugView and submit the form yourself. If the event appears, the tag is alive and the problem is registration rather than collection. If nothing appears, it is cause 3 or 4.

4) Read it as a ratio. Where conversions do arrive, compare them against the step above. Submissions far below form-page views, or a conversion rate under a hundredth of a percent of sessions, indicate partial collection rather than none.

How to fix it

For cause 2, change the key event name in Admin to the name that actually arrives. The conversion marking applies to data already collected.

For cause 3, change the trigger. When a form navigates immediately after submitting, counting the thank-you page view as the conversion is far more reliable than the submit event. GTM cannot see inside a third-party iframe, so use whatever message or redirect the form vendor posts to the parent window.

Cause 1 is an implementation request. Hand it over with the event name, when it fires, and which parameters ride along, one line each. Renaming later splits your history, so it is cheaper to settle the name up front.

Confirm in DebugView afterwards and watch the number appear in tomorrow's report. Conversion marking is retroactive, but events that were never collected do not come back. The months that read zero stay zero.

In one line

The key events list is a promise; the tag produces the data. Listed but zero means you should suspect collection, not registration — start by checking the name matches, and that is usually where it ends.