
Reporting Identity in GA4
Learn more about Reporting Identity in GA4 and how you can use it.
If you’re staring at your Google Analytics 4 reports trying to figure out the difference between ‘views’ and ‘sessions’.
Don’t worry. You are absolutely not alone. It’s one of the most common questions I get from clients.
Let’s be honest, the shift from Universal Analytics (UA) to GA4 changed more than just the interface; it fundamentally changed how we measure and define core interactions.
But here’s the good news: the distinction is actually quite simple once you break it down. Understanding it is the key to unlocking accurate, actionable insights from your data.
So, let’s clear this up for good.
In short, a view is the total number of website pages or mobile app screens your users saw.
It’s a simple tally. If a user lands on your homepage, clicks to your ‘Services’ page, and then clicks back to the homepage, that counts as three views.
It includes repeat views of the same page by the same user within their visit.
Technically, GA4 is counting every time the page_view event is triggered.
The Big UA Difference: If you’re a UA veteran, you’ll know this metric as ‘Pageviews’. The main difference is that ‘Views’ in GA4 combines traditional website pageviews with mobile app screen views, giving you a unified total across your digital properties.
Metrics you’ll see built from this include Views per user and Views per session.
A session is different. It’s not a single action but a period of time during which a user interacts with your website or app.
Think of it as the container that holds all the user’s actions (like views, clicks, and conversions) for a single visit.
A session starts when a user lands on your site or opens your app.
It ends after a period of inactivity—by default, GA4 sets this at 30 minutes.
If that user leaves and comes back 10 minutes later, they’re still in the same session. If they come back three hours later, a new session will start.
Technically, GA4 records a session_start event. From this, you get some of your most important metrics, like Engaged sessions, Average session duration, and Session conversion rate.
Okay, so they’re different definitions. So what?
Understanding the difference is crucial because it tells you two very different things about user behaviour.
Views tell you about content popularity. A page with many views is getting a lot of eyeballs, either from new users or repeat visitors.
Sessions tell you about traffic and engagement. A high number of sessions means people are visiting your site frequently. ‘Engaged sessions’ tells you how many of “those visits were actually meaningful.
A single session can, and should, contain multiple views. Analysing the relationship between them is where the real strategy comes from.
High Views per Session: This is generally a good sign! It means users are engaged, browsing multiple pages, and digging deeper into your site during their visit.
Low Views per Session (e.g., close to 1): This could mean users are finding what they need instantly (good for a contact page), or they’re landing on your page and ‘bouncing’ straight off (bad for a blog post).
A Quick Troubleshooting Tip: Your ‘Views’ count should almost always be higher than your ‘Sessions’ count (since one session can have many views). If you’re ever analysing a report and your number of sessions is higher than your views, it’s a massive red flag. This can point to an issue with how your tracking code is set up, so it’s worth investigating immediately.
Let’s boil it all down to the simplest definitions:
Views: The total number of pages and screens seen.
Session: The single visit or period of activity that contains those views.
By understanding this difference, you can move beyond simple traffic counting and start analysing user behaviour with much more confidence. You can now accurately report on whether your content is just attracting users (sessions) or actually engaging them (views per session).
Can one session have multiple views?
Yes, absolutely. In fact, that’s usually the goal. A single user (one session) who lands on your homepage, then clicks to your ‘About’ page, and finally visits your ‘Contact’ page has generated 1 session and 3 views.
What is a “good” views per session rate?
This depends entirely on your website. For a blog, you might want a high views-per-session (2-3+) as it shows people are reading multiple articles. For a simple landing page, you might expect it to be low (1-2) as the user’s goal is to sign up or get information quickly, not browse.
How do I change the 30-minute session timeout in GA4?
You can adjust this in your GA4 property settings. Go to Admin > Data Streams > [Select your stream] > Configure tag settings > Show all > Adjust session timeout. You can set it to be shorter or much longer (up to 7 hours and 55 minutes).

Learn more about Reporting Identity in GA4 and how you can use it.

Learn how to use GA4 content groups to get smarter, high-level insights from your analytics.
Author
Hello, I'm Kyle Rushton McGregor!
I’m an experienced GA4 Specialist with a demonstrated history of working with Google Tag Manager and Looker Studio. I’m an international speaker who has trained 1000s of people on all things analytics.