Skip to main content
ComponentsEngineJS ProfilerRPA BOT RecorderRUM JS
Availability2014.1 or later

Supported monitoring components

Components by coverage type

Prerequisites

Gather details before deploying

Deploy RUM JS

Load script in Experience Cloud

Troubleshooting

Fix Experience Cloud issues
Deploy Monitoring for Salesforce Experience Cloud GermainUX monitors the availability, performance, user experience, business processes, errors, and usage of Salesforce Experience Cloud sites. The deployment is modular. Install only the components required for the monitoring capabilities you want to enable.

​
Supported monitoring components

1

Identify the Experience Cloud sites and environments to monitor

2

Create the Experience Cloud UX Monitoring Profile in GermainUX

3

Configure privacy and bot exclusions

4

Review the generated RUM JS installation instructions

5

Add the required Salesforce Trusted URLs or CSP permissions

6

Deploy RUM JS to the Experience Cloud site

7

Publish the site

8

Validate Real User Monitoring and Session Replay

9

Configure business-process monitoring and user feedback

10

Configure Salesforce API monitoring through the Engine when required

11

Optionally deploy the JS Profiler and synthetic monitoring

12

Configure KPIs, SLAs, alerts, dashboards, and maintenance periods

​
Prerequisites

Before deploying browser monitoring, collect: Create separate profiles for sites or environments that require different URLs, monitoring settings, or privacy controls.

​
Create the UX Monitoring Profile

In GermainUX, go to: Workspace > Settings > Wizards > Salesforce Experience Cloud Depending on the GermainUX version, this may appear as: Workspace > Wizards > Salesforce Experience Cloud Enter:
  • Application or site name
  • Experience Cloud URL
  • Environment
  • Privacy settings
  • Bot and crawler exclusions
  • Other settings requested by the wizard
Complete the form and select Finish. The wizard creates the application configuration and UX Monitoring Profile required for the site.

​
Review the profile

Go to: Workspace > Analytics > UX Monitoring Profiles Depending on the version: Workspace > Settings > Analytics > UX Monitoring Profiles Select the profile created for the Experience Cloud site and review:
  • Application name
  • Environment
  • URL matching
  • Monitoring status
  • Session Replay status
  • Privacy rules
  • Bot and crawler exclusions
  • Initialization script
  • Installation instructions
  • GermainUX endpoints
Use the Installation section to retrieve the deployment instructions again.
Follow the installation instructions generated for the selected profile. Do not copy configuration values from another Salesforce site or environment.

​
Deploy RUM JS

Deploy the generated GermainUX RUM JS integration into the Experience Cloud site so it loads in the site’s required page context. The exact Salesforce procedure depends on:
  • Experience Builder version
  • Site template
  • Lightning Web Runtime or Aura runtime
  • Site security configuration
  • Organization release
  • Custom Experience Cloud implementation
Where supported by the selected Experience Cloud configuration, the generated loader can be added through the site’s approved head-markup or script-loading mechanism. The deployment must ensure that:
  • RUM JS loads on every required site page.
  • The correct UX Monitoring Profile is selected.
  • The script is loaded only once.
  • Guest and authenticated pages are included as intended.
  • Monitoring does not run on unrelated Salesforce sites.
  • The site can download the required GermainUX resources.
  • Browser telemetry can be sent to GermainUX.
After adding the integration, publish the Experience Cloud site.

​
Content Security Policy and Trusted URLs

Salesforce can block scripts and outbound connections that are not explicitly trusted. Add the GermainUX origins identified in the generated installation instructions to the applicable Salesforce Trusted URLs or CSP configuration. Depending on the deployment, permission may be required for:
  • Script loading
  • connect-src requests
  • Images
  • WebSocket connections
  • Frames or workers, when used by an enabled feature
Use the exact GermainUX origins required by the deployment. Avoid broad wildcard entries. After updating the security configuration:
1

Publish the site

2

Open a new browser session

3

Review the browser console

4

Confirm that no CSP violations block GermainUX

5

Confirm that telemetry requests succeed

​
Authenticated and guest users

Experience Cloud can serve both authenticated and unauthenticated visitors. Define how each group should be monitored.

​
Authenticated users

Confirm that GermainUX receives an approved user identifier after authentication. Do not capture:
  • Passwords
  • Authentication tokens
  • Salesforce session identifiers
  • OAuth tokens
