Skip to main content
ComponentsGermainUX RUM JS Feature availability: GermainUX 2017.2 or laterEngineMobile AppRUM JS
Availability2018.1 or later

Privacy and consent

Avoid collecting sensitive details

Analyze feedback

Segment and compare responses

Configure alerts and ownership

Route feedback to owners

Troubleshooting

Fix feedback collection issues
Configure User Feedback for Salesforce Experience Cloud The GermainUX User Feedback Popup allows authenticated and guest users to provide feedback directly from a Salesforce Experience Cloud site. Each response can be correlated with the user’s current experience, including:
  • Site and environment
  • Page and URL
  • Authenticated or guest session
  • Recent navigation and clicks
  • Errors and validation messages
  • Performance and network activity
  • Business-process or journey step
  • Session Replay, when enabled
This helps teams understand both what the user reported and what occurred before the feedback was submitted.

Prerequisites

Before enabling feedback: See Deploy Monitoring for Salesforce Experience Cloud.

Define the feedback objective

Use feedback to answer a specific question. Keep questions short, neutral, and actionable.

Available feedback formats

Depending on the configured feedback mechanism, GermainUX can capture:
  • Thumbs up or thumbs down
  • Positive or negative feedback
  • Written comments
  • Ratings and scores
  • Survey responses
  • NPS responses
  • Site, page, user, and session context
A thumbs-up or thumbs-down response is not an NPS score. Standard NPS requires the likelihood-to-recommend question and a 0–10 scale:

Enable the Feedback Popup

The popup is disabled by default and must be enabled for the applicable Experience Cloud UX Monitoring Profile. Go to: Workspace > Analytics > UX Monitoring Profiles Depending on the GermainUX version: Workspace > Settings > Analytics > UX Monitoring Profiles Select the profile for the Experience Cloud site and open its initialization script. Enable the popup:
Add the feedback setting to the existing initialization script. Do not create a second germainApm.start() call. Save and publish the profile, then open a new Experience Cloud browser session.

Disable the popup

The default value is false. To disable it explicitly:
Disabling the Feedback Popup does not disable Real User Monitoring or Session Replay.

Customize the popup

The buttons, labels, colors, comment form, and position can be customized.
Retain the default GermainUX icons or replace the sample data with approved image data.

Configuration reference

Choose the position

Available positions are: Select a position that does not cover:
  • Experience Cloud navigation
  • Chat or support controls
  • Form buttons
  • Cookie or consent banners
  • Salesforce notifications
  • Mobile navigation
  • Accessibility controls
Test the popup across desktop, tablet, and mobile layouts. Use parentSelector when the controls must be attached to a specific stable site element rather than document.body.

Use clear labels

Recommended labels include: Avoid using “This page contains an error” as the only negative option. Users may be dissatisfied because of content, workflow, usability, performance, or support—not necessarily a technical failure.

Target guest and authenticated users

Define which Experience Cloud audiences should receive feedback controls. Possible scopes include:
  • Guest users
  • Authenticated customers
  • Partners
  • Employees
  • Specific user groups
  • Selected site pages
  • Specific workflows
  • Pilot users
  • Specific environments
Targeting can be controlled through the UX Monitoring Profile, URL scope, user attributes, or supported initialization logic. Test each user type separately because page structure, permissions, and identity context can differ.

Control feedback frequency

Avoid survey fatigue. For automatically triggered questions:
  • Do not prompt on every page
  • Avoid interrupting a transaction
  • Prompt after meaningful outcome
  • Do not immediately repeat
  • Limit repeated requests
  • Suppress synthetic users
  • Avoid overlapping surveys
Persistent positive and negative controls can remain available without automatically opening a survey.

Correlate feedback with session context

Confirm that feedback retains available context such as:
  • Experience Cloud site
  • Environment
  • Page
  • URL
  • Authenticated or guest status
  • Approved user identifier
  • Session ID
  • Submission time
  • Feedback type
  • Comment
  • Related error
  • Related business process
  • Related performance activity
This reduces the need for users to describe technical details manually.

Connect feedback with Session Replay

When replay is enabled, authorized analysts can review the activity leading to a feedback submission. Replay can reveal:
  • What the user was trying to accomplish
  • Which pages were visited
  • Whether the user repeated actions
  • Whether a control did not respond
  • Whether an error appeared
  • Whether the workflow was confusing
  • Whether performance contributed
  • What happened immediately before submission
Protect sensitive information before connecting feedback with replay. Feedback comments can contain personal, customer, health, financial, or confidential information. Before production rollout: A suitable placeholder is:

Validate the configuration

Test with both guest and authenticated sessions when both populations are monitored. Validation steps:
1

Open the Experience Cloud site

2

Confirm that the feedback controls appear

3

Verify that they do not obstruct the page

4

Submit positive feedback

5

Submit negative feedback with a comment

6

Confirm that both events reach GermainUX

7

Verify site, page, user, and session context

8

Confirm that Session Replay is linked when enabled

9

Verify privacy masking

10

Confirm that only authorized users can access the response

Also test:

KPIs

See KPIs of Real User Feedback Popup. Useful measures include:

Analyze feedback

Segment responses by:
  • Site
  • Page
  • User type
  • Guest versus authenticated
  • Customer or partner group
  • Region
  • Browser or device
  • Feedback type
  • Error category
  • Business process
  • Journey step
  • Application version
  • Time period
Use the new AnalysisDashboard for quick segmentation:
Segmentation for Feedback

Segmentation for Feedback - GermainUX

Compare feedback with:
  • Page and click performance
  • User-facing application errors
  • User validations
  • Journey abandonment
  • Business-process overrun
  • Repeated activity
  • Recent releases
  • Session Replay
Use aggregate trends to identify broad patterns and individual comments to understand specific experiences.

Dashboards

Go to: Workspace > Dashboards > All Search for:
  • Salesforce Experience Cloud dashboards
  • Portlets containing Feedback
  • User Experience dashboards
  • Marketing or journey dashboards
The exact dashboards available depend on the installed GermainUX version and configuration.

Configure alerts and ownership

Create alerts for feedback requiring timely action, such as:
  • Strongly negative feedback
  • A severe problem reported in a comment
  • Feedback correlated with a critical error
  • Repeated negative feedback for one page or workflow
  • A sudden decline in positive responses
  • Feedback from a high-impact process
Route feedback according to its likely owner: Do not generate a separate critical incident for every negative response. Consider severity, comment content, technical evidence, affected-user volume, and business impact.

Troubleshooting

The popup does not appear

Verify that:

Feedback submits but does not appear

Check:

Feedback has no user or session context

Verify that:

Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Salesforce Experience Cloud environment. Contact GermainUX Support.

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.