Skip to main content

3. Configure Session Replay

Replay for store sessions

25. Configure Analysis Dimensions

Slice store activity by dimension

28. Configure Alerts and Watches

Alerts for store issues

30. Configure Dashboards

Store performance dashboards
Configure Monitoring for WooCommerce Configure GermainUX to analyze customer experience, conversion, cart and checkout activity, performance, errors, APIs, integrations, and supporting WooCommerce technology.

1. Open the UX Monitoring Profile

Go to: Germain Workspace > Settings > Analytics > UX Monitoring Profiles Select the UX Monitoring Profile created for the WooCommerce storefront.

2. Configure Real User Monitoring

Configure the telemetry required for the WooCommerce storefront. Depending on your monitoring scope, collect:
  • User sessions
  • Page views
  • Navigation
  • Clicks
  • Product interactions
  • Cart activity
  • Checkout activity
  • Browser performance
  • Network requests
  • JavaScript errors
  • Customer-defined events

3. Configure Session Replay

Configure Session Replay for the WooCommerce UX Monitoring Profile. Applicable settings can include:
  • Enable or disable Session Replay
  • Session timeout
  • Maximum recording duration
  • Session behavior when username changes
  • IP exclusions
  • Included IP ranges
  • Username exclusions
  • Bot and crawler exclusions
  • Headless-browser exclusions
Global settings are available under: Germain Workspace > Settings > System > UX and Session Replay Settings Configure appropriate:
  • Masking
  • Anonymization
  • Element exclusions
  • Page exclusions
  • Consent-dependent activation
  • Retention
  • Access control
Protect:
  • Passwords
  • Authentication tokens
  • Payment information
  • Names
  • Contact details
  • Billing addresses
  • Shipping addresses
  • Sensitive order information
  • Personal information
  • URL parameters containing identifiers

5. Configure Product Discovery Events

Configure relevant product-discovery events such as:
  • Landing-page view
  • Campaign entry
  • Search
  • Category view
  • Filter
  • Sort
  • Product-list view
  • Product selection
  • Product view
  • Variation selection
  • Review interaction
Event availability depends on:
  • WooCommerce version
  • Theme
  • Plugins
  • Storefront architecture
  • Browser-visible information

6. Configure Cart Events

Configure applicable cart events such as:
  • Add to cart
  • Remove from cart
  • Quantity update
  • Coupon application
  • Cart view
  • Cart abandonment
Use these events to analyze progression from product interest to checkout.

7. Configure Account Events

When applicable, configure:
  • Registration
  • Login
  • Logout
  • Password reset
  • Account access
Avoid collecting passwords or authentication secrets.

8. Configure Checkout Events

Configure browser-visible checkout events such as:
  • Checkout start
  • Customer-details entry
  • Shipping selection
  • Payment-method selection
  • Validation failure
  • Payment result
  • Order submission
  • Order confirmation
  • Checkout abandonment
Do not treat browser-only payment events as authoritative when server-confirmed transaction status is available.

9. Configure Purchase Confirmation

Use authoritative WooCommerce data when exact purchase confirmation is required. Depending on your architecture, this can come from:
  • WooCommerce REST API
  • Webhook
  • Database
  • Integration record
  • Server-side order status
Correlate this information with the browser customer journey where possible.

10. Configure Business Processes

Model important WooCommerce journeys as GermainUX business processes. Examples include:

Product Discovery

Search → Product View

Conversion

Product ViewAdd to CartCheckoutPaymentConfirmed Order

Account

Registration → Login

Coupon

CartApply CouponCheckout

Order Service

Account → Order Lookup

Return

Order → Return or Cancellation Request For each process, define:
  • Start
  • Milestones
  • Completion
  • Failure
  • Abandonment

11. Configure Conversion Analytics

Analyze:
  • Conversion rate
  • Completion rate
  • Funnel progression
  • Funnel drop-off
  • Time spent at each stage
  • Abandonment
  • Errors
  • Performance delays
  • Repeated actions
  • Customers affected
  • Revenue affected when available
Compare results by:
  • Device
  • Browser
  • Geography
  • Campaign
  • Product
  • Customer segment
  • Time period

12. Configure Click Monitoring

Monitor:
  • Standard clicks
  • Dead clicks
  • Error clicks
  • Rage clicks
