What is a Hit Type Tracked by Google Analytics?

Ever wondered how Google Analytics knows someone visited your homepage, clicked a button, or bought a product? The answer is a simple but powerful concept called a "hit." Every piece of data in your Google Analytics reports starts as a hit - a single interaction sent to Google's servers. This article breaks down the different types of hits, explains the big changes from Universal Analytics to Google Analytics 4, and shows you why understanding them is crucial for accurate reporting.

Graphed

Still Building Reports Manually?

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

Watch the Demo

What Exactly is a Google Analytics Hit?

Think of hits as individual lines on a receipt for your website's activity. Each time a user interacts with your site in a specific way, a "line item" or hit gets sent to Google Analytics for processing. The browser essentially sends a tiny packet of information to Google's servers describing what just happened - for example, "this user just viewed this page," or "this user just clicked this video's play button." These individual hits are the raw building blocks of your entire GA reporting structure. Google Analytics aggregates these millions of tiny hits to calculate all the metrics and dimensions you see in your reports, like sessions, users, bounce rate, and conversion rates. Without hits, there would be no data to analyze.

Graphed

Still Building Reports Manually?

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

Watch the Demo

The Old School: Hit Types in Universal Analytics

If you used Google Analytics before 2023, you were using Universal Analytics (UA). In UA, hits were categorized into several distinct types, each designed to capture a different kind of interaction. While UA is no longer processing data, knowing these original categories helps understand the philosophy behind the new model in Google Analytics 4. The primary hit types in Universal Analytics were:

• Pageview Hit: The most common type. Sent every time someone loaded a page on your website.
• Event Hit: A more flexible hit used to track interactions that weren't a full page load, like clicking a button, downloading a PDF, or watching a video. Setting these up required manual configuration.
• Transaction Hit (or E-commerce Hit): Specifically used to track purchases, including data like Transaction ID, product SKUs, and revenue.
• Social Interaction Hit: Designed to measure clicks on social media buttons (e.g., a "Tweet this" or "Like on Facebook" button) on your site.
• User Timing Hit: Sent performance data to GA, allowing developers to measure page load speed and other technical timings from real users.
• Exception Hit: Used by developers to track errors or crashes happening in the browser. In the Universal Analytics model, each of these served a very specific purpose. You needed to choose the right hit type to track the right interaction. This system worked, but it could be rigid. That’s why GA4 changed everything.

The New Reality: How Google Analytics 4 Reimagined Hits

Google Analytics 4 simplified this entire structure with a bold declaration: everything is an event. Instead of having multiple distinct hit types like pageviews, events, and transactions, GA4 uses a flexible, event-based model. In this new world, a "pageview" is now simply a specific type of event fired named page_view. A "transaction" is now an event named purchase. This change might seem small, but it fundamentally redefines how you track user behavior. This new model means every single interaction - from loading a page to scrolling, clicking an outbound link, and completing a purchase - is captured as an "event" with a unique name. This gives you far more flexibility to track the user journey without getting stuck in predefined categories. Events in GA4 fall into four main categories, which build upon each other.

Graphed

Still Building Reports Manually?

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

Watch the Demo

1. Automatically Collected Events

Right out of the box, GA4 starts collecting certain events without you needing to do anything. Once the GA4 tracking code is on your site, these user interactions are tracked by default. Some of the most important automatically collected events include:

• session_start: Fires when a user begins a new session on your site or app. This forms the basis of the "Sessions" metric.
• first_visit: Fires the very first time a user visits your site. This helps GA4 calculate "New Users."
• user_engagement: Fires periodically when your webpage is in the foreground, helping GA4 determine if a session was "engaged."

2. Enhanced Measurement Events

This is where GA4 really starts to shine. Enhanced Measurement is a setting (on by default) that allows GA4 to automatically track several important interactions that used to require complicated manual setup in Universal Analytics. With a simple toggle switch, GA4 can track:

• scroll: Fires once per page when a user scrolls 90% of the way down. This is great for understanding if users are engaging with long-form content.
• click: Captures every click on an outbound link (a link that leads away from your current domain). Incredibly useful for tracking clicks to partner sites or affiliates.
• file_download: Fires automatically when a user clicks a link to a common file type like a PDF, DOCX, XLSX, or ZIP file. No more manual event tracking for content downloads!
• video_start, video_progress, video_complete: If you have embedded YouTube videos on your site, GA4 can track when users start, progress through (at 10%, 25%, 50%, and 75%), and finish watching them.
• view_search_results: Tracks when a user performs a search using your website's internal search function.

3. Recommended Events

Google provides a list of suggested event names for common scenarios across different industries (e.g., e-commerce, travel, gaming). While you could name your events whatever you want, using Google’s recommended names helps GA4 better understand your data and unlock more sophisticated reporting features.

For E-commerce and Retail:

• view_item_list: A user views a list of products (e.g., a category page).
• add_to_cart: A user adds an item to their shopping cart.
• begin_checkout: A user starts the checkout process.
• purchase: The most important one! A user completes a purchase. This replaces the old Universal Analytics "transaction" hit.

For Lead Generation or General Business:

• generate_lead: A user submits a form or a request for information.
• login: A user logs into their account.
• sign_up: A user signs up for a new account. You still have to set these up yourself (often using Google Tag Manager), but sticking to the standard naming convention is a best practice that will pay off later.

4. Custom Events

If none of the above event types cover an interaction you want to track, you can create your own custom events. This is where the power and flexibility of GA4's data model become fully apparent. You can create an event for virtually anything. Examples of valuable custom events include:

• completed_onboarding_step: For SaaS applications, tracking progress through a setup wizard.
• used_roi_calculator: For a B2B site, tracking engagement with a key sales tool.
• author_bio_expanded: For a blog, tracking how often readers interact with author information. With custom events, the only limit is what you decide is important to measure. You name the event and can pass along custom parameters to add more context to the interaction.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Why Understanding Hits and Events Matters

Knowing the difference between a pageview, a scroll event, and a purchase event isn't just a technical exercise. It's fundamental to getting reliable insights you can trust.

• It's the Foundation of Accuracy: Every report you create is built from these hits. If you don't track an important custom user action as an event, for all intents and purposes, it 'doesn't exist'. Google Analytics can't report on what it doesn't measure.
• It Empowers Better Goal Tracking: Once you go beyond pageviews and track key events like generate_lead or clicks on a specific call-to-action, you can set up those events as Conversions in GA4. This allows you to directly measure business objectives, not just website traffic.
• It Simplifies Debugging: Is your form submission data not showing up? Your first step should be to check if the generate_lead event hit is actually being sent to Google Analytics when the form is submitted. Using browser developer tools or Google Tag Manager's Preview Mode lets you see these hits in real-time.
• It Unlocks Deeper Analysis: By understanding that you can track almost any interaction, you can start answering more nuanced questions. You can track things like "How many users who scrolled to the bottom of the long blog post also clicked on the webinar CTA inside of the blog?" which provides much more context and color than you can ever get by answering a simpler question, like "how many people simply viewed that blog post URL".

Final Thoughts

At its core, every chart and number in Google Analytics traces back to a "hit" - a single interaction between a user and your website. While Universal Analytics used different categories for these hits, Google Analytics 4 has unified them all under an "event," creating a more powerful and flexible model for measuring what truly matters to your business. While understanding how to collect all this data is one thing, bringing it together to tell a coherent story is another. Often, important data from sources like Google Analytics, your ad platforms, and your CRM exists in different places, making it hard to see the full picture. Our goal with Graphed is to solve this. We seamlessly connect to all your marketing and sales data sources (including GA4), so you can instantly ask questions in plain English - like "Show me which campaigns from Facebook ads led to the most purchase events in GA4 last month" - and get a complete dashboard in seconds. This lets you focus on the insights, not on the manual work of piecing data together.