What Are the Four Score Types in Google Analytics?

Ever pull a report in Google Analytics and find the numbers don't quite add up the way you expect? You might see a total number of sessions that's different from the total when you break it down by a dimension like "Page." This isn't a bug, it's a feature called "scope." Understanding how scope works is the key to creating accurate reports and getting real insights from your data. This article will break down the four types of scope - Hit, Session, User, and Product - so you can build reports with confidence.

Graphed

Still Building Reports Manually?

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

Watch the Demo

First Things First: What Exactly is 'Scope' in Google Analytics?

In Google Analytics, "scope" defines the context for a piece of data. It tells you at what level a particular dimension or metric is collected and processed. Think of it like a set of Russian nesting dolls or different zoom levels on a camera.

At the very center, you have the smallest, most granular piece of data (the hit). That hit lives inside a larger container (the session), and that session belongs to an even bigger container (the user). Each level gives you a different perspective on your user's behavior.

Why does this matter? Because mixing and matching data from different scopes without understanding the rules can lead to misleading reports. For example, asking a user-level question with a hit-level dimension is like trying to find out your most loyal customer by looking at a single receipt. It just doesn't work. Once you grasp scope, your analysis becomes much more powerful and precise.

The Four Scopes in Google Analytics: A Breakdown

Google Analytics operates on four main scope levels. Let's break them down from the smallest piece of data to the biggest picture.

Graphed

Still Building Reports Manually?

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

Watch the Demo

1. Hit-Level Scope: The Smallest Piece of the Puzzle

A "hit" is the most fundamental interaction on your website that gets sent to Google Analytics. Every time something is tracked - a page loading, a button being clicked, a form being submitted - it's recorded as a single hit.

• What it is: Any individual piece of data sent to GA.
• Analogy: A single footstep someone takes inside a store. It's one specific action at one specific moment.
• Examples of hits:

If a person lands on your homepage, then clicks an "About Us" link, and finally plays an embedded video, that sequence just generated three separate hits: two pageviews and one event.

Common Hit-Level Dimensions & Metrics:

• Page Title
• Page Path
• Event Category / Action / Label
• Transaction ID
• Time on Page

You use hit-level scope to analyze what happens during those micro-moments. It's perfect for answering questions like, "Which call-to-action button on my landing page gets the most clicks?" or "How many people watched the product demo video?"

2. Session-Level Scope: The Visitor's Journey

A "session" is a container that groups all the hits from a single user during one visit to your site. It starts the moment a user arrives and ends when they leave, become inactive for 30 minutes, or at midnight.

• What it is: A single visit to your website, containing one or more hits.
• Analogy: The entire shopping trip. It includes every footstep (hit) a person takes, from walking through the door to checking out or leaving.
• Example: A user clicks a Google Ad, lands on your site, views three pages, downloads a PDF (an event hit), and then leaves. All of these interactions (a total of 5 hits) are grouped together into a single "session."

The vast majority of standard reports in Google Analytics are based on session-level scope. This is where you understand the performance of a visit as a whole.

Common Session-Level Dimensions & Metrics:

• Source / Medium
• Campaign
• Landing Page
• Device Category
• Goal Completions
• Bounce Rate
• Session Duration
• Pages per Session

Session-level scope is essential for acquisition analysis. It answers questions like, "Which traffic source brings the most engaged visitors?" or "Is my mobile traffic converting as well as my desktop traffic?"

Graphed

Still Building Reports Manually?

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

Watch the Demo

3. User-Level Scope: The Big-Picture View

The "user" scope is the broadest view. It groups together all sessions from the same person (or, more technically, the same browser identified by a cookie) over a set period. One user can have multiple sessions, which in turn have multiple hits.

• What it is: A unique browser or device that has visited your site multiple times.
• Analogy: The shopper themselves, not just their trip. This person might come to your store on Monday, Wednesday, and again on Saturday. The user scope tracks all those unique trips (sessions) and ties them back to the same individual.
• Example: Someone clicks a Facebook Ad on their laptop on Tuesday afternoon and browses a few pages (Session 1). On Friday morning, they get your email newsletter, click a link from their phone, and make a purchase (Session 2). Google Analytics attributes both sessions to the same user.

Common User-Level Dimensions & Metrics:

• Users
• New Users
• User Type (New vs. Returning)
• Days Since Last Session
• Demographics (Age, Gender)
• Customer Lifetime Value (LTV)

You use user-level scope to understand long-term customer behavior and audience characteristics. It's built for answering high-level questions like, "How many sessions does it take for a new user to convert?" or "What are the common traits of our most valuable customers?"

4. Product-Level Scope: All About a Single Item

This fourth scope is specific to sites using Enhanced Ecommerce tracking. It attaches data to individual products, independent of the hit or session it was part of.

• What it is: Information viewed or purchased on a product-by-product basis.
• Analogy: The price tag on an individual item in the store. It carries its own set of specific details (SKU, brand, category, price) that you want to track separately from a shopper's overall journey.
• Example: A visitor adds a "Blue T-Shirt - Medium" to their cart, views the page for a "Gray Hoodie - Large," and ultimately purchases only the blue t-shirt. With product-level scope, you can analyze each of these actions - the "add to cart," the "product detail view," and the "purchase" - for each specific product involved.

Common Product-Level Dimensions & Metrics:

• Product Name / SKU
• Product Category / Brand
• Product Revenue
• Quantity
• Unique Purchases
• Cart-to-Detail Rate

Product-level scope is critical for e-commerce performance analysis. It lets you answer questions like, "Which products are most frequently added to carts but not purchased?" or "Does showing Product A as a recommendation lead to more sales of Product B?"

Putting It All Together: Why Scope Matters in Your Reports

Understanding the theory is one thing, but the real test is applying it. Mismatched scopes are one of the most common sources of confusion when building custom reports in Google Analytics. The platform will let you combine scopes, but the resulting numbers can be easily misinterpreted.

Graphed

Still Building Reports Manually?

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

Watch the Demo

An Example of a Common Mistake

Imagine you want to see which pages are most important for your site's sessions. You create a custom report with:

• Dimension: Page (Hit Scoped)
• Metric: Sessions (Session Scoped)

GA will generate a report, but the Sessions metric in this context doesn't mean "sessions that started on this page." Instead, it means "the total number of sessions in which this page was viewed at least once." One session could include views of five different pages - that single session would then be counted for all five pages in your report.

If you wanted to see which pages started the most sessions, you should have used the session-scoped dimension Landing Page instead.

The golden rule is this: for the clearest, most intuitive reports, try to use dimensions and metrics that share the same scope. If you must mix them, pause and ask yourself exactly what question the resulting combination is answering.

Final Thoughts

Thinking in terms of Hits, Sessions, Users, and Products transforms your relationship with Google Analytics. You move beyond simply reading numbers and start to critically understand the context behind them, unlocking a new level of precision in how you measure performance and get real, actionable insights.

Building reports while keeping all the scope rules in mind can still feel complex, and it's easy to pull a metric that looks right but is subtly misleading. We built Graphed to remove this friction. Instead of worrying about mismatched scopes in a custom report builder, you can just ask in plain English "show me which campaigns last month drove the most users who made a purchase" and get a clear, correct dashboard instantly. We connect to tools like Google Analytics, your ad platforms, and CRM, handling the technical details so you can focus on the insights, not the setup.