🔖 GermainUX RUM JS
GermainUX RUM JS monitors the experience of real users interacting with web applications.
It captures performance, behavior, errors, business activity, and Session Replay directly from the user's browser and sends the resulting telemetry to GermainUX for real-time analysis.
👀 Overview
Use GermainUX RUM JS when you control the monitored web application and can add GermainUX JavaScript to its pages or application shell.
Depending on the UX monitoring profile, GermainUX can capture:
|
Item |
|---|
|
Page views |
|
Navigation |
|
User sessions and journeys |
|
Clicks and interactions |
|
Page and resource performance |
|
User-perceived response times |
|
JavaScript errors |
|
Browser freezes |
|
HTTP requests and service calls |
|
Application errors |
|
Business-process activity |
|
Session Replay |
|
Behavioral data used for UX and friction analysis |
This telemetry can be correlated with backend, database, infrastructure, and business-process monitoring.
📅 When to Use RUM JS
Use RUM JS when:
|
Condition |
|---|
|
You control the application or its tag-management configuration. |
|
You want continuous Real User Monitoring. |
|
You need Session Replay. |
|
You want to analyze user behavior, conversion, adoption, performance, or friction. |
|
Monitoring can execute from the application's JavaScript context. |
If you cannot modify the application, consider GermainUX RUM Extension.
❓ RUM JS or RUM Extension or RUM Windows?
|
Method |
Recommended When |
|---|---|
|
RUM JS |
You control the application and can add GermainUX JavaScript |
|
RUM Extension |
You cannot modify the application or monitoring must run from the browser extension |
|
RUM Windows |
This is to monitor Windows-native applications (e.g. C#, .NET, etc). However the above two RUM JS and RUM Extension are to monitor Web-Based applications (Angular, React, Salesforce, SAP, Siebel, Shopify etc) |
⚙️ How It Works
A typical architecture is:
Web Application → GermainUX RUM JS → GermainUX Enterprise
When a user opens the application:
-
GermainUX RUM JS loads.
-
It retrieves its monitoring configuration.
-
It captures telemetry permitted by the UX monitoring profile.
-
Privacy rules are applied.
-
The browser sends telemetry to GermainUX.
-
GermainUX processes and correlates the data for analysis, dashboards, alerts, Session Replay, and automation.
📋 Requirements
At a high level, confirm:
|
Requirement |
|---|
|
JavaScript is enabled. |
|
The application uses a supported browser. |
|
The browser can reach GermainUX. |
|
Content Security Policy permits required GermainUX resources. |
|
Firewall and proxy configuration permits required connections. |
|
Privacy configuration has been reviewed. |
📦 Deployment Options
RUM JS can be deployed through:
|
Option |
|---|
|
Application templates |
|
Shared layouts |
|
Tag-management platforms |
|
Content-management systems |
|
eCommerce platforms |
|
Framework-specific integrations |
|
Platform-specific integrations |
When a dedicated GermainUX integration exists for the application or framework, use its deployment instructions rather than applying a generic approach.
🗺️ Deployment Overview
The general process is:
-
Define the monitored application in GermainUX.
-
Create or select the UX monitoring profile.
-
Configure privacy and exclusions.
-
Obtain the RUM JS deployment configuration.
-
Add it to the application.
-
Validate in non-production.
-
Confirm telemetry and Session Replay.
-
Validate sensitive-data handling.
-
Roll out progressively to production.
The exact deployment mechanism depends on the application.
🔎 Google Tag Manager
For applications that use Google Tag Manager, follow the dedicated procedure:
Deploy RUM JS with Google Tag Manager
The GTM-specific tag creation, trigger configuration, publishing, and verification steps should remain only on that child page.
💻 Supported Platforms and Frameworks
RUM JS can be used with supported:
|
Category |
|---|
|
JavaScript frameworks |
|
CRM applications |
|
eCommerce platforms |
|
CMS platforms |
|
Business applications |
|
Custom web applications |
Examples include Angular, React, Vue.js, Magento, Shopify, WooCommerce, WordPress, Microsoft Dynamics 365, Salesforce, Oracle Siebel CRM, and other supported platforms.
Use the dedicated integration documentation when available.
🔧 Configure the UX Monitoring Profile
The UX monitoring profile controls what RUM JS captures.
Typical areas include:
|
Area |
|---|
|
Session monitoring |
|
Session Replay |
|
Page and route tracking |
|
User interactions |
|
Network requests |
|
JavaScript errors |
|
Performance |
|
Business-process detection |
|
Privacy |
|
Element and page exclusions |
|
Sampling |
|
Data volume |
Detailed configuration should remain in the applicable UX Monitoring documentation rather than being expanded on this deployment overview.
🔒 Privacy and Security
Configure privacy before production monitoring.
Determine:
|
Consideration |
|---|
|
Which applications and pages may be monitored |
|
Which users may be monitored |
|
Which fields must never be collected |
|
Which elements must be masked or excluded |
|
Whether user identifiers should be anonymized |
|
Who may access Session Replay |
|
Appropriate data retention |
Pay particular attention to passwords, authentication information, financial data, and other sensitive content.
🛡️ Content Security Policy
Applications using Content Security Policy may need to permit the GermainUX script and required network connections.
Apply only the GermainUX origins and directives required by the selected deployment.
Coordinate production CSP changes with the appropriate application-security team.
✅ Validate
After deploying RUM JS, confirm:
|
Check |
|---|
|
GermainUX JavaScript loads successfully. |
|
Required connections to GermainUX succeed. |
|
The correct application and UX monitoring profile are applied. |
|
User sessions appear. |
|
Interactions and performance data appear. |
|
Errors are captured. |
|
Session Replay operates when enabled. |
|
Privacy rules behave correctly. |
Validate representative:
|
Area |
|---|
|
Authenticated workflows |
|
Unauthenticated workflows |
|
Browsers |
|
Application routes |
|
Subdomains |
🚀 Production Rollout
For high-traffic applications, use a staged rollout:
-
Validate in development or QA.
-
Test privacy and Content Security Policy.
-
Deploy to a limited user population.
-
Review data quality and overhead.
-
Adjust monitoring configuration where required.
-
Expand progressively.
🐛 Troubleshooting
At a high level, if no telemetry appears, verify:
|
What to check |
|---|
|
Script deployment |
|
Application configuration |
|
UX monitoring profile |
|
GermainUX connectivity |
|
Firewall and proxy configuration |
|
Content Security Policy |
|
Application URL scope |
Platform-specific deployment issues should be addressed in the appropriate integration guide.
📞 Support
For assistance installing, configuring, or troubleshooting GermainUX-Agent, contact GermainUX Support.
Component: RUM JS
Feature Availability: 2017.1