Skip to main content
ComponentsEngineJS ProfilerMobile AppRPA Bot RecorderRUM JS
Availability2018.1 or later

KPI data sources

Browser and server telemetry sources

Salesforce platform KPIs

Supplement with platform data

User-feedback KPIs

Link sentiment to sessions

Validation checklist

Confirm telemetry after deployment

​
Overview

GermainUX provides preconfigured KPIs for monitoring the availability, performance, usage, and user experience of Salesforce Experience Cloud sites. You can also create custom KPIs for organization-specific pages, components, journeys, and service-level objectives. The KPIs available in your environment depend on the monitoring components you deploy and the Salesforce features enabled for your organization.

​
KPI data sources

RUM JS and JS Profiler provide browser-side telemetry. They do not directly profile server-side Apex execution. Server-side Salesforce information is collected through the Engine, Salesforce APIs, event logs, or debug logs.

​
User sessions

Use session KPIs to understand who uses the site, how long sessions last, and whether users complete their intended journeys. Keep the same session identifier when a guest signs in if you want to analyze the complete guest-to-authenticated journey.

​
Page and navigation performance

Experience Cloud sites frequently behave as single-page applications. Configure virtual-page and route detection so navigation within the site is measured even when the browser does not perform a full page load. Define stable logical page names for Experience Builder routes. This prevents record identifiers, query strings, locale prefixes, or dynamic URL segments from fragmenting the KPI data.

​
User interaction

For useful reporting, assign business-oriented names such as Submit Support Case, Search Knowledge, or Accept Partner Lead instead of relying only on HTML element text.

​
Browser and application errors

Do not classify expected validation messages as application failures. Keeping validation separate prevents normal form behavior from inflating reliability and error-rate KPIs.

​
Network and service requests

Exclude or sanitize sensitive URL parameters, request bodies, headers, and response content before enabling detailed request capture.

​
Business-process KPIs

Business-process monitoring connects individual pages, clicks, and requests into complete Experience Cloud journeys. Common processes include:
  • User registration and account activation
  • Login, logout, and password recovery
  • Support-case creation
  • Case-status review
  • Knowledge search and article viewing
  • Partner lead registration
  • Opportunity submission
  • Order or application submission
  • Profile and preference updates
Each configured process can produce KPIs such as: Custom business processes automatically make additional process and step dimensions available for dashboards, pivots, and reports.

​
Salesforce platform KPIs

When the GermainUX Engine and the required Salesforce APIs are configured, Experience Cloud browser telemetry can be supplemented with Salesforce platform information.

​
Availability, capacity, and usage

​
Login and security events

Depending on Salesforce licensing and Event Monitoring configuration, the following events may be available:
  • Login and logout
  • Login As activity
  • API activity and API anomalies
  • Credential-stuffing detections
  • Session-hijacking detections
  • Report execution and report anomalies
  • Record changes
  • Bulk API result downloads
The Login As event can be particularly relevant to Experience Cloud because it identifies administrators signing in as another user, including supported Experience Cloud scenarios.

​
Code, log, and backend execution

When Salesforce debug-log or event-log collection is enabled, GermainUX can report KPIs for:
  • Apex execution and triggers
  • Apex callouts
  • Unexpected Apex exceptions
  • SOQL and database execution
  • Flow interviews and coverage
  • Visualforce execution
  • Aura requests
  • REST, SOAP, Bulk API, and URI activity
These backend KPIs require the corresponding Salesforce collection configuration. They are not produced by RUM JS or JS Profiler alone.

​
Synthetic monitoring KPIs

RPA-based synthetic scenarios measure site availability and performance even when no real users are active. Use a dedicated test account and non-production-safe data wherever possible. Do not run destructive synthetic actions against production records unless the scenario has been explicitly designed for that purpose.

​
User-feedback KPIs

If the GermainUX feedback popup is enabled, you can correlate user sentiment with sessions, pages, errors, and performance. Common feedback measurements include:
  • Positive and negative feedback volume
  • Feedback score or sentiment
  • Feedback by page or component
  • Feedback by user, account, browser, device, or location
  • Feedback associated with slow pages or failed requests
  • Feedback associated with a session replay
  • Comments submitted by users
Apply the configured privacy rules to feedback comments because users may enter personal or confidential information.

​
Analyze KPIs

Use dashboards and pivots to break down Experience Cloud KPIs by dimensions such as:
  • Site and application
  • Environment
  • Page or route
  • Experience Builder component
  • User or guest status
  • Account, contact, profile, or user type
  • Browser, operating system, and device
  • Geography and network
  • Salesforce organization and instance
  • Error type
  • Request endpoint
  • Business process and step
  • Release or application version
Start with these dashboard views:
  • Availability and synthetic health
  • Active users and session trends
  • Page and route performance
  • Slow and failed user interactions
  • Browser and application errors
  • Network and Salesforce request performance
  • Business-process completion and abandonment
  • User feedback and affected-session analysis
Use Session Replay to investigate an affected session. Replay reconstructs the monitored browser experience from captured events; it is not a video recording.

​
Create custom KPIs

Create a custom KPI when a preconfigured KPI does not represent the business outcome or technical operation you need to measure. A useful custom KPI should define:
  • The event or transaction being measured
  • Its business meaning
  • The expected unit, such as seconds, count, percentage, or score
  • The dimensions needed for analysis
  • Warning and critical thresholds
  • The applications and environments to which it applies
  • Privacy and data-retention requirements
  • The owner responsible for reviewing it
Examples include partner registration completion, knowledge-search success, case deflection, application submission, and response time for a specific Lightning Web Component.

​
Validation checklist

After deployment, verify that:
  • The Experience Cloud site appears under the intended application name.
  • Authenticated and guest sessions are classified correctly.
  • Client-side navigation generates distinct logical page views.
  • Clicks use stable, meaningful names.
  • Network requests are assigned to the correct site and operation.
  • Expected validation messages are separate from application errors.
  • Sensitive values are masked or excluded.
  • Business-process steps appear in the correct sequence.
  • Synthetic runs use the intended environment and account.
  • Engine-based Salesforce KPIs are arriving at their configured schedule.
  • Dashboards use the correct environment, site, and time filters.
  • Alerts are configured only after a representative baseline is available.

​
Get Help

Contact GermainUX Support

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.

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.