Session
A session is a group of interactions associated with a period of activity on a website or application.
Analytics platforms use sessions to group events into visits or periods of use.
What It Means in Practice
One session might include:
- Arriving on a landing page
- Reading an article
- Opening a service page
- Starting a contact form
- Leaving the website
Those individual events can be grouped together as one session.
A later visit may become another session.
How Sessions Work
Session rules depend on the analytics platform.
Systems may use inactivity timeouts, app state, identifiers, and other rules to determine when one session ends and another begins.
That means session counts are constructed measurements rather than natural units that exist independently of the analytics tool.
Why It Matters
Sessions are useful for understanding visits and journeys.
They can help answer questions such as:
- Which traffic sources bring visits?
- How often do visits become conversions?
- Which pages commonly begin a session?
- Which journeys involve several interactions?
They are usually more meaningful when combined with other metrics and dimensions.
Common Problems
Common session problems include:
- Treating sessions as people
- Comparing sessions between platforms with different rules
- Assuming a session represents focused attention
- Focusing on session volume without outcomes
- Ignoring how consent or implementation changes affect counts
How to Improve
Use sessions as one unit of analysis rather than a universal success metric.
Pair them with user, event, conversion, traffic-source, and engagement information to understand what actually happened during those visits.