Update time: March 16, 2026
If you’ve spent time setting up a custom event in Google Tag Manager or directly in GA4, tested it in Preview mode or DebugView, watched it fire perfectly — and then opened your GA4 reports only to find nothing — I’ve been there. It’s frustrating, confusing, and honestly, it happens more often than most people admit.
In this article, I’ll walk through the most common reasons why GA4 events (especially custom events) don’t show up in reports, what you can do about each one, and how to systematically narrow down the root cause.
Data Delay
GA4 reporting is not always real-time. I know, it would be nice if it were, but that’s not how it works. Newly created events can take some time before they show up in standard reports. In many cases, you’ll need to wait up to 24 hours for an event to appear, and some reports and explorations can take 24–48 hours to fully process the data from your website or app.
I’ve written more about this here: GA4 Data Delay: How Long It Really Takes
What to do: Give it some time and check back after 24–48 hours.
Data Thresholds
If your data volume is relatively small, GA4 may apply data thresholds to protect user privacy. When thresholds kick in, some data simply won’t appear in your reports — even though it was collected correctly.
What to do: Extend the date range to increase data volume, or wait until GA4 collects enough traffic so demographic data can become available automatically.
GTM Container Not Published
This one is deceptively common. If you implemented the event via Google Tag Manager, it will work perfectly in Preview mode — that’s the whole point of Preview. But in production, nothing gets sent unless the container is actually published.
What to do: Double-check that your GTM container has been published after your changes. It sounds obvious, but you’d be surprised how often this is the culprit.
Custom Event Name Mismatch
Here’s a subtle one. You may have defined a custom event in GA4 under one name (say, generate_lead) but your GTM tag or code is sending it under a slightly different name (generate_lead_form, lead_generated, or with a typo). GA4 won’t merge these — they’re treated as entirely separate events.
What to do: Double-check the event name in your GTM tag (or your code) against the event name in Admin → Events in GA4. They must match exactly, including case sensitivity.
Data Filters
If you have Data Filters enabled in GA4, certain traffic (like internal traffic from your own IP) can be excluded from reports. So if you’re testing and your own IP is being filtered, those test events will never make it to the reports — even though they fired perfectly.
What to do: Go to Admin → Data Settings → Data Filters and review your active filters. Make sure the traffic you’re testing with isn’t being filtered out.
Browser Extensions Blocking GA4
This one is tricky because it happens silently. Some browser extensions — ad blockers, privacy tools, script blockers — can block GA4 tracking requests. The event fires on your page, but the request never reaches Google’s servers.
What to do: Open your browser’s Developer Tools → Network tab and filter the requests using v=2. If you see requests starting with collect, your GA4 tracking requests are going through. If not, try disabling your extensions one by one to find the culprit.
Incorrect Date Range
Sometimes the explanation is boringly simple. If the date range in your report doesn’t include the time when the event was triggered, you won’t see it. I’ve done this more times than I’d like to admit.
What to do: Make sure the report’s date range covers the period when you fired the event. When in doubt, use a broader range.
Viewing the Wrong Property
If you implemented the event in Property A but you’re checking Property B… well, you’re not going to find it. This happens more often when you manage multiple GA4 properties — it’s easy to get them mixed up.
What to do: Confirm you’re looking at the correct GA4 property before you start troubleshooting anything else.
Looking at the Wrong Report
Not all reports show event data. If you’re checking the Pages and Screens report, for example, it focuses on page-level metrics, not specific events. So even if your event is firing correctly, you won’t see it there.
What to do: Check your event in Reports → Engagement → Events or use the Explore section for deeper analysis.
Final Words
Ten reasons, one goal: helping you figure out why your GA4 custom events aren’t showing up. Some of these are quick configuration checks, others require a bit of patience and methodical testing. I’ve been through almost all of them myself, probably more than once.