Skip to main content
ServiceAnalyticsAutomation
Availability2017.1 or later

Deploy

RUM JS, Extension, Windows

Configure

Popup settings

Analyze

Review feedback

Troubleshoot

Common fixes

Overview

Configure GermainUX User Feedback to collect feedback directly from users while they interact with monitored web and native Windows applications. Depending on the application, User Feedback can be deployed using: Feedback can be associated with available user, application, session, activity, error, performance, and Session Replay context, helping teams connect: What the user said + What the user experienced This page covers deployment, configuration, advanced configuration, validation, API integration, troubleshooting, security, and privacy.

Before You Begin

Before configuring User Feedback:

Choose a Deployment Method

Select the RUM component appropriate for the monitored application. Only one RUM deployment method is normally required for a given application.

Deploy User Feedback

RUM JS

Use GermainUX RUM JS when the monitoring script can be deployed directly into the monitored web application. The deployment process is:

RUM Extension

Use GermainUX RUM Extension when the required monitoring script cannot be deployed directly into the application’s required execution context or when browser-extension deployment is preferred. For example, some SaaS applications may require extension-based monitoring to provide the required browser context. The deployment process is:

RUM Windows

Use GermainUX RUM Windows to collect User Feedback from monitored native Windows applications. The deployment process is:

Configure the User Feedback Popup

For RUM JS, the Feedback Popup is configured in the applicable Monitoring Profile’s Init Script. The popup is disabled by default and must be enabled for each applicable Monitoring Profile.

Enable the Popup

Set settings.plugins.feedback.enabled to true.
This enables the Feedback Popup using its default settings.

Disable the Popup

No configuration is required to keep the popup disabled because enabled defaults to false. To disable it explicitly:

Customize the Feedback Popup

The popup’s appearance, labels, position, buttons, and comment form can be customized. The following example enables User Feedback and customizes the positive and negative buttons, labels, colors, comment form, and screen position:

Advanced Configuration Reference

The settings.plugins.feedback object provides detailed control over the RUM JS Feedback Popup.

FeedbackSettings

FeedbackSettings Properties

FeedbackButton

FeedbackButton Properties

Default button settings include the GermainUX thumbs-up and thumbs-down icons, standard accessible labels, and default positive and negative colors. The position property determines where the Feedback Popup appears. Supported values:
  • top-left
  • top-right
  • bottom-left
  • bottom-right
Default:
Choose a position that does not interfere with application navigation, chat widgets, accessibility controls, or other interactive elements.

Comment Configuration

The comment object controls the form used to collect additional feedback.

Comment Styles

Custom styles can be applied to:
  • container
  • email
  • comment
  • send
  • close
For example:
Use custom styling when the Feedback Popup needs to align with the visual design of the monitored application.

Parent Element

By default, feedback buttons are added to:
Use parentSelector when the feedback control needs to be attached to another element. For example:
When using a custom parent element, verify that:

Validate the Deployment

Perform a controlled test before broad rollout.

Validate Feedback KPIs & Measures

Feedback submitted through the User Feedback Popup is captured by the preconfigured User Feedback KPI. The User Session Replay KPI also provides session-level feedback measures: Use these measures to verify the configuration and identify sessions containing feedback.

API Integration

GermainUX APIs can process feedback submitted through the User Feedback Popup and use it within custom analytics and automation workflows. API-based processing can be used to:
  • Create automated insights
  • Trigger real-time alerts and notifications
  • Prioritize negative experiences
  • Initiate follow-up workflows
  • Create custom transactions
  • Enrich feedback analysis with user and session context
For example:
Negative FeedbackProcess FeedbackAnalyze User & Session ContextPrioritizeTrigger Follow-Up
This allows feedback to become an operational signal rather than simply a response stored for later review.

Automate Actions from Feedback

Feedback can be incorporated into workflows that:
  • Notify a support, product, or operations team.
  • Create or update a ticket.
  • Trigger additional analysis.
  • Route feedback according to application, category, user population, or other available context.
  • Initiate a follow-up workflow.
  • Generate a custom transaction for additional analysis or reporting.
The exact workflow can be customized according to the organization’s requirements.

User Monitoring and Session Replay APIs

Use the User Monitoring and Session Replay APIs for applicable API operations involving User Feedback and its associated monitoring context. Refer to the User Monitoring and Session Replay API documentation for available API operations.

Analyze Submitted Feedback

After deployment, submitted feedback can be investigated using GermainUX Analytics. Use the User Feedback KPI to review feedback by application, page or screen, and user, and open the associated Session Replay to see what the user experienced when the feedback was submitted.

Troubleshooting

Feedback Does Not Appear

Verify that:
  • User Feedback is enabled in the applicable Monitoring Profile.
  • The Real User Monitoring component is active and sending data.
  • The correct application and environment are being analyzed.
  • The selected time range includes the test feedback.
  • The feedback is associated with the expected monitored session.

Session Replay Is Not Available

Verify that:
  • Session Replay is enabled.
  • The application and user are included in the Session Replay configuration.
  • The session occurred within the selected time range.
  • Privacy or exclusion settings did not prevent the expected data from being captured.

Security & Privacy

Feedback comments and Session Replay may contain personal or sensitive information. Before production rollout:
  • Configure appropriate masking and exclusion rules.
  • Limit access to authorized roles.
  • Confirm applicable consent requirements.
  • Avoid collecting unnecessary personal information.
  • Apply appropriate data-retention policies.
  • Protect API credentials and integrations.
  • Limit sensitive information sent through alerts or external systems.
  • Test feedback alerts and integrations to ensure they do not expose sensitive content.
If an email address or other identifying information is collected, verify that it is necessary for the intended feedback workflow and handled according to your organization’s privacy requirements. User Feedback GermainUX RUM JS GermainUX RUM Extension GermainUX RUM Windows User Session Monitoring & Replay Analytics Automation Data Retention

Get Help

Contact GermainUX Support

The Germain Team can help you set this up.

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