If usernames or email addresses cannot be stored, use a permitted pseudonymous identifier.

​
Guest users

Guest activity can be monitored without assigning a personal identity. Confirm that:
  • Each browser session receives a suitable anonymous identifier.
  • Guest activity is not incorrectly assigned to a Salesforce user.
  • Login transitions do not combine anonymous and authenticated identities incorrectly.
  • Consent requirements are met.
  • Bots and crawlers are excluded.

​
Exclude bots and crawlers

The Experience Cloud wizard can configure standard bot and crawler exclusions. Typical exclusions include:
  • Googlebot
  • Bingbot
  • Baiduspider
  • DuckDuckBot
  • YandexBot
  • Sogou
  • Slurp
  • FacebookExternalHit
  • Synthetic and load-testing agents
Excluding automated traffic prevents it from affecting user-experience, adoption, conversion, and Session Replay analytics. Do not exclude a common browser user agent used by legitimate visitors.

​
Configure privacy

Experience Cloud sites can expose customer, partner, employee, case, account, order, and other confidential data. Before production rollout, mask or exclude:
  • Passwords
  • Authentication and session tokens
  • Customer and partner identifiers
  • Names and contact information
  • Case descriptions
  • Account information
  • Payment data
  • Protected health information
  • Attachments
  • Search queries
  • Form fields
  • Custom Lightning components containing sensitive data
  • User-feedback comments when required
Review both standard Salesforce components and custom Lightning Web Components. Test privacy settings with:
  • Guest users
  • Authenticated customers
  • Partners
  • Employees
  • Administrative users
  • Desktop and mobile layouts

​
Validate RUM JS loading

Open the Experience Cloud site in a new browser session and use the browser developer tools. Confirm that:
  • The GermainUX script request succeeds.
  • No 404, 403, TLS, or CSP error appears.
  • The intended GermainUX endpoint is used.
  • Monitoring initializes once.
  • Telemetry requests succeed.
  • The profile matches the current site URL.
  • Unrelated Salesforce pages are not monitored.
If a CDN or cache is used, confirm that the published site contains the latest integration.

​
Validate Real User Monitoring

Perform a representative journey:
1

Open the Experience Cloud site

2

Navigate between pages

3

Sign in when authenticated monitoring is enabled

4

Search for content or a record

5

Open a relevant page

6

Submit a safe test form or transaction

7

Trigger a known validation when appropriate

8

Sign out

Confirm in GermainUX that:
  • A user session is created.
  • The correct application and environment are assigned.
  • Guest or authenticated identity is handled correctly.
  • Pages, clicks, and network requests are captured.
  • Errors and validations appear under the intended KPIs.
  • Business-process events appear when configured.
  • Session Replay is available when enabled.
  • Sensitive content is masked or excluded.

​
Validate Session Replay

Confirm that replay:
  • Reconstructs the expected page sequence
  • Shows the recorded user interactions
  • Includes relevant errors and performance events
  • Associates activity with the correct session
  • Protects sensitive content
  • Does not expose authentication credentials or tokens
  • Ends or changes identity correctly at logout
Session Replay reconstructs captured page changes and events. It is not a screen-recording video.

​
Business-process monitoring

After RUM is active, configure critical Experience Cloud journeys such as:
  • Registration
  • Login
  • Customer onboarding
  • Case creation
  • Self-service support
  • Knowledge search
  • Partner lead submission
  • Application or request submission
  • Order or payment workflow
  • Profile update
GermainUX can identify:
  • Slow steps
  • Workflow overruns
  • Drop-offs
  • Repeated actions
  • Unexpected paths
  • Errors blocking completion
  • Differences between user groups
  • Lost productivity or customer effort
For example, GermainUX can identify customers requiring eight minutes to complete a workflow expected to take two minutes, then isolate the steps responsible for the six-minute overrun. See Business Process and Workflow Mining.

​
Application and API monitoring

RUM JS provides essential browser-side health and performance monitoring. For Salesforce API, event, capacity, or server-side monitoring, deploy and configure the GermainUX Engine. Engine-based monitoring can collect:
  • Salesforce API activity
  • Resource usage
  • Instance status
  • Real-Time Event Monitoring
  • Event Monitoring logs
  • Apex and Flow information
  • Audit activity
  • Errors and exceptions
