A Browser RUM session is a collection of chronological events for a particular end user from the start of a session to a configurable period of inactivity. An event represents an activity occurring at the moment in time that can be recorded, aggregated, and correlated at certain levels. In Browser RUM, events are limited to page loads, virtual page loads, iFrames, and Ajax requests.

For example, when a user purchases product from an e-commerce site, the session might capture the page/virtual page loads, iFrames, or Ajax requests for the user logging in (start), selecting and paying for products, and logging out (end).

This figure describes how the user's actions cause events that are tracked in the session.

You can think of sessions as a time-based context to analyze a user's experience interacting with an application. By examining RUM sessions, you can understand how your applications are performing and how users are interacting with them. This enables you to better manage and improve your application, whether that means modifying the UI or optimizing performance.

In some use cases, you can use RUM sessions to analyze a user's or a group's behavior. You analyze a user's behavior based on the user's unique ID across multiple sessions in what is called sniping. In addition, you can query for a segment of users with similar behavior, such as visiting a certain specific page or using a particular device. This technique of grouping users with similar behavior is called bucketing. Browser RUM sessions allow you to query users on a wide array of criteria such as the type of browser, device, location, landing page, IP address, and more.

The JavaScript Agent loads a temporary GUID into the browser local storage and then transmits beacons to the EUM Cloud or EUM Server that include this GUID. We can then use the GUID to track the user's device over the duration of one or more sessions. The EUM Cloud then publishes these events into a session record stored in the Events Service.

セッションは、コントローラで設定したユーザの非アクティブ期間に到達するまで保持されます。また、GUID がローカルストレージから削除された場合もセッションを終了することができます。これには、いくつかの理由が考えられます。たとえば、ユーザがローカルストレージをクリアしたり、ブラウザを閉じたときにローカルストレージをクリアするようにブラウザを設定したりすることができます。

We do not perform browser or device fingerprinting. By default, we do not store user IP addresses. If you configure the Controller to store IP addresses, then the IP addresses are stored for up to 14 days.

As in Browser RUM Analyze, the main Sessions page is made up of two tabs:

• Records
• Charts