> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Salesforce Browser Monitoring Data

> What the Salesforce UX Monitoring Profile captures in each user's browser, and the KPI where you find each type of data.

Components
[`RUM Extension`](https://docs.germainux.com/deploy/germain-ux-rum-extension)
[`RUM JS`](https://docs.germainux.com/deploy/germain-ux-rum-js)

Service
`Analytics`

Availability
2017.1 or later

> [card] [Users, Sessions and Context](#users-sessions-and-context)
>
> Identity, session, app and page

> [card] [What the Profile Captures](#what-the-profile-captures)
>
> Capability, KPI and fields

> [card] [Names and Paths](#page-names-and-paths)
>
> How IDs are grouped

> [card] [Session End](#session-end)
>
> Logout ends the session

## Overview

The **Salesforce** UX Monitoring Profile goes beyond generic browser monitoring. It understands Salesforce Lightning and Classic: Aura requests, record pages, console tabs, toasts, Chatter and Omni-Channel. It turns them into named, searchable data.

Use this page as a reference when you build a dashboard, an SLA or an alert on Salesforce user data. It answers questions such as:

* Which KPI holds Salesforce errors shown to users?
* Where do I find the Apex class behind a failed request?
* How do I link a browser request to Salesforce server logs?
* Which KPI measures how long users take to create a record?

The profile collects this data with RUM JS or the RUM Extension. See [Deploy Monitoring for Salesforce](https://docs.germainux.com/integrations/salesforce-monitoring/salesforce-monitoring-deployment.md).

## Users, Sessions and Context

Every record from a Salesforce browser carries the user, the session, the Lightning app and where the user was in Salesforce.

| Context | How GermainUX gets it |
| - | - |
| **User** | In Lightning, the user's email address from Salesforce, or the user ID when the email isn't available. In Classic, the user name, or the user ID. |
| **Session** | The Salesforce session cookie. In Lightning, where that cookie isn't readable from the page, a session value from the Lightning client that is unique to the session. |
| **App** | The label of the Lightning app, such as **Sales** or **Service Console** |
| **UI hierarchy** | Up to four levels that describe where the user is: the Lightning app, the navigation tab, console subtabs, the record as "Object: Record name", the path stage, the record tab, an open docked panel and an open modal dialog. |

The UI hierarchy is the context you filter and group by in dashboards. For heatmaps, GermainUX hashes the record-specific levels, so pages of the same type are grouped together.

## What the Profile Captures

| Capability | KPI | What is recorded |
| - | - | - |
| **Clicks and page loads**, named after what the user did, such as "Account View Record" | **Salesforce User Click** | Click name, duration, success, and the record ID for View Record and Update Record. See [User Click Analysis for Salesforce Cloud](https://docs.germainux.com/integrations/salesforce-monitoring/salesforce-user-click-analysis.md). |
| **Network requests**. Aura XHR calls are named **Aura HTTP Request** | **Salesforce Outbound HTTP Request** | URL, duration, status and success. An Aura request with an action in error is a failed request. |
| **Lightning Experienced Page Time (EPT)** | **Page Performance Measure** | A measure named **PageView EPT** for each Lightning page view |
| **Salesforce server time** for each Aura request | **Server Timing** | **Service** time and **DB** time, from the performance summary Salesforce returns |
| **Browser-to-server correlation** | **Salesforce Outbound HTTP Request** | The Salesforce request ID (`X-SFDC-Request-Id`), stored as `TID:<request ID>` so you can match the request to Salesforce server-side records with the same ID |
| **Searches**: list view, folder (for example Reports) and global search | **Search Results** | Search term and result count, named "\<Object> List Search", "\<Object> Search" or "Global Search" |
| **Console workspace tabs** | **Browser Metric** | Metric **Salesforce Workspace**, labelled **Tabs Opened**: the number of open workspace tabs, with each tab's title, URL and subtab count in **Details** |
| **Chatter feed actions**: posts, polls and questions created, comments created, updated or deleted, likes, bookmarks, votes, best answers, mutes and published drafts | **Salesforce Feed Event** | Action name (for example "Text Post Created" or "Comment Liked"), feed and record IDs, and the post or comment text in **Details** |
| **Record creation**, from **New** to Save | **Salesforce Record Creation BP** | Built from the **Salesforce Create Record Start** and **Salesforce Create Record End** browser events, with the object type |
| **Opportunity stages**: time spent in each stage of an opportunity's path | **Salesforce Opportunity Interval**, **Salesforce Opportunity BP** | Stage name and position, opportunity ID, and `COMPLETED` once the opportunity reaches the last stage |
| **Error dialogs and toasts** | **JavaScript Popup Dialog** | See [Error Monitoring for Salesforce Cloud](https://docs.germainux.com/integrations/salesforce-monitoring/error-monitoring-for-salesforce-cloud-configure.md) |
| **Failed Aura actions** | **Browser Event** | Event **Salesforce Error** with the message and the Apex controller class |
| **Console messages and Aura logger errors** | **JavaScript Console Event** | Salesforce-specific error names and severity |
| **Field changes**: picklists, date pickers, lookups, comboboxes and checkboxes, with the field label | **User Change** | Field label and value |
| **What the user was doing**, such as "Editing Opportunity record" or "Logging a call" | **Story Beat** | Labels built from object types, field names and navigation items |
| **Omni-Channel** presence, work and messages | **Chat Event**, **Chat Transaction** | See [Omni-Channel Monitoring for Salesforce Cloud](https://docs.germainux.com/integrations/salesforce-monitoring/omni-channel-monitoring-for-salesforce-cloud-configure.md) |
| **Agentforce** questions, answers and ratings | **Chat Event**, **Chat Transaction** | See [Agentforce Monitoring for Salesforce](https://docs.germainux.com/integrations/salesforce-monitoring/salesforce-agentforce-monitoring.md) |
| **User feedback**, including Agentforce likes and dislikes | **User Feedback** | See [User Feedback for Salesforce](https://docs.germainux.com/integrations/salesforce-monitoring/user-feedback-for-salesforce-configure.md) |
| **Errors the user saw**: error dialogs and toasts, the default error phrases, and failed Agentforce answers | **User-Facing Error** | One record for each error shown to the user |

The profile leaves out two kinds of request by default: Salesforce streaming (`/cometd/`) and CRM Analytics dashboards (`/analytics/wave/ui`).

## Page Names and Paths

Lightning URLs and page titles contain record IDs and record names. Grouped as they are, every record would be a page of its own. GermainUX replaces the record-specific parts with placeholders, so pages of the same type are analyzed together.

| Part | Example | Grouped as |
| - | - | - |
| Record ID in a record URL | `/lightning/r/Account/001.../view` | `/lightning/r/Account/<id>/view` |
| Dates, timestamps, long numbers and UUIDs in a path | `/2026-11-19/` | `<date>`, `<timestamp>`, `<number>`, `<uuid>` |
| Static files: icons, images, fonts, framework files and resources | `/resource/1700000000000/logo` | `/resource/<resource>` |
| Record name or search term at the start of a Lightning page title | "Acme Corp \| Account \| Salesforce" | "\<identifier> \| Account \| Salesforce" |

Dashboard and report names stay in the title, and so do related-list titles, because they don't identify a record.

## Session End

When the user clicks **Log Out** in Salesforce, GermainUX ends the monitored session and stops monitoring in that browser tab. The next login starts a new session.

## Additional Resources

> [card] [KPIs for Salesforce](https://docs.germainux.com/integrations/salesforce-monitoring/salesforce-monitoring-kpis.md)
>
> All preconfigured Salesforce KPIs

> [card] [User Monitoring and Replay](https://docs.germainux.com/integrations/salesforce-monitoring/salesforce-user-monitoring-and-replay.md)
>
> Session Replay for Salesforce

> [card] [Analytics](https://docs.germainux.com/analytics.md)
>
> More Analytics Features

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't Find What You Need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.