What is HIT in Google Analytics?

Every time a visitor does something on your website - whether it’s loading a page, playing a video, or buying a product - they send a tiny signal to Google Analytics. That signal is called a "hit," and it's the fundamental building block of all your website data. This article breaks down exactly what hits are, the different types you need to know, and why understanding them is essential for accurate reporting.

Graphed

Still Building Reports Manually?

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

Watch the Demo

What is a Google Analytics Hit? The Building Blocks of Your Data

Think of hits as the individual atoms that make up your analytics data. A single hit is a small, single-line request sent to Google's servers to record one interaction. On its own, a hit doesn’t tell you much. But when Google Analytics groups these hits together, they form a clear picture of user activity, creating the familiar metrics we all use, like Sessions and Users.

Each time the Google Analytics tracking code on your site is executed, it packages up information about the interaction - like the user's location, the device they're using, and the page they're on - and sends it off as a hit. Every metric and report you see in your GA dashboard starts with these individual data points.

The Different Types of Hits in Google Analytics

Not all interactions are the same, so Google Analytics uses several types of hits to categorize them. While there are a few technical types, the ones you’ll encounter most often are Pageview hits, Event hits, and E-commerce hits.

1. Pageview Hits

This is the most common and straightforward type of hit. A pageview hit is sent to Google Analytics every single time a page with the GA tracking code is loaded by a user. If a user lands on your homepage, that’s one pageview hit. If they then click to your "About Us" page, that’s a second pageview hit.

• When it's sent: Automatically upon page load.
• What it does: Forms the basis of metrics like Pageviews, Unique Pageviews, and calculates Bounce Rate.
• Example: A user reading this blog post generated a pageview hit when the page finished loading in their browser.

Graphed

Still Building Reports Manually?

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

Watch the Demo

2. Event Hits

Event hits are where analytics gets really powerful. Unlike pageviews, events track specific user interactions on a page that don't cause a new page to load. You have to set these up manually using Google Tag Manager or some custom code, but it's well worth the effort.

Things you can track with event hits include:

• Video plays (clicking the "play" button)
• File downloads (clicking a link to a PDF or spreadsheet)
• Form submissions (clicking the "submit" button on a contact form)
• Button clicks (any call-to-action button like "Sign Up Free Trial")
• Scroll depth (tracking when a user has scrolled 25%, 50%, or 75% down a page)

Every event hit is defined by a few key components you get to name yourself, which gives you complete control over how the data is organized in your reports:

• Event Category: The overarching group for the object the user interacted with. (Example: 'Video')
• Event Action: The specific action the user took. (Example: 'Play')
• Event Label (Optional): Provides additional detail about the event. (Example: 'Homepage Hero Video')
• Event Value (Optional): A numerical value associated with the event. (Example: The length of the video in seconds)

Using these together, you can see granular data on how people are actually engaging with your site's features, not just which pages they're viewing.

Setting up an Event Hit

If you were using Google Tag Manager to track a contact form submission, your resulting event hit sent to Google Analytics might be structured like this:

Category: "Form Submission" Action: "Contact" Label: "Contact Us Page"

3. E-commerce (or Transaction) Hits

This type of hit is essential for any business selling products online. An e-commerce, or transaction, hit is sent when a user completes a purchase. It contains a wealth of detail about the sale.

A single transaction hit can include information like:

• Transaction ID
• Store name
• Total transaction value (revenue)
• Tax, shipping, and handling costs
• Details about each product in the cart (name, SKU, price, quantity)

This hit empowers the E-commerce reports inside Google Analytics, allowing you to directly connect website traffic, marketing campaigns, and user behavior to actual revenue and product performance.

Graphed

Still Building Reports Manually?

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

Watch the Demo

From Individual Hits to the Big Picture: Sessions & Users

Google Analytics makes sense of individual hits by organizing them into a clear hierarchy: Hits > Sessions > Users.

When a user arrives on your site, the first hit they trigger (usually a pageview) starts a new session. Every subsequent hit they generate within a certain timeframe - clicking to new pages (pageview hits), playing a video (event hits), etc. - is grouped into that same session. Google Analytics can then calculate session-based metrics like Pages per Session and Average Session Duration.

How does a session end?

A session ends in one of three ways:

1. Time-based expiration: The most common way. The session ends after 30 minutes of inactivity. If a user leaves your site open in a tab but doesn't interact with it for 31 minutes, and then clicks to a new page, a new session will begin.
2. End of Day: All sessions are automatically reset at midnight based on the time zone of your reporting view.
3. Change in campaign source: If a user arrives on your site from a Facebook ad, browses a few pages, then returns to your site minutes later through a Google organic search link, a new session will be credited to Google.

Understanding this grouping is fundamental. Two users could each generate 10 hits, but one user might do it all in a single session, while the other does it across five different sessions over a week. These represent two very different patterns of engagement.

Why You Should Care About Hits: Practical Implications

Going beyond the basic definitions, a solid grasp of hits directly impacts the quality of your analysis and how you troubleshoot problems.

1. Getting Accurate Engagement Data

Out of the box, Google Analytics only fires pageview hits. This creates the classic problem of high bounce rates on blog posts. A "bounce" is technically a session with only one hit. A user can land on your blog, read an entire 2,000-word article, find it incredibly valuable, and leave - all without generating a second hit. This is recorded as a bounce, making it seem like your content is not engaging.

By adding a scroll-depth event hit (e.g., one that fires when a user scrolls 75% down the page), you create a session with two hits. This session is no longer a bounce, giving you a much more accurate reflection of true user engagement on your content pages.

2. Debugging Your Tracking Setup

If you've launched a new landing page and aren't seeing form submissions show up as goals in GA, the first question to ask is, "Is the event hit even firing?" Using tools like GA's Realtime report or the Google Tag Assistant Chrome extension, you can perform an action on your site and watch to see if the corresponding hit is sent to Google Analytics. If no hit is fired, you know the problem is with your tracking setup, not your landing page copy.

Graphed

Still Building Reports Manually?

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

Watch the Demo

3. Understanding GA Data Collection Limits

The free version of Google Analytics has a generous but finite processing limit: 10 million hits per tracking ID per month. For most small and medium-sized businesses, this is more than enough. However, for extremely high-traffic websites that also use many custom event hits, it’s possible to approach this limit. Understanding what constitutes a hit helps you track in a smart, efficient way, ensuring you only collect data that provides real value without sending unnecessary information.

Final Thoughts

In short, hits are the atomic interactions that Google builds your entire analytics masterpiece from. By understanding the core types - pageviews for browsing, events for engagement, and transactions for sales - you move beyond surface-level metrics and gain a deeper, more accurate understanding of how users truly behave on your website.

Manually tracking custom events and piecing together user journeys across tools like Google Analytics, Shopify, and your ad platforms can be a constant struggle. At Graphed, we eliminate that. By connecting your data sources into one place, we allow you to ask questions in plain English - no wrestling with custom reports required. Instead of spending hours investigating whether a specific button click is working, you can simply ask, "Show me which ad campaigns are driving the most PDF downloads," and get a real-time answer instantly. It transforms analytics from an archaeological dig into a simple conversation. With your data connected to Graphed, you can spend less time gathering data and more time acting on it.