GA4 users vs sessions: what each metric measures

In GA4, user metrics count unique identifiers that triggered events, while a session groups interactions during a visit. One measured user can start several sessions in the reporting period. Choose the metric based on whether you want to describe recorded visits or the users counted by the property.

Two identifiers and three sessions

Suppose a shop’s report shows two user identifiers over one week. Identifier A starts a session on Monday and another on Thursday. Identifier B starts one session on Wednesday. The summary is:

Those counts describe the data collected in this example. The identifiers do not guarantee the site recognised two real people across every device or browser. Reported identity depends on the identifiers available and the property’s setup.

What each GA4 metric means

Google defines a session as a group of interactions that take place within a time frame. It starts when someone opens an app or views a page or screen when no session is active. By default, GA4 ends a session after 30 minutes of inactivity, although that setting can be changed. Google’s Analytics sessions documentation explains the behavior.

In the official GA4 dimensions and metrics table, “total users” counts unique identifiers that triggered events. The “Users” metric shown in many reports refers to active users. Google defines active users using criteria that include an engaged session or activity signals collected by the property. Check the exact column name, especially when exporting data or comparing reports.

Pick the metric that matches the question

To describe how many visits were recorded, review sessions. To describe how many unique identifiers used the site, look for total users; when a report says “Users,” confirm whether it means active users. Do not swap these denominators when calculating another rate.

GA4 can also connect activity across sessions and devices when a property implements User-ID with its own persistent identifiers. Google explains that the business creates and assigns those IDs, and that reporting identity determines how they are combined with other identifiers. Without that implementation, someone using two browsers may appear under separate identifiers. Google’s User-ID documentation explains the scope and requirements.

Before comparing periods

Keep the period, applied filter, metric name and report identity setup with the result. A week with three sessions and two users in this example can produce a different combination when the period, configuration or Analytics identifiers change.

The difference between sessions and users does not tell you whether a visit was useful. Keep visit counts separate from metrics that describe engagement or outcomes.

The two identifiers and three sessions are a fictional teaching example. GA4 describes activity measured in a property; its count is not a perfect identification of people.

The cover is an AI-generated illustration.