Skip to main content
ComponentsEngineJS ProfilerMobile AppRPA Bot RecorderRUM JS
Availability2022.1 or later

Overview

SAP apps supported for replay

SAP Commerce Cloud Monitoring

Track customer journeys end-to-end

Privacy Configuration

Mask or exclude SAP fields

Troubleshooting

Resolve SAP monitoring issues
Configure User Monitoring and Session Replay for SAP

​
Overview

GermainUX monitors user activity and reconstructs sessions for compatible browser-based SAP applications, including: User Monitoring provides aggregated insights across users and sessions. Session Replay provides detailed context for investigating individual experiences. GermainUX can capture:
  • Pages and application views
  • User actions and navigation
  • Clicks, input changes, scrolling, and other configured interactions
  • Page and action response times
  • Browser and JavaScript errors
  • Network requests
  • Business-process steps
  • User feedback
  • Frustration indicators
  • Device, browser, and location attributes
  • Session Replay data
Session Replay reconstructs captured browser activity; it is not a video recording. Replay completeness depends on the application structure, monitoring scope, browser context, and privacy configuration.
AI summaries: GermainUX can AI-summarize any individual session, so you know what the user did without replaying it. It can also summarize a bulk set of sessions at once (for example 1,000 or 100,000 sessions) to surface the top recurring frictions. See AI-Generated Session Summaries.

​
Prerequisites

Before enabling User Monitoring and Session Replay:
1

Deploy GermainUX RUM JS in the SAP web application

2

Confirm that the script runs in the required application context

3

Create or select the appropriate UX Monitoring Profile

4

Define applications, URLs, environments, and users in scope

5

Configure masking and exclusion rules

6

Confirm that the required network and security policies permit telemetry collection

For applications contained in cross-origin frames, RUM JS must run inside each frame that needs to be monitored. A script running only in the parent page cannot access protected cross-origin content. User Monitoring and Session Replay are intended for compatible browser applications. They do not monitor the native SAP GUI desktop client.

​
Enable User Monitoring

1

Go to Workspace > Analytics > UX Monitoring Profiles

2

Select the profile associated with the SAP application

3

Enable user-session and interaction monitoring

4

Configure the application URLs and environments in scope

5

Select the user actions and browser telemetry to capture

6

Configure user and session identification

7

Save and publish the profile

8

Open the SAP application and confirm that session data reaches GermainUX

The available settings may vary by GermainUX version.

​
Enable Session Replay

Within the SAP UX Monitoring Profile:
1

Enable Session Replay

2

Select the applications and environments to record

3

Configure recording or sampling rules

4

Define included and excluded users where required

5

Configure element, field, and page masking

6

Exclude sensitive or unnecessary content

7

Set recording and retention requirements

8

Save and publish the configuration

9

Generate a test session and verify its replay

Recording can be limited to selected applications, pages, users, environments, or conditions to control data volume and privacy exposure.

​
Configure User Identification

GermainUX can associate sessions with an application-provided user identifier when one is available and approved for collection. Use a stable, non-sensitive identifier such as:
  • Pseudonymous user ID
  • Internal support identifier
  • User role
  • Department
  • Region
  • Customer segment
  • SAP Commerce Cloud customer type
Do not collect passwords, authentication tokens, payment data, or unnecessary personal information. If no approved identifier is available, GermainUX can still analyze anonymous or pseudonymous sessions.

​
Configure Application Context

Add relevant attributes to make sessions easier to analyze, including:
  • SAP application
  • Environment
  • Fiori application or SAPUI5 view
  • Page or route
  • Business process
  • Process step
  • User role
  • Release or application version
  • SAP Commerce Cloud site
  • Device and browser
Consistent application context helps teams compare performance, errors, adoption, and process completion across user populations.

​
SAP Commerce Cloud Monitoring

For SAP Commerce Cloud, User Monitoring and Session Replay can capture the customer journey across:
  • Storefront entry
  • Navigation
  • Product search
  • Product listing
  • Product details
  • Product selection
  • Add to cart
  • Cart updates
  • Checkout
  • Payment interactions
  • Order confirmation
  • Account management
