What Kind of Hits Does Google Analytics Track?

Ever wondered what Google Analytics is actually doing when it "tracks" a user on your website? The answer comes down to one fundamental concept: the "hit." Understanding what a hit is, and the different types that exist, is the first step toward moving from simply looking at a dashboard to truly understanding your user behavior. This article will break down the different kinds of hits both in the older Universal Analytics and the current Google Analytics 4 so you can make sense of the data flowing into your reports.

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?

A "hit" is a specific interaction on your website that sends a piece of data to Google Analytics servers for processing. Think of each hit as a single ping or a single piece of information, like a digital breadcrumb a user leaves behind as they navigate your site. Each time a visitor loads a page, clicks a button, watches a video, or makes a purchase, a hit is sent. Google Analytics then collects and organizes these millions of individual hits into the familiar reports showing users, sessions, pageviews, and conversions.

How this works has changed significantly with the transition from Universal Analytics (UA) to Google Analytics 4. Let's look at both models, as you might run into UA data when looking at historical performance.

The Different Hit Types in Universal Analytics (UA)

Universal Analytics, the predecessor to GA4, had a more rigid structure with distinctly defined types of hits. While GA4 is the new standard, understanding this framework provides valuable context for how analytics measurement has evolved.

1. Pageview Hits

The most common and fundamental type of hit. A pageview hit is sent every single time a page with the Google Analytics tracking code on it loads in a user's browser. If a user visits your homepage, that's one pageview hit. If they then click to your "About Us" page, that sends a second pageview hit. This is the cornerstone of metrics like Pageviews and Unique Pageviews.

Graphed

Still Building Reports Manually?

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

Watch the Demo

2. Event Hits

What about interactions that don't cause a new page to load? That’s where event hits come in. These are custom-defined interactions that you tag manually to measure specific actions on a page. Examples include:

• Playing a video
• Clicking a "Download PDF" button
• Submitting a contact form
• Expanding an accordion section to read more

In Universal Analytics, events were structured with four main components: Category (e.g., 'Videos'), Action (e.g., 'Play'), Label (e.g., 'Homepage Promo Video'), and an optional Value (e.g., a numerical value). This required careful planning to set up and track properly.

3. E-commerce (Transaction) Hits

E-commerce-specific hits were a special category designed to capture purchase data. An e-commerce hit was typically sent on the "Thank You" or order confirmation page after a successful transaction. It included detailed information like:

• Transaction ID
• Total Revenue
• Product SKUs
• Prices
• Quantities
• Shipping costs and taxes

This allows for robust e-commerce reporting, showing you which products are selling best and the revenue generated from your site.

4. Screenview Hits

This is simply the mobile app equivalent of a pageview hit. When a user views a specific screen within your mobile application, a screenview hit is sent to GA. In reports, you would see "Screen Views" instead of "Pageviews."

5. Other, Less Common Hit Types

Universal Analytics also had a few other, more specialized hits:

• Social Interaction Hits: Used to track clicks on social sharing buttons like a Facebook "Like" or a Twitter "Share" button embedded on your site.
• User Timing Hits: Allowed developers to measure the speed of specific elements on a page, such as how long a form takes to submit or how fast a specific image loads.
• Exception Hits: Used for technical debugging to track errors or crashes occurring on the site or in an app.

In the UA model, you had to consciously decide which type of hit was appropriate for the interaction you wanted to measure. This has been totally revamped in GA4.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Everything is an Event: The Hit Model in Google Analytics 4

The biggest change in GA4 is its "event-based" data model. Forget the rigid categories of pageviews, events, and transactions. In GA4, every hit is considered an event. A pageview is now just an event named page_view. A purchase is an event named purchase. This simplifies the entire framework and makes it far more flexible.

GA4 organizes its events into four distinct categories.

1. Automatically Collected Events

As soon as you install the GA4 tracking tag on your website, Google starts tracking a set of default events without you needing to do anything. These provide a solid baseline of user activity right out of the box. Key examples include:

• session_start: Sent whenever a user begins a new session.
• first_visit: Tracks a user's very first visit to your website.
• user_engagement: Fired periodically when a user is actively engaged with your site (e.g., your site is the active window on their screen).

2. Enhanced Measurement Events

This is one of GA4's most powerful features. With a simple toggle in your settings, you can automatically enable tracking for a list of common website interactions that used to require custom code. No Google Tag Manager required! These include:

• page_view: The classic pageview hit, but now an event.
• scroll: Fired when a user scrolls 90% of the way down a page. Great for measuring content engagement on long-form blog posts or landing pages.
• click: Tracks outbound clicks to other domains. Perfect for seeing how many users click on your partner links.
• view_search_results: Tracks when a user performs a search on your internal site search.
• video_engagement: Captures video plays, progress, and completions for embedded YouTube videos.
• file_download: Automatically logs an event when a user clicks a link to a common file type like a PDF, DOCX, or CSV.
• form_interaction: Tracks a user starting to fill out a form and submitting it.

3. Recommended Events

Google provides a list of "recommended" event names for common business scenarios across various industries (like e-commerce, travel, and gaming). While they function just like custom events, following Google's naming conventions can help ensure your reports are standardized. Examples include:

• E-commerce: add_to_cart, begin_checkout, purchase
• General: login, sign_up, share

You still need to implement the code to fire these events, but Google gives you the blueprint for what to call them.

4. Custom Events

If an interaction you want to track doesn't fit into any of the above categories, you can create your own custom event. This gives you ultimate flexibility. For example, you could create custom events to track:

• pricing_calculator_use: Fires when a user interacts with a pricing tool.
• newsletter_modal_dismiss: Tracks who closes your pop-up instead of signing up.
• comment_submit: Logs when users leave a comment on a blog post.

You can name these whatever you want (within certain limits) and associate them with custom parameters to capture extra context about the interaction.

Graphed

Still Building Reports Manually?

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

Watch the Demo

How Hits Become Meaningful Reports

So, why does any of this matter? Because Google Analytics isn't just a bucket for millions of individual hits. Its job is to process these raw interactions and organize them into meaningful data points.

Hits are grouped into sessions (a user's visit to your site), which are then associated with a specific user. These are then aggregated into the metrics you see in your reports - like Sessions, Users, Engagement Rate, and Conversions. The supplementary data sent with each hit, like the browser, device type, or traffic source, becomes the dimensions that allow you to slice and dice your data.

Understanding the fundamental "hit" building block gives you a massive advantage when analyzing your data. You can more accurately diagnose why metrics look the way they do and can more confidently set up tracking to measure the interactions that truly matter for your business goals.

Final Thoughts

In short, a "hit" is the basic unit of data in Google Analytics, representing every interaction from loading a page to completing a purchase. While Universal Analytics had distinct hit types, GA4 unified this process into one flexible, event-based model, giving you more power to measure what users are really doing on your site.

Understanding these concepts is the first step, but the real challenge for marketers and founders is often connecting this data to the rest of your tools. A user’s journey doesn’t just happen on your website, it starts with an ad click, continues through your site, and might end in your CRM or e-commerce platform. Instead of spending hours pulling reports from a dozen different places, we built tools to simplify that. With Graphed you can connect your Google Analytics, ad platforms, Shopify, and CRM in seconds. From there, you just ask our AI data-analyst in plain English to build the dashboards you need, giving you a complete, real-time view of your performance without any of the manual work.