You set up an event, marked it as a conversion, submitted the form yourself, and the report still shows zero. It is one of the most common frustrations with GA4, and in the vast majority of cases it comes down to one of five causes that you can check in a fixed order.
First, the patience test: GA4 processes with a delay
Before you rebuild anything, look at the clock. GA4's standard reports process data with a noticeable delay, usually 24 to 48 hours. A conversion you triggered an hour ago does not belong in the "Conversions" report yet. Start tinkering here and you are chasing a ghost.
A new conversion is visible immediately in only two places: the "Realtime" report and "DebugView." That is exactly where you check whether anything arrives at all, before you blame the delay.
Cause 1: the event does not fire at all
Everything else is pointless if the underlying event never fires. Open DebugView, perform the action on the page yourself and watch whether the event appears in the timeline. If it does not, the problem is upstream of GA4: the trigger in Google Tag Manager does not catch, the selector on the button is wrong, or the form loads a new page before the event is sent. How to define an event cleanly in the first place is in setting up conversion tracking.
Cause 2: the "mark as key event" box is unchecked
This is the classic. An event only becomes a conversion in GA4 once you explicitly mark it as a key event (formerly conversion). The event can fire perfectly and appear in the events report while staying invisible in the conversion report as long as the box is unchecked. Find it under "Admin → Events" or "Key events." And: the marking is not retroactive. Conversions are counted from the moment you check the box; the days before stay at zero.
Cause 3: you are looking at the wrong date range or report
GA4 remembers the last chosen date range across reports. Set "last 7 days" yesterday and go looking for an event from an hour ago today, and you see nothing. Just as common: the key event's name is different from what you expect, because GA4 creates automatic events with their own names. A check in the events report clarifies which name your action actually runs under.
Cause 4: filters, consent and internal traffic
Three quiet data eaters. An active internal filter for your own IP discards your test hits exactly when you are testing. A consent banner that loads no tracking without agreement blocks the event for anyone who declines, and often for you too. And if you use Consent Mode, you see modeled rather than counted data, which in small volumes can round to zero. When in doubt, test in an incognito window with explicit consent.
Cause 5: duplicate or missing linking
If your tracking runs through several paths at once, say a hardcoded gtag plus Tag Manager, an event can arrive twice or not at all. And a conversion from search only shows up cleanly attributed when Analytics and Search Console are linked. How that link is made is in setting up Google Search Console. Which four reports actually say something afterwards is in reading GA4.
Frequently asked questions
Why is my GA4 conversion not showing?
Most often because the event is not marked as a key event, or because the 24-to-48-hour processing time has not elapsed. First check in DebugView whether the event fires at all, then the box under "Key events," then the selected date range.
How long does it take for a conversion to appear in GA4?
In the standard reports, usually 24 to 48 hours. In the "Realtime" report and "DebugView," a correctly triggered event is visible immediately. Those two views are the right place to test.
Does GA4 count conversions retroactively when I check the box?
No. An event is only counted as a conversion from the moment you mark it as a key event. The time before stays at zero, even if the event itself already fired earlier.