Use these signals to identify:
  • Broken controls
  • Repeated customer attempts
  • Error-generating interactions
  • User frustration

13. Configure Performance Monitoring

Analyze:
  • Page-load time
  • Interaction response time
  • Browser processing
  • Network-request duration
  • WooCommerce API response time
  • Third-party response time
  • Checkout response time
Use baselines appropriate for each step rather than applying one threshold to every page.

14. Configure JavaScript Error Monitoring

Monitor:
  • JavaScript exceptions
  • Browser console errors
  • Failed network requests
  • Resource failures
  • Theme issues
  • Plugin issues
  • Third-party script failures
Correlate errors with:
  • Customer
  • Session
  • Product
  • Cart
  • Checkout
  • Conversion
  • Browser
  • Device

15. Configure WooCommerce REST API Monitoring — Optional

When Engine monitoring is deployed, configure approved REST API monitoring. Depending on permissions, configure:
  • Endpoint
  • HTTP method
  • Authentication
  • Headers
  • Request parameters
  • Timeout
  • Expected HTTP status
  • Response validation
  • Monitoring frequency
Use only permissions required by the monitoring use case.

16. Configure Webhook Monitoring — Optional

Monitor important WooCommerce webhook flows. Analyze: Examples include webhooks associated with:

17. Configure WordPress and WooCommerce Application Monitoring — Optional

Depending on the hosting environment, configure monitoring for:

18. Configure Database Monitoring — Optional

When MySQL or MariaDB monitoring is available, analyze: Correlate database conditions with storefront and checkout performance.

19. Configure Log Monitoring — Optional

Configure log monitoring for relevant accessible logs. Examples include: Create parsing and alert rules appropriate for each log source.

20. Configure Infrastructure Monitoring — Optional

When hosting access is available, monitor: Use infrastructure telemetry to identify capacity or resource conditions affecting WooCommerce.

21. Configure JS Profiler — Optional

Use JS Profiler when deeper browser troubleshooting is required. Analyze:

22. Configure Synthetic Monitoring — Optional

Configure synthetic WooCommerce scenarios created with GermainUX RPA Bot Recorder. Configure: Avoid uncontrolled production purchases or real charges.

23. Configure KPIs

Configure KPIs appropriate for the WooCommerce monitoring objective. Depending on enabled features, these can include: Use only KPIs available in the installed GermainUX version.

24. Configure Measures

Measures can include:

25. Configure Analysis Dimensions

Analyze WooCommerce activity by:

26. Configure SLAs

Configure thresholds appropriate for the storefront and customer journey. Examples:

Availability

Storefront Availability < Expected SLA

Page Performance

Page Load Time > Threshold

Checkout Performance

Checkout Response Time > Threshold

JavaScript Errors

JavaScript Error Rate > Threshold

APIs

Critical WooCommerce API Response Time > Threshold

Conversion

Conversion Rate < Expected Threshold

Checkout

Checkout Failure Rate > Expected Threshold

Synthetic Monitoring

Critical Shopping Scenario = Failed

27. Configure Rules and Automated Analysis

Create Rules such as: Slow Checkout + Conversion Decrease JavaScript Error + Cart Abandonment Payment Failure + Checkout Abandonment API Degradation + Failed Orders Database Slowness + Slow Checkout Plugin Error + Affected Customers Third-Party Service Degradation + Revenue Impact

28. Configure Alerts and Watches

Examples include: Storefront Unavailable → Alert Operations Checkout Failure Rate Increasing → Notify eCommerce Team Payment Integration Failure → Alert Integration Team Conversion Drop → Notify Digital Team JavaScript Error Increase → Notify Engineering Database Performance Degradation → Notify Application and Database Teams Synthetic Checkout Failure → Alert Support GermainUX can trigger:

29. Configure Maintenance Windows

Define maintenance windows for: Suppress expected alerts during approved maintenance activity.

30. Configure Dashboards

Conversion Dashboard

Monitor:

Customer Experience Dashboard

Monitor:

Checkout Dashboard

Monitor:

Engineering Dashboard

Monitor:

31. Validate the Configuration

Verify:
1

Customer sessions are captured

2

Product events are captured

3

Cart events are captured

4

Checkout events are captured

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.