Configure business events for important activities such as:
  • Search submitted
  • No search results
  • Product viewed
  • Product added to or removed from cart
  • Checkout started
  • Checkout step completed
  • Checkout error
  • Order confirmed
GermainUX can analyze these events with errors, performance, abandonment, feedback, and Session Replay. Use authoritative server-side order data for confirmed orders and revenue reporting. Third-party or cross-origin checkout pages can be replayed only when GermainUX monitoring is permitted and deployed in that browser context.

​
Privacy Configuration

Configure privacy controls before enabling Session Replay in production. Mask or exclude:
  • Passwords
  • Authentication and security codes
  • Payment-card information
  • Personal or health information
  • Confidential business data
  • Hidden fields containing sensitive values
  • Authentication tokens
  • Sensitive URL parameters
  • Selected pages or application areas
Available controls can include:
  • Input masking
  • Text masking
  • Element exclusion
  • Page exclusion
  • Attribute filtering
  • URL and query-parameter filtering
  • User or group exclusion
  • Recording sampling
  • Role-based access
  • Data-retention limits
Test privacy rules against every application area included in monitoring.

​
Analyze User Activity

Use GermainUX dashboards to analyze:
  • Active and unique users
  • Session volume and duration
  • Pages and applications used
  • Features and workflows adopted
  • User-action response time
  • Errors affecting users
  • Slow or failed network requests
  • Business-process completion and abandonment
  • Repeated or inefficient actions
  • Frustration indicators
  • SAP Commerce Cloud search, cart, checkout, and conversion activity
  • Feedback associated with individual sessions
Segment results by application, environment, role, region, browser, device, release, or other configured attributes.

​
Investigate with Session Replay

Session Replay can help answer:
  • What was the user trying to accomplish?
  • Which actions occurred before an error?
  • Where did the process slow down or fail?
  • Did the user repeat an action?
  • Was navigation confusing or ineffective?
  • Which browser or network error affected the session?
  • Why was a business process abandoned?
  • What happened before negative feedback was submitted?
When available, correlate the replay with:
  • JavaScript and browser errors
  • Network requests
  • Application logs
  • API and integration performance
  • Infrastructure metrics
  • Business-process events
  • User feedback
  • Recent deployments
Cross-system correlation requires compatible timestamps and shared identifiers. GermainUX does not automatically create browser-to-ABAP execution traces.

​
Configure Alerts and Reports

Configure alerts or scheduled reports for conditions such as:
  • Increased user-facing errors
  • Abnormally slow user actions
  • Failed or abandoned business processes
  • Repeated frustration indicators
  • SAP Commerce Cloud cart or checkout failures
  • Declining conversion or feature adoption
  • Negative feedback
  • New application errors
Include links to relevant sessions, replays, dashboards, or error analyses when available.

​
Validation

After enabling monitoring:
1

Open the SAP application and complete a test process

2

Confirm that the session appears in GermainUX

3

Verify pages, views, and user actions

4

Confirm that errors and network requests are associated with the session

5

Open the Session Replay and validate the event sequence

6

Verify that sensitive fields and content are masked

7

Test included and excluded pages

8

Confirm that SAP Commerce Cloud events use the correct product, cart, and checkout context

9

Verify access permissions and retention settings

10

Confirm that alerts and reports reach the intended recipients

​
Troubleshooting

​
Sessions are not collected

Verify that:

​
Replay is incomplete

Check whether:
  • The interaction occurred in an unmonitored frame.
  • Cross-origin restrictions prevent access.
  • Recording started after the session began.
  • Sampling excluded part of the activity.
  • Privacy rules intentionally removed content.
  • The application uses unsupported rendering or protected content.

​
A user cannot be identified

Confirm that:
  • The application exposes an approved identifier.
  • The identifier is available when monitoring initializes.
  • Privacy rules do not remove it.
  • The correct UX Monitoring Profile is active.

​
Sensitive information appears in replay

Disable recording for the affected application area until the privacy configuration is corrected. Add the required masking or exclusion rule, test it, and verify previously collected data according to the organization’s security and retention procedures.

​
Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your SAP 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.