Definition:

A visit is a set of interactions recorded during a continuous period of activity on a website or application. Digital analytics platforms generally represent it as a session, whose rules determine when it begins, when it ends, and which events it contains.

A visit does not necessarily correspond to one person. The same user may make several visits, use different devices, or not be recognised across periods. It is also different from a page view because one visit can include several pages, screens, and events.

Its duration and boundaries depend on the tool and its configuration. A 30-minute inactivity interval is a common default, not a universal definition of a visit.

Table of contents

1 How a Visit Is Measured
2 Differences from Other Metrics
3 Visits in Google Analytics 4

How a Visit Is Measured

Measurement groups observed activity through identifiers, events, and time-based rules. An implementation generally considers these six components:

Start: an interaction, such as opening a page or application, begins a visit when no other session is active.
Identifier: the tool assigns a session identifier to associate the events recorded during that period.
Activity: pages, screens, clicks, forms, and other events may be associated with the visit.
Inactivity: the session ends if the configured period passes without further interaction.
New visit: later activity may begin another session, even when it comes from the same browser or recognised user.
Processing: the platform applies its collection, identity, time-zone, and filtering rules before presenting the metric.

A visit represents the activity the tool was able to observe. A server request, page load, or isolated event does not necessarily constitute a separate visit.

Systems can also measure sessions in mobile applications, authenticated services, and experiences that do not reload complete documents. The technical definition should therefore be reviewed within the web analytics measurement plan being used.

Differences from Other Metrics

Interpretation requires separating units that answer different questions. These five distinctions are particularly relevant:

Visit or session: groups interactions that occur within a defined period.
User: represents a browser, device, account, or other identity recognised by the measurement method; it does not always correspond to one unique person.
Page or screen view: records that a page or screen was displayed and may occur several times within a visit.
Event: records a defined interaction or occurrence, such as a view, click, purchase, or error.
Engaged session: applies additional conditions to distinguish sessions that reach a specified duration, conversion, or number of views.

Counting visits helps describe volume and change, compare traffic sources, and study journeys. However, a variation does not by itself explain whether the number of people, their behaviour, or the measurement changed.

The classification of a returning visitor also depends on the system recognising the identifier at different times. Deleting cookies, changing devices, refusing tracking, or signing in may alter that classification.

Visits in Google Analytics 4

Google Analytics 4 uses the sessions metric. A session begins when a person opens an application in the foreground or views a page or screen and no session is active. The platform records a session_start event and generates parameters that identify the session and its number for the recognised user.

The Google Analytics documentation on sessions specifies a default timeout of 30 minutes of inactivity, which can be adjusted. This does not mean that every visit to any website lasts 30 minutes or that an active session ends when it reaches that duration.

Sessions can be analysed through metrics such as sessions, engaged sessions, average engagement time per session, and events per session. Interpretation should check at least these five aspects:

Configuration: session timeout, events, filters, and time zones applied.
Coverage: consent, blockers, tagging errors, and activity that is not collected.
Identity: devices, browsers, and accounts that may join or separate activity from the same person.
Attribution: rules that assign sources, media, or campaigns to sessions and their outcomes.
Continuity: implementation changes that may alter comparisons between periods.

Visits help describe recorded use, but they do not directly measure unique people, attention, satisfaction, or causality. Their usefulness depends on a stable definition, a verified implementation, and a comparison consistent with the question being analysed.