What are Hits in Google Analytics?

Thinking about Google Analytics data means imagining charts of traffic, rows of user data, and conversion funnels, but all of this information starts from a single, simple concept: a "hit." A hit is the most basic building block of data in Google Analytics, representing a single interaction from a user. This article breaks down exactly what hits are, the different types you'll encounter, and why knowing about them helps you better understand your website's performance.

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?

In the simplest terms, a hit is any interaction that sends information to Google Analytics' servers. Think of it as a small message, or a "ping," sent from a user's browser to tell Google Analytics, "Hey, something just happened here!"

Every time a user loads a page, clicks a button you're tracking, watches an embedded video, or makes a purchase, their browser sends one of these data packets to Google. This packet includes information about the interaction, such as what happened, when it happened, and basic details about the user (like their browser type and the page they were on). All the reports you see in your Google Analytics dashboard are built by collecting, organizing, and analyzing millions of these individual hits.

In the past, with Universal Analytics, hits were strictly divided into several specific types. However, Google Analytics 4 has fundamentally simplified this model. Today, nearly every interaction is considered a type of "event." Understanding this shift from the older hit model to the new event-driven model is crucial for working effectively with GA4.

Graphed

Still Building Reports Manually?

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

Watch the Demo

The Different Types of Hits, Redefined in GA4

GA4 consolidated the old, rigid hit types into a flexible, event-based system. While the underlying "ping" still happens for each interaction, they are now all classified as different kinds of events. Here’s a breakdown of how the classic types of hits have evolved in Google Analytics 4.

1. Page View Hits (Now the 'page_view' Event)

This is the most common type of interaction you'll track. A page view hit is sent to Google Analytics every time a page on your website is loaded by a user's browser.

• What it is: A user navigating to a page on your site. For example, when someone lands on your homepage, a /blog/my-post page, or your /contact page.
• How it works in GA4: This is an automatically collected event called page_view. As long as the GA4 tracking code is on your website, you don't have to do anything to start collecting page view data. It just works.

2. Event Hits (Now Simply 'Events')

In Universal Analytics, an "event hit" was used for tracking custom interactions that weren't page views - like a form submission, a file download, or a video play. In GA4, this concept was expanded to cover nearly everything.

An event lets you measure a distinct user interaction. There are a few different categories of events in GA4:

• Automatically Collected Events: These are events GA4 tracks for you with no setup required. Examples include session_start (when a user starts a new visit), first_visit (the first time a user ever visits your site), and user_engagement (when the user has your site open and active for a certain duration).
• Enhanced Measurement Events: These are common interactions that you can enable with a single toggle in your GA4 settings. This includes helpful events like scroll (when a user scrolls 90% of the way down a page), file_download, and video events such as video_start and video_complete.
• Recommended Events: Google provides a list of recommended events for different business types (like e-commerce or gaming) that you can implement. These have predefined names and parameters. For example, a marketer might implement the generate_lead event when a user submits a contact form or the sign_up event when someone creates an account.
• Custom Events: If none of the above fit your needs, you can create a completely custom event. You can name it whatever you want and send whatever data is relevant. For example, you could create an event called quote_tool_used to track engagement with an interactive pricing tool on your site.

3. E-commerce Hits (Reimagined as E-commerce Events)

These hits are specifically for tracking user interactions throughout the shopping funnel. From viewing a product to completing a purchase, these actions are vital for any online store looking to understand customer behavior.

In GA4, these are a specific type of recommended event. You implement them with predefined names to get rich e-commerce reports. Key examples include:

• view_item_list: When a user sees a list of products (e.g., on a category page).
• add_to_cart: When a user adds an item to their shopping cart.
• begin_checkout: When a user starts the checkout process.
• purchase: The all-important event when an order is completed.

Just like any other events, these can be viewed in GA4 reports to see which products are most popular, where users are dropping off in the funnel, and which marketing channels drive the most revenue.

Graphed

Still Building Reports Manually?

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

Watch the Demo

From Hits to Sessions: How the Data Adds Up

Understanding the concept of a hit (or an event in GA4) is essential because it’s the foundation for all other metrics, like sessions and users.

1. A User is the individual person visiting your website, often identified by a client ID stored in a cookie.
2. A Session is a single visit by that user. A session begins when a user arrives and ends after a period of inactivity (typically 30 minutes).
3. Hits (Events) are the individual actions that a user takes within that session.

Here’s a practical example of a visitor's journey and the hits it would generate:

1. 2:30 PM: A user clicks a link from a search result and lands on your homepage.
2. 2:31 PM: They scroll down the page and click to watch an embedded video.
3. 2:33 PM: After watching, they navigate to your "Products" page.
4. 2:35 PM: They click "Add to Cart" on a product.
5. 2:36 PM: They get distracted and leave your website. The browser tab remains open, but they don't interact with it.
6. 3:06 PM: Because 30 minutes have passed with no new hits, Google Analytics ends the session.

One user, one session, but seven different hits (events) recorded a detailed story of their brief visit.

Why Understanding Hits Still Matters

Even though GA4 simplifies everything into an "event" model, the term "hit" and its core concept are still important for a few key reasons, especially when trying to troubleshoot or think strategically about your analytics.

Debugging and Data Accuracy

If you're not seeing the data you expect in your reports - maybe sign-ups aren’t being recorded or a campaign isn’t getting credit for conversions - the problem almost always comes down to a missing or improperly configured hit. Is the event actually being sent to Google Analytics when the user clicks the "Submit" button? Tools like GA4's own 'DebugView' are designed specifically for this, allowing you to watch the actual stream of hits from your browser in real-time. This helps you confirm your tracking is working correctly.

Planning Your Analytics Strategy

Knowing that every user action can be tracked as a hit forces you to think about what is truly important for your business. You shouldn't try to track every single click on everything, as it will just create noise. Instead, identify the key user interactions that align with your business goals. Should you track when a user expands a specific 'show details' button? Or is it more useful to track when they complete an ROI calculator? Realizing each of these can be a hit helps you plan a meaningful measurement strategy.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Understanding Data Limitations

While most websites never have to worry about this, Google Analytics does have processing limits. Knowing that a large number of very specific custom hits contribute to these limits can be important for extremely high-traffic websites or apps. For example, the free version of GA4 properties has a limit of 500 distinctly named custom events. This prevents you from creating infinitely different hits, prompting a more thoughtful approach to tracking.

Final Thoughts

At its heart, a hit is simply a record of an interaction between a user and your website. While Google Analytics 4 has renamed most hits as "events," understanding the original concept is fundamental to grasping how all your marketing data is collected, processed, and presented back to you in useful reports. It’s what transforms raw clickstream data into meaningful business insights.

Getting a handle on all the events firing across your website, not to mention your other marketing platforms, is a lot to manage. That's why we built Graphed to help connect all your data sources like Google Analytics, Shopify, and social ad platforms in one place. Instead of sorting through different reports and event names, we enable you to just ask for what you need in plain English. For example, you can simply ask, "Show me how my blog traffic from last week compares to the week before," and instantly get a chart without having to manually build it. Graphed lets your team focus on analyzing performance instead of getting stuck on how the data gets reported, and you can create live dashboards that answer your most important business questions in seconds.