How to Check Events in Google Analytics 4

Switching to Google Analytics 4 means getting familiar with a whole new way of thinking about your data, and at the core of it all are events. But once you've set them up, figuring out where to actually see them can feel like a scavenger hunt. This guide will show you exactly where to look for your event data in GA4, from a quick check to see if they're firing properly to building custom reports for deeper analysis.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

First, What Is a GA4 Event?

Before checking for events, it helps to understand what GA4 is actually tracking. Unlike Universal Analytics, which was built around sessions and pageviews, GA4 is built entirely on an event-based model. This means almost every interaction is captured as an event - a page view, a scroll, a button click, a form submission, a purchase, etc.

This is a big advantage because it gives you a much more flexible and user-centric view of what's happening on your site. There are four main categories of events in GA4:

• Automatically Collected Events: These are the basics that GA4 tracks out-of-the-box when you install the tracking code. Think session_start, first_visit, and user_engagement.
• Enhanced Measurement Events: These are common interactions you can turn on with a simple toggle in your GA4 settings. They include handy events like page_view, scroll (when a user scrolls 90% of a page), click (for outbound links), and file_download.
• Recommended Events: Google provides a long list of suggested event names for standard scenarios, like generate_lead for a form submission or add_to_cart for e-commerce. Using these standard names helps GA4 understand your data better.
• Custom Events: If none of the above fit your needs, you can create your own custom events. This is what you’ll do to track very specific interactions, like watching a certain video, clicking a unique call-to-action button, or interacting with a specific website feature.

Method 1: The Quick Check with the Realtime Report

The first place to look, especially right after you've implemented a new event, is the Realtime report. Think of this as your immediate "is this thing on?" check. The data here won't be rich with detail, but it will confirm if GA4 is receiving your event.

When to Use It:

Use the Realtime report for immediate validation. If you just configured a contact_form_submission event in Google Tag Manager, this is where you go to see if it's firing correctly after you test it.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

How to Access It:

1. On the left-hand navigation menu in GA4, go to Reports.
2. Under Reports, click on Realtime.
3. Look for the card titled "Event count by Event name."

You should see your new event appear in this list within seconds of triggering it on your website. You can even click on the event name in the list to see the parameters being sent along with it. Don't panic if you don't see it immediately in other reports, standard reports can take between 24 and 48 hours to fully process event data.

Method 2: Viewing All Events in the Engagement Report

For a detailed overview of all your events over a specific time period, the main "Events" report is your primary destination. This is where you'll spend most of your time when analyzing general event performance.

When to Use It:

Come here when you want to see a summary of how many times each event has occurred, how many users have triggered it, and if there are conversion events, how much revenue is associated with them.

How to Access It:

1. From the left-hand menu, navigate to Reports > Engagement.
2. Click on Events.

This will bring you to a table listing every event GA4 has collected. The default columns are:

• Event name: The name of the event (e.g., page_view, form_submit).
• Event count: The total number of times the event was triggered.
• Total users: The number of unique users who triggered the event.
• Event count per user: The average number of times a user triggered the event.
• Total revenue: If you're tracking e-commerce, this shows the revenue associated with the event.

Drilling Down on a Specific Event

The real value of this report is what happens when you click on a specific event name. Doing this takes you to a more detailed report for just that event. For example, if you click on the page_view event, you’ll see cards showing which pages are viewed most, which countries your viewers are in, and more.

This drill-down view is crucial for understanding the context around your events. For a custom event like request_demo, clicking on it could show you details like the source/medium of users who requested a demo and their geographic location, all powered by the parameters you're sending with the event.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Method 3: Advanced Analysis with Explorations

What if you want to answer a more specific question, like "Which blog posts are generating the most newsletter RSVPs?" Standard reports can't easily answer this. For this level of detail, you need to use the "Explore" section to build a custom report.

Explorations may seem intimidating at first, but they are incredibly powerful and where you can extract the most valuable insights from GA4.

When to Use It:

Use Explorations when you have a specific question that requires you to combine dimensions (like Page Title or Traffic Source) with your event metrics.

How to Build a Custom Event Report in Explore:

Let's walk through our example: finding which blog posts generate the most generate_lead events. We'll use the "Free form" exploration.

1. In the left-hand menu, click Explore and then click Blank new exploration.
2. Give your exploration a name at the top left, like "Blog Lead Generation."
3. Import Your Dimensions: In the "Variables" column, click the "+" next to DIMENSIONS. Search for and import "Event name" and "Page path and screen class."
4. Import Your Metrics: In the same "Variables" column, click the "+" next to METRICS. Search for and import "Event count."
5. Build the Report:
6. Filter for Your Event: Now, this is the key step. We only want to see the counts for our generate_lead event.

Your table will now update to show you a clean list of page paths (your blog posts) and the number of generate_lead events that specifically occurred on each one. You've just built a custom report that would have been impossible to create in the standard reporting interface!

Important Tips for Checking Events

Tip 1: Remember the Data Processing Lag

Except for the Realtime report, GA4 data isn't truly "live." It usually takes 24-48 hours for data to be fully processed and appear in your standard reports and explorations. If you just set up a new event, don't worry if it's not visible outside of the Realtime report on the first day.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Tip 2: You Must Configure Custom Definitions

A common point of frustration is sending custom parameters with an event but not being able to see them in your reports. For example, you might send a button_text parameter with a cta_click event. To use this as a dimension in your reports (like in an Exploration), you must register it as a custom dimension. You can do this in Admin > Data display > Custom definitions.

Tip 3: Use DebugView for In-Depth Testing

For more detailed, real-time event debugging, use the "DebugView" in GA4. Navigate to Admin > Data display > DebugView. You'll need to enable debug mode from your browser (most easily done using the "Google Analytics Debugger" Chrome extension). When active, you'll see a granular, second-by-second stream of all the events and parameters firing from your device. This is the absolute best way to troubleshoot your custom event setup before you launch it.

Final Thoughts

Checking your events in Google Analytics 4 gets much easier once you know where to look. Use the Realtime report for quick validation, the standard Engagement > Events report for general analysis, and Explorations for custom analysis to answer specific business questions about user behavior.

This process of manually checking events, drilling down into reports, and building custom explorations is a core part of a data analyst's workflow, but it can be time-consuming. We built Graphed because we believe getting answers from your data shouldn't require hours of navigating complex interfaces. Instead of manually building an exploration report, you can connect your GA4 account and simply ask, "What were my top signed-up blog posts?", and get an instant report. It allows you to skip straight to the insights and focus on strategy, not just report building.