See:

​
JavaScript analysis

Deploy the GermainUX JS Profiler when RUM identifies a browser-side issue that requires deeper evidence. Examples include:
  • Browser freezes
  • Expensive JavaScript functions
  • Repeated execution
  • Custom Lightning component errors
  • Slow network requests
  • Browser CPU or memory problems
The JS Profiler captures browser-side JavaScript, network, and execution information. It does not directly profile server-side Apex execution. Correlate browser evidence with Apex, API, log, and database telemetry collected through the Engine. See GermainUX JS Profiler.

​
Mobile application monitoring

If the Experience Cloud implementation includes a native mobile application, deploy the GermainUX Mobile App integration appropriate to that application. Mobile monitoring can provide:
  • Application and device context
  • Mobile sessions
  • Errors and crashes
  • Network activity
  • Performance
  • User interactions
See GermainUX Mobile App.

​
Synthetic monitoring

Use the RPA Bot Recorder to create Selenium-based scenarios for critical Experience Cloud journeys. Synthetic scenarios can test:
  • Site availability
  • Login
  • Registration
  • Navigation
  • Search
  • Case submission
  • Form submission
  • Logout
After recording:
1

Import the scenario into GermainUX

2

Select an execution Engine and location

3

Configure credentials and safe test data

4

Add success assertions

5

Configure step and scenario timeouts

6

Run the scenario manually

7

Configure its schedule and alerts

8

Enable recurring execution after validation

See GermainUX RPA Bot Recorder.

​
Automations and RPA bots

GermainUX automation can:
  • Notify teams
  • Create incidents
  • Run diagnostic scripts
  • Call HTTP APIs
  • Generate reports
  • Collect additional evidence
  • Execute approved remediation
  • Validate recovery
Automatic remediation should be limited to explicit, approved, tested, and reversible actions. See Automation. Use a phased rollout:
1

Sandbox or Development

2

QA

3

UAT

4

Controlled production users

5

All intended production traffic

At each stage, review:
  • Site compatibility
  • CSP
  • Monitoring coverage
  • Identity handling
  • Session Replay
  • Privacy masking
  • Browser performance
  • Network volume
  • Data volume
  • Error collection
  • User feedback

​
Upgrade the deployment

When upgrading GermainUX or changing the profile:
1

Review the current generated installation instructions

2

Compare them with the deployed integration

3

Test changes in a sandbox

4

Back up the existing site configuration

5

Update RUM JS or profile settings

6

Publish the site

7

Clear applicable caches

8

Validate monitoring and privacy

9

Promote the change through the normal Salesforce release process

​
Roll back

To remove or roll back browser monitoring:
1

Disable the UX Monitoring Profile when immediate collection must stop

2

Remove or restore the Experience Cloud integration using the reverse of the deployment procedure

3

Restore the previous site configuration

4

Publish the site

5

Clear applicable caches

6

Open a new browser session

7

Confirm that RUM JS no longer loads

8

Verify normal site operation

Disabling the profile does not necessarily remove the script from the published Experience Cloud site.

​
Troubleshooting

​
RUM JS does not load

Verify:
  • The site was published.
  • The integration exists in the active site version.
  • The script URL is correct.
  • CSP or Trusted URLs permit the request.
  • DNS and TLS are valid.
  • Browser policy does not block the script.
  • The latest site version is not hidden by caching.

​
RUM JS loads but no data appears

Check:
  • The UX Monitoring Profile is enabled.
  • The current URL matches the profile.
  • Telemetry requests are not blocked.
  • The GermainUX endpoint is correct.
  • Bot exclusions do not match the user.
  • Privacy or filtering rules are not excluding all activity.

​
Authenticated users are not identified

Verify:
  • User metadata is available after authentication.
  • The configured identity provider runs after login.
  • Login transitions are handled correctly.
  • The selected identifier is permitted and populated.
  • The user started a new session after configuration changes.

​
Session Replay is unavailable

Confirm that:
  • Replay is enabled for the profile.
  • Replay is enabled globally.
  • The user and site are within the capture scope.
  • Replay telemetry succeeds.
  • Privacy rules do not exclude the complete page.
  • The session contains recordable activity.

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