🚀 Deploy User Monitoring & Session Replay
🔍 Overview
GermainUX User Monitoring & Session Replay captures the actual experience of users interacting with web, browser-based, and native Windows applications.
Depending on the application and deployment requirements, User Monitoring & Session Replay can be deployed using:
|
Component |
|---|
|
GermainUX RUM JS |
|
GermainUX RUM Extension |
|
GermainUX RUM Windows |
For applications and technologies with a dedicated GermainUX Integration, use the corresponding Integration deployment guide. Integration guides provide application-specific instructions and identify the appropriate GermainUX components for that technology.
👉 Choose a Deployment Method
|
Component |
Use When |
|---|---|
|
GermainUX RUM JS |
Monitoring a web application where GermainUX JavaScript can be deployed directly. |
|
GermainUX RUM Extension |
Monitoring a browser-based application when direct RUM JS deployment is unavailable or browser-extension deployment is required or preferred. |
|
GermainUX RUM Windows |
Monitoring a native Windows application. |
Before using the generic deployment instructions, check whether a dedicated GermainUX Integration is available.
⚙️ Integration Deployment Guides
GermainUX provides dedicated Integration guides for many applications, platforms, frameworks, and technologies.
When an Integration guide is available, follow that guide instead of the generic RUM deployment instructions. The Integration guide identifies the recommended deployment architecture and may use RUM JS, RUM Extension, RUM Windows, or multiple GermainUX components.
Examples include:
|
Integration |
|---|
|
Salesforce Experience Cloud |
|
Oracle Siebel CRM |
|
SAP Commerce Cloud |
|
|
|
Other supported applications and technologies |
📃 RUM JS
Use GermainUX RUM JS when GermainUX JavaScript can be deployed directly into the monitored web application.
RUM JS can capture available user-experience data including:
|
Data |
|---|
|
User activity |
|
Page navigation |
|
Clicks and interactions |
|
Friction detection and analysis (UX, Workflow and Technology e.g. Errors) |
|
Performance (User, Workflow and Technology) |
|
Network activity |
|
User journeys |
|
Session Replay |
|
6 Heatmaps |
|
User Feedback (Collection & Analysis) |
🚀 RUM JS Deployment
RUM JS can typically be deployed through:
|
Method |
|---|
|
Application source code |
|
Application templates or shared layouts |
|
Tag-management platforms |
|
Content-management systems |
|
eCommerce platforms |
|
Framework-specific implementations |
When a dedicated Integration guide exists for the application or technology, use that guide instead.
🕹 RUM Extension
Use GermainUX RUM Extension when the monitored application runs in a browser but GermainUX RUM JS cannot be directly deployed, or when browser-extension deployment provides the required monitoring scope.
RUM Extension can capture available browser and application context including:
|
Data |
|---|
|
User activity |
|
Page navigation |
|
Clicks and interactions |
|
Friction detection and analysis (UX, Workflow and Technology e.g. Errors) |
|
Performance (User, Workflow and Technology) |
|
Network activity |
|
User journeys |
|
Session Replay |
|
6 Heatmaps |
|
User Feedback (Collection & Analysis) |
📦 RUM Extension Deployment
RUM Extension can be deployed to individual browsers or centrally across an organization using supported enterprise browser-management mechanisms.
Deploy GermainUX RUM Extension
For applications such as CRM, ERP, or other supported SaaS platforms, check the Integration Deployment Guide first. It may contain application-specific configuration and deployment requirements.
🖥 RUM Windows
Use GermainUX RUM Windows to monitor users interacting with native Windows applications.
RUM Windows provides user-experience visibility for applications that do not run inside a web browser.
Depending on the monitored application and configuration, available context can include:
|
Data |
|---|
|
User activity |
|
Page navigation |
|
Clicks and interactions |
|
Friction detection and analysis (UX, Workflow and Technology e.g. Errors) |
|
Performance (User, Workflow and Technology) |
|
Network activity |
|
User journeys |
|
Session Replay |
|
6 Heatmaps |
|
User Feedback (Collection & Analysis) |
🚧 RUM Windows Deployment
RUM Windows operates through the GermainUX Windows-side monitoring components and configuration.
A typical deployment includes:
|
Step |
|---|
|
Deploy the required GermainUX Windows component. |
|
Connect it to GermainUX Enterprise. |
|
Configure the applications and users to monitor. |
|
Configure User Monitoring and Session Replay. |
|
Configure privacy, masking, and exclusions. |
|
Validate monitoring on a test device. |
|
Roll out to additional users or devices after validation. |
When a dedicated Integration guide exists for the native application, use the Integration guide because it may contain application-specific monitoring requirements.
❓ Which Deployment Guide Should I Use?
Use the following process to determine which guide to follow.
1️⃣ 1. Check for a GermainUX Integration
If a dedicated GermainUX Integration exists:
Use the Integration Deployment Guide.
The Integration guide identifies the recommended GermainUX components and application-specific configuration.
2️⃣ 2. If No Integration Guide Exists
Select the RUM component based on the application:
Web application where JavaScript can be deployed
→ RUM JS
Browser-based application where JavaScript cannot be deployed or browser-level monitoring is required
→ RUM Extension
Native Windows application
→ RUM Windows
Some monitoring scenarios may require more than one GermainUX component.
📋 General Deployment Process
Regardless of the deployment method, the general process is:
|
Step |
Action |
|---|---|
|
1 |
Identify the application to monitor. |
|
2 |
Check for a GermainUX Integration and use its deployment guide when available. |
|
3 |
Select the appropriate RUM component when a dedicated Integration guide is not available. |
|
4 |
Deploy the component. |
|
5 |
Configure the monitored applications and users. |
|
6 |
Configure the data to capture. |
|
7 |
Configure Session Replay when required. |
|
8 |
Configure privacy, masking, and exclusions. |
|
9 |
Test with a controlled user population. |
|
10 |
Validate monitoring and Session Replay. |
|
11 |
Expand deployment after successful validation. |
✅ Validate the Deployment
After deployment, perform a controlled test before broad production rollout.
Verify that:
|
Check |
|---|
|
The appropriate RUM component is active. |
|
The expected application is being monitored. |
|
User sessions are reaching GermainUX. |
|
User activity is captured as expected. |
|
Application and user context are correct. |
|
Errors and performance data are captured when applicable. |
|
Session Replay is available when enabled. |
|
User Feedback works when configured. |
|
Privacy and masking settings are applied correctly. |
|
Only authorized users can access captured data. |
🎞 Session Replay
Session Replay can be enabled with RUM JS, RUM Extension, or RUM Windows where supported.
After enabling Session Replay:
|
Step |
Action |
|---|---|
|
1 |
Generate a controlled test session. |
|
2 |
Confirm that the session appears in GermainUX. |
|
3 |
Open the Session Replay. |
|
4 |
Verify that the expected user activity is captured. |
|
5 |
Verify that masking and exclusions are applied correctly. |
|
6 |
Confirm that errors, feedback, and other available context are associated with the appropriate point in the session. |
Session Replay should be validated before broad production rollout.
💬 User Feedback
User Feedback can be configured with the applicable RUM deployment to collect feedback directly from monitored users.
Feedback can then be associated with available user and session context, helping teams understand:
What the user said + What the user experienced
See Configure User Feedback for deployment, configuration, advanced configuration, APIs, validation, and troubleshooting.
🔒 Security & Privacy
User Monitoring and Session Replay can capture detailed information about user interactions with monitored applications.
Before production deployment:
|
Action |
|---|
|
Determine which applications and users should be monitored. |
|
Capture only the information required for the use case. |
|
Configure appropriate masking and exclusions. |
|
Exclude sensitive fields and application areas when required. |
|
Restrict access to authorized users. |
|
Apply appropriate data-retention policies. |
|
Review applicable privacy, consent, security, and compliance requirements. |
|
Validate privacy settings using controlled test sessions before broad deployment. |
Troubleshooting
If monitoring data or Session Replay is unavailable, verify:
|
Check |
|---|
|
The appropriate RUM component is deployed and active. |
|
The correct application is configured for monitoring. |
|
The monitored user is included in the intended monitoring scope. |
|
Monitoring data can reach GermainUX. |
|
Browser security policies are not blocking RUM JS or RUM Extension where applicable. |
|
The Windows monitoring component is running for RUM Windows. |
|
Session Replay is enabled when required. |
|
Privacy or exclusion rules are not preventing the expected data from being captured. |
For additional troubleshooting, see User Monitoring & Session Replay Troubleshooting.
🔗 Related Documentation
🤝 ℹ️ Get Help
The Germain Team can help you set this up. Contact GermainUX Support.
Component: RUM JS, RUM Ext, RUM Windows
Feature Availability: 2017.1 or later