GA4 Conversions Not Showing? The Checks We Run, in Order.

When GA4 conversions are not showing, the cause is almost always one of eight things: you are looking for the old word (GA4 now calls them key events), the event was never marked as a key event, the marked name does not match the event that fires (names are case sensitive), standard reports have not processed yet, a data filter is excluding the traffic, consent mode is withholding or modeling the data, thresholding is hiding rows, or you are comparing GA4 to Google Ads, which counts the same action differently. You confirm which one with Realtime, DebugView, and the Key events list in Admin, then fix the single layer that failed. This piece walks that order and shows what a normal gap looks like.

GA4 records everything as events. A tag on the site (gtag.js or a Google tag in Google Tag Manager) sends each event, such as generate_lead or purchase, with parameters to Google Analytics. An event becomes a key event, the metric formerly called conversions, only when it is marked as one in Admin, under Data display, then Events or Key events. A Google Ads conversion is a separate object built on top of that key event and lives in the Google Ads account. The chain is event, then key event, then Google Ads conversion, and each link can break on its own.

The eight causes we find most often.

We run these checks on our own properties and on every account we take over. The order below is roughly how often each one is the answer.

• Looking for the wrong label: since March 2024 GA4 reports say key events where they used to say conversions, so an older saved report, dashboard or connector can look empty
• Event never marked as a key event: the event arrives and shows in the Events report, but nobody toggled Mark as key event, so it never counts
• Name mismatch: the key event was created by typing a name such as Generate_Lead while the tag sends generate_lead, and GA4 treats them as two different events
• Processing delay: Realtime shows the event within minutes, but standard reports have not processed the day yet, and a newly marked key event can take up to 24 hours to appear
• Data filter excluding the traffic: an active internal or developer traffic filter removes the test conversions you are looking for, permanently
• Consent mode: with basic consent mode, no data is sent until a visitor accepts, and with advanced consent mode, denied visitors are only visible as modeled data when the property qualifies
• Thresholding: GA4 withholds rows in reports that include demographics, search query data, or Google signals based audiences when user counts are low
• Comparing against Google Ads: the imported conversion uses Google Ads attribution, counting and click date, so the two numbers rarely match

How to verify the key event is arriving.

Do not start in the standard reports. They are the last place data lands. Three checks, in this order.

Realtime. Open Reports, then Realtime overview, complete a test form or order, and look at the event count and key events cards. Google says Realtime updates a few minutes after a user triggers a key event. If the event shows here under its exact name, collection works and the problem is downstream.

DebugView. In Admin, under Data display, click DebugView. Turn on debug mode with Tag Assistant at tagassistant.google.com or Google Tag Manager preview mode, then trigger the action. The Seconds stream shows events from the last 60 seconds and the Minutes stream archives the last 30 minutes. Click the event to see its exact name and parameters. Copy that name; you will need it in the next check.

The Key events list. In Admin, under Data display, open Key events and compare every name, character by character, against what DebugView shows. Then open Events and confirm the same name appears under Recent events with Mark as key event toggled on. If the tag itself never fires, stop here and debug the container first with our guide to a Google Tag Manager tag not firing.

Diagnose top to bottom.

Each step isolates one layer. Stop at the first one that fails.

GA4 key events vs Google Ads conversions.

A key event in GA4 does not automatically become a Google Ads conversion. To import it, the GA4 property and Google Ads account must be linked, auto-tagging must be on, and the event must already be a key event. You then create the conversion in Google Ads under Goals, Summary, Create conversion action, choosing the Google Analytics property as the source, or in GA4 under Advertising, Conversion management. Google says it can take up to 24 hours before imported data shows in Google Ads.

Once imported, the conversion follows Google Ads rules. Google Ads reports conversions against the date of the ad click, while GA4 reports the key event on the date it happened. Google Ads counting can be set to Every or One per click, and the conversion window can be 1 to 90 days. GA4 credits all channels, not just paid search. Two different totals are normal. If Google Ads shows nothing at all, work through our Google Ads conversion tracking diagnosis, and consider enhanced conversions or offline conversions from your CRM for leads that close later.

What is normal and what is a red flag.

Some gaps are built into GA4. Google documents that Realtime typically updates within a few minutes, intraday data for a standard property arrives in about 2 to 6 hours, and daily processing takes about 12 hours. Attribution credit for key events can change for up to 12 days after the key event is recorded, so the last two weeks of channel data will move. Before daily processing completes, intraday reports use the paid and organic last click model, and source and campaign can briefly show gaps.

Consent modeling has documented entry requirements. Behavioral modeling needs at least 1,000 events per day with analytics_storage set to denied for at least 7 days, and at least 1,000 daily users with analytics_storage granted for at least 7 of the previous 28 days. Smaller sites usually do not qualify, so denied visitors simply do not appear. That is expected, not a bug.

These are red flags: zero key events for a full day when Realtime shows the event; a key event that is flat at zero while the same event name has a count in the Events report; key events that drop on the day a consent banner, theme, or tag container was changed; and a key events total higher than the real number of leads or orders, which usually means the event fires on page reload or on both a form step and a thank-you page. A higher total is as broken as a missing one. Phone leads are a common blind spot, which our CallRail GA4 integration guide covers, and the full pre-spend check lives in our conversion tracking audit checklist.