Skip to main content
ComponentsRUM JSRUM ExtRUM Windows
Availability2017.1 or later

Choose a Deployment Method

Pick the right method

RUM Extension

For browser-only deployments

Session Replay

Enable and validate replay

Troubleshooting

Check missing monitoring data

​
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:
  • 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

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:
View GermainUX Integrations

​
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:
  • Clicks and interactions
  • Conversations with chatbot or human
  • Friction detection and analysis (CX, UX, Workflow and Technology e.g. Errors)
  • Heatmaps (6 of them!)
  • Network activity
  • Page navigation
  • Performance (User, Workflow and Technology)
  • Session Replay
  • User activity
  • User Feedback (Collection & Analysis)
  • User journeys

​
RUM JS Deployment

RUM JS can typically be deployed through:
  • Application source code
  • Application templates or shared layouts
  • Content-management systems
  • eCommerce platforms
  • Framework-specific implementations
  • Tag-management platforms
To deploy Real User Monitoring (RUM) and Session Replay, first check whether there is a dedicated deployment guide for the integration you are using. If there isn’t one, follow the standard GermainUX RUM JS deployment guide. When the above methods are not allowed or technically possible, use the RUM Extension for browser-based applications or RUM Windows for Windows-based desktop applications, when applicable.

​
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:
  • Clicks and interactions
  • Conversations with chatbot or human
  • Friction detection and analysis (CX, UX, Workflow and Technology e.g. Errors)
  • Heatmaps (6 of them!)
  • Network activity
  • Page navigation
  • Performance (User, Workflow and Technology)
  • Session Replay
  • User activity
  • User Feedback (Collection & Analysis)
  • User journeys

​
RUM Extension Deployment

To deploy Real User Monitoring (RUM) and Session Replay, first check whether there is a dedicated deployment guide for the integration you are using. If there isn’t one, follow the standard GermainUX RUM Extension deployment guide. When the above methods are not allowed or technically possible, use the RUM JS for browser-based applications or RUM Windows for Windows-based desktop applications, when applicable.

​
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:
  • Clicks and interactions
  • Conversations with chatbot or human
  • Friction detection and analysis (CX, UX, Workflow and Technology e.g. Errors)
  • Heatmaps (6 of them!)
  • Network activity
  • Page navigation
  • Performance (User, Workflow and Technology)
  • Session Replay
  • User activity
  • User Feedback (Collection & Analysis)
  • User journeys

​
RUM Windows Deployment

RUM Windows operates through the GermainUX Windows-side monitoring components and configuration. A typical deployment includes:
  • 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.
To deploy Real User Monitoring (RUM) and Session Replay, first check whether there is a dedicated deployment guide for the integration you are using. If there isn’t one, follow the standard GermainUX RUM Windows deployment guide. When the above methods are not allowed or technically possible, use the RUM JS for browser-based applications or RUM Windows for Windows-based desktop applications, when applicable.

​
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:

​
Validate the Deployment

After deployment, perform a controlled test before broad production rollout. Verify that:
  • 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: 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 ConfigureUser 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:
  • 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.
More details on Data Security and Privacy.

​
Troubleshooting

If monitoring data or Session Replay is unavailable, verify:
  • 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.

​
Additional Resources

Configure

User Monitoring and Session Replay

KPIs

Related to User Monitoring and Session Replay

Session Replay Player

Read more

API

Of User Monitoring and Session Replay

AI

Insights & Recommendations

Analytics

More Analytics Features

Automation

More Automation Features

Dashboards

Dashboards and reports overview

Reports

Automatic and scheduled reports

Management

More Management Features

​
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.