Website Hits in Google Analytics: What the Numbers Are Telling You

Website hits in Google Analytics refer to the interactions your site sends to GA’s servers, including pageviews, events, transactions, and session data. In GA4, the older concept of “hits” has been replaced by an event-based model where every interaction, from a page load to a button click, is recorded as an event. Understanding what these numbers mean, and more importantly what they don’t mean, is the difference between useful measurement and expensive noise.

Most marketers look at traffic volume first. It’s the number that’s easiest to report and hardest to argue with. But volume without context is close to meaningless, and I’ve seen too many agency reviews where a rising sessions chart was used to mask a conversion rate that was quietly falling apart.

What Does “Website Hits” Actually Mean in Google Analytics?

The term “hits” comes from Universal Analytics, Google’s previous measurement platform. In that model, a hit was any interaction sent to Google’s collection servers: a pageview hit, an event hit, a transaction hit, a social interaction hit. Each time something happened on your site, a hit was fired. Your total hit count was effectively a measure of how much data your property was generating.

GA4 retired this language. Everything is now an event. A pageview is an event called page_view. A scroll is an event called scroll. A purchase is an event called purchase. The underlying principle is the same, but the architecture is more flexible because you’re no longer constrained by hit types. You can define and track almost any interaction as a custom event.

When people search for “website hits Google Analytics,” they’re usually asking one of three things: how much traffic is their site getting, how do they interpret the numbers they’re seeing, or how do they set up tracking correctly in the first place. This article covers all three, because they’re connected. If you haven’t set GA4 up properly, the numbers you’re interpreting aren’t reliable, and any conclusions you draw from them are built on shaky ground.

If you want a broader foundation for making sense of your analytics stack, the Marketing Analytics and GA4 hub covers the full landscape from setup to reporting to commercial application.

How GA4 Measures Traffic: The Event Model Explained

GA4 collects data through four categories of events. Automatically collected events fire without any configuration: page_view, session_start, first_visit. Enhanced measurement events are enabled through the GA4 interface and cover scrolls, outbound clicks, site search, video engagement, and file downloads. Recommended events follow Google’s naming conventions for specific industries, particularly ecommerce. Custom events are anything you define yourself.

The practical implication is that a freshly installed GA4 property is not fully configured. It’s collecting basic data, but it’s missing the events that matter most for commercial decisions. If you’re running an ecommerce site and you haven’t implemented the recommended ecommerce events, you have no purchase data, no add-to-cart data, and no checkout funnel data. You have sessions and pageviews, which tells you people visited, not what they did.

Getting the setup right from the start matters more than most people realise. The Semrush guide to setting up Google Analytics is a solid reference if you’re working through an implementation or auditing an existing property. It’s worth doing the audit before you start building reports, because reports built on incomplete data tend to produce confident-sounding conclusions that are simply wrong.

Early in my career, I inherited a GA setup that had been running for two years. The client had been reporting monthly on traffic growth and was pleased with the trend. When I looked at the raw data, I found that the tracking code had been duplicated across most pages, which meant every pageview was being counted twice. The “growth” was real in the data. It was not real in the world. That experience made me treat inherited analytics setups with a healthy scepticism I’ve never lost.

Sessions, Users, and Pageviews: What Each Metric Is Telling You

These three metrics are the ones most people look at first, and they’re the ones most often misread.

A session is a group of interactions on your site within a given time frame. GA4 defines a session as ending after 30 minutes of inactivity, or at midnight. One user can generate multiple sessions. Sessions give you a measure of visit frequency, not just audience size.

Users in GA4 are counted as either total users or active users. Active users, which is the default metric in most GA4 reports, counts users who had an engaged session, triggered a conversion event, or had a first_visit event. This is a more meaningful number than total users because it filters out immediately-bounced visits, but it also means your “users” number in GA4 will look lower than it did in Universal Analytics. If you’re comparing year-on-year data across the platform migration, the numbers are not directly comparable.

Pageviews count how many times a page was loaded or reloaded. A single user who visits five pages generates five pageviews in one session. High pageviews relative to sessions can indicate good content engagement. It can also indicate that people are struggling to find what they’re looking for. Context determines which interpretation is correct, and you need additional data to know which one applies.

The metric GA4 introduced that Universal Analytics didn’t have is engagement rate: the percentage of sessions that were “engaged,” meaning they lasted longer than 10 seconds, had a conversion event, or had two or more pageviews. This replaced bounce rate as the primary quality signal. It’s a better metric because it measures something positive rather than the absence of something, but like any aggregate, it can mask significant variation by traffic source or landing page.

Why Traffic Source Is the First Segmentation You Should Apply

Aggregate traffic data is almost never actionable. The moment you look at total sessions without segmenting by source, you’re averaging together audiences with very different intent, behaviour, and commercial value. That average tells you very little.

GA4 organises traffic into default channel groups: organic search, direct, referral, paid search, organic social, paid social, email, and others. Each of these represents a different acquisition context. Organic search visitors arrived because they searched for something and found you. Direct visitors typed your URL or came through an untracked source. Paid visitors came because you paid for their click. These are not the same audience and should not be treated as one.

When I was managing paid search at scale, one of the most common errors I saw clients make was celebrating overall traffic growth while paid traffic was quietly subsidising a decline in organic. The total line looked healthy. The underlying mix was deteriorating. You only see that when you segment.

UTM parameters are the mechanism that makes source-level analysis reliable for campaigns. Without them, traffic from email newsletters, social posts, and third-party placements often lands in the “direct” bucket, which makes direct look larger than it is and makes your campaign channels look smaller. Proper UTM tagging is one of the highest-leverage configuration tasks in any GA4 setup. The Semrush guide to UTM tracking codes is a practical reference for building a consistent tagging convention across your team.

How to Read Traffic Data Without Being Misled By It

GA4 gives you a lot of numbers. The discipline is knowing which ones are worth your attention and which ones are producing the illusion of insight.

A few principles I’ve applied consistently over the years:

Look at trends, not snapshots. A single week’s data is almost never meaningful. Seasonality, algorithm updates, campaign timing, and technical issues all create short-term fluctuations that can look significant but aren’t. Compare against the same period in the prior year where possible, and always have at least 90 days of context before drawing conclusions about a trend.

Connect traffic to outcomes. Sessions and pageviews are input metrics. Conversions, revenue, leads, and goal completions are output metrics. If your traffic is growing but your conversions aren’t, the traffic quality has declined, the landing experience has degraded, or your offer has become less competitive. All three are worth investigating. None of them are visible if you only look at traffic volume.

Treat direct traffic with suspicion. A large direct traffic number usually contains a mix of genuine brand-driven visits, dark social traffic from messaging apps and newsletters, and untagged campaign traffic. It’s not a clean signal. If your direct traffic is more than 20-25% of total sessions and you haven’t done a UTM audit recently, it’s worth doing one.

Check for data anomalies before reporting. Bot traffic, spam referrals, and internal traffic from your own team can all inflate your numbers. GA4 has improved its bot filtering compared to Universal Analytics, but it’s not perfect. If you see a sudden spike in sessions from an unusual source with a 100% engagement rate or a 0% engagement rate, investigate before you report it as real traffic.

Building a clean, focused dashboard helps enforce this discipline. The Crazy Egg guide to building a Google Analytics dashboard covers the practical mechanics of surfacing the metrics that matter without drowning in the ones that don’t.

What GA4 Doesn’t Tell You (And What Fills the Gap)

Google Analytics is a quantitative tool. It tells you what happened: how many people visited, which pages they viewed, where they came from, and whether they converted. It does not tell you why they behaved the way they did, what stopped them from converting, or what they were trying to accomplish when they arrived.

That gap matters. I’ve sat in enough post-campaign reviews to know that the most dangerous question in analytics is “why did conversion rate drop?” because GA4 alone cannot answer it. You can see that it dropped. You can see which pages or segments it dropped on. But the reason requires qualitative data: session recordings, heatmaps, user feedback, on-site surveys.

Tools like Hotjar sit alongside GA4 precisely to fill this gap. Hotjar’s own framing of how it complements Google Analytics is worth reading if you’re building out a measurement stack. The short version: GA4 tells you where the problem is, session recording tools help you understand what’s causing it.

For sites with significant video content, GA4’s native video tracking has limitations. Wistia’s GA4 integration is one approach to getting richer video engagement data into your analytics property, particularly useful if video is a meaningful part of your conversion path.

There’s also a broader point here about data literacy. Analytics tools are a perspective on reality, not reality itself. The numbers reflect what the tracking captured, filtered through Google’s processing, subject to sampling at scale, and shaped by how the property was configured. That’s not a reason to distrust them. It’s a reason to hold them with appropriate confidence rather than treating them as ground truth.

I spent time judging the Effie Awards, which evaluate marketing effectiveness. One of the consistent patterns in the strongest entries was that the teams behind them understood the limits of their measurement. They didn’t overclaim from their data. They triangulated across multiple sources and were honest about what they could and couldn’t prove. That intellectual honesty tends to produce better decisions than false precision.

Setting Up GA4 to Capture Meaningful Data

A GA4 property that’s been installed but not configured is like a speedometer with no calibration. It shows a number, but you can’t trust what it represents.

The configuration steps that make the most difference in practice:

Define and mark conversions. GA4 doesn’t automatically know what a conversion is for your business. You need to identify the events that represent meaningful outcomes, form submissions, purchases, account signups, phone call clicks, and mark them as conversions in the GA4 interface. Without this, you have traffic data but no outcome data.

Filter internal traffic. If your team is regularly on your site, their sessions will inflate your traffic numbers and distort your engagement metrics. Set up an internal traffic filter using your office IP addresses and exclude it from your reporting views.

Link GA4 to Google Search Console. This integration brings organic search query data into GA4, so you can see which search terms are driving traffic to which pages. It’s one of the highest-value free integrations available and it’s frequently overlooked.

Enable enhanced measurement selectively. GA4’s enhanced measurement is on by default and collects scroll depth, outbound clicks, site search, and more. Review what’s enabled and make sure it aligns with your measurement needs. In some cases, the automatic scroll tracking fires too aggressively and inflates engagement metrics in ways that aren’t meaningful.

Implement a consistent UTM convention. Agree on naming conventions for source, medium, and campaign parameters across your team and enforce them. Inconsistent UTM tagging, where one campaign uses “Email” and another uses “email” and another uses “e-mail,” fragments your channel data and makes source analysis unreliable.

When I grew the agency team from around 20 people to close to 100, one of the persistent challenges was maintaining data hygiene across a larger group of people with different levels of analytics experience. The answer wasn’t more tools. It was clearer conventions, documented processes, and someone accountable for the integrity of the data. The same principle applies whether you’re a team of three or a team of 300.

Turning Traffic Data Into Commercial Decisions

Traffic data becomes commercially useful when it informs decisions about where to invest, what to fix, and what to stop doing. That requires connecting the data to business outcomes, not just reporting the numbers.

A practical framework I’ve used across a range of clients: look at each traffic source in terms of volume, engagement quality, and conversion rate. A source that drives high volume but low engagement and near-zero conversions is not a good source, regardless of how the volume looks on a chart. A source that drives modest volume but strong engagement and a healthy conversion rate is worth investing in, even if it doesn’t look impressive in a headline sessions report.

This kind of analysis is where analytics starts to drive real commercial decisions. At lastminute.com, the early paid search work I was involved in was effective precisely because the team was willing to look at revenue per click rather than just click volume. When you’re measuring the right output, you make very different decisions about where to put budget.

Landing page performance is another area where traffic data becomes actionable. If a specific landing page is receiving significant traffic from paid campaigns but converting at a fraction of your site average, that’s a clear signal that the page experience is misaligned with the ad creative or the audience intent. GA4 can show you the gap. Fixing it requires understanding what’s happening on the page, which brings you back to the qualitative layer.

For a deeper look at how analytics fits into the broader measurement picture, the Marketing Analytics and GA4 hub covers everything from attribution to reporting frameworks to the commercial application of data.

The BCG research on data and analytics in financial services makes a point that applies well beyond that sector: the organisations that extract the most value from data are not necessarily the ones with the most data. They’re the ones with the clearest questions and the discipline to answer them rigorously. That BCG analysis on data-driven transformation is worth reading for the framing, even if your context is very different from financial services.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions