How to Find Hits in Google Analytics

Ever heard the term 'hit' used in a Google Analytics discussion and found yourself nodding along, not entirely sure what it means? You're not alone. This article will explain exactly what a hit is, reveal the fundamental shift in how Google Analytics 4 handles them, and show you step-by-step where to find the data that hits represent.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What Exactly is a 'Hit' in Google Analytics?

First, let's clear up the definition. A "hit" is any single interaction on your website that sends a command to Google Analytics' servers. Think of each hit as a tiny data packet telling Google, "Hey, something just happened here!"

A Quick Trip Back to Universal Analytics (UA)

In the older version of Google Analytics (Universal Analytics, or UA), hits were everything. They were the most basic units of data collection and fell into a few main categories:

• Pageview hits: Fired every time a page loaded on your site. This is the most common type of hit.
• Event hits: Fired when a user did something specific, like clicking a button, watching a video, or submitting a form. You had to set these up manually.
• Transaction hits: Fired when a purchase was made, sending e-commerce data like revenue and products purchased.
• Social interaction hits: Fired when someone clicked a social button, like a "Tweet" or "Like" button on your site.

In the UA world, you could find a summary of hits in various reports, but the term itself was more of a behind-the-scenes building block for metrics like sessions and users.

So, Where Did Hits Go in GA4?

When Google Analytics 4 was introduced, it completely changed the data model. The core concept of "hits" - sending interaction data to Google - is still there, but the language and structure have evolved. Here’s the big change:

In GA4, everything is an event.

Where UA had different types of hits (pageviews, events, transactions), GA4 standardized it all. That pageview that used to be a "pageview hit"? It’s now an event called page_view. A button click that was an "event hit"? It's now simply a click event. Even a session starting is now a dedicated event, session_start.

This "event-based" model is more flexible and gives you a much richer view of what users are actually doing, not just which pages they are viewing.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Why You Don't "Find Hits" in GA4 Anymore

With this shift, the mentality of "finding hits" is outdated. You won't find a report in your GA4 dashboard simply called "Hits." That's because you're no longer looking for raw, undefined interactions. Instead, you're looking for specific, named events.

Your goal has shifted from asking "How many hits did my website get?" to asking more specific, valuable questions like:

• "How many page_view events did the blog post generate?"
• "How many users triggered the add_to_cart event?"
• "What's the count for our custom form_submission event?"

By focusing on events, you get a clearer, more actionable picture of user behavior. You are, in effect, looking at your hits — they're just neatly categorized and named now.

How to Find and Analyze What Your Hits Represent in GA4

Okay, so you're ready to find your events (the new hits). GA4 offers a few different places to see this interaction data, ranging from a live snapshot to a deep, technical view.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

1. Using the Realtime Report for Immediate Feedback

The Realtime report is your best friend when you want to confirm that tracking is working right now. It is the closest thing to watching hits come in as they happen.

How to use it:

1. On the left-hand navigation menu in GA4, go to Reports > Realtime.
2. Look for the card titled "Event count by Event name." This card shows you every event (hit) that has occurred on your site in the last 30 minutes.

This is incredibly useful for testing. For example, if you just launched a new "Download PDF" button, you can open your website, click the button, and watch for your file_download event to pop up in the Realtime report a few seconds later. It’s instant confirmation that Google is receiving the "hit."

2. Diving into the Engagement > Events Report

This is your home base for analyzing all user interactions over a specific time period. It offers a comprehensive view of every type of hit, all neatly organized as events.

How to use it:

1. Navigate to Reports > Engagement > Events.
2. You'll see a table listing all the events collected for the selected date range. Key columns include:

This report is where the magic happens. You can click on any event name in the list to drill down for more detail. For example, clicking on page_view will show you a dedicated report on which specific pages are receiving the most pageviews — a direct and powerful insight into your most popular content.

3. For the Power-User: The DebugView

If you really want to get under the hood and see every single data packet being sent from your browser to Google in real-time, DebugView is the tool for you. It's designed for testing and troubleshooting your tracking setup.

How to set it up:

1. First, you need a browser extension called the "Google Analytics Debugger." You can find it on the Chrome Web Store.
2. Once installed, navigate to your website and click the extension's icon in your toolbar to turn it ON.
3. In a separate tab, open your GA4 property and go to Admin > DebugView (you'll find it under "Data display").

You will now see a live, second-by-second stream of every single event and parameter coming from your browser. Each blue icon represents an event (a 'hit'), and clicking on it reveals all the granular detail associated with that interaction. It's the most literal way to "see your hits," making it perfect for verifying that custom events are set up correctly before you push them live.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Putting It All Together: From Hits to Insights

Understanding what hits are and where to find their GA4 equivalent (events) is just the first step. The real value comes from turning that data into business decisions.

Instead of just counting hits, start connecting them to user behavior:

• Look at your top page_view events: The pages with the most "page hits" are your most popular content. What are these pages about? Can you create more content like them or add a stronger call-to-action on these pages to capitalize on the traffic?
• Analyze click events: Which links and buttons are users clicking most often? This shows you what navigation items or calls-to-action are a priority for your audience.
• Compare add_to_cart and purchase events: Are a lot of people triggering the first event but not the second? You might have a problem with your checkout process that needs immediate attention.

Moving from a "hit counting" mindset to an "event analysis" mindset helps you see the story your data is telling about the user journey. That's how raw data transforms into actionable insights.

Final Thoughts

In short, the concept of a "hit" from classic analytics has simply evolved into a more powerful, flexible "event" model in GA4. By learning to navigate the Events and Realtime reports, you can get a clear view of every user interaction that matters, helping you understand your audience and optimize their experience.

We know that digging through menus and reports in Google Analytics can be tedious, taking valuable time away from actually making decisions. We built Graphed to remove this friction entirely. Instead of hunting for the right report, you can simply ask questions in plain English like, "Which were our top 10 most viewed pages last month?" or "Show me a chart of sign-ups vs. video plays over the last 90 days." Our AI instantly builds real-time dashboards and reports, saving you from the manual work of data wrangling.