> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Monitoring for Wix

> Configure how GermainUX monitors, analyzes, and alerts on user experience, performance, customer journeys, conversions, and errors across Wix websites.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)
[`RUM Windows`](https://docs.germainux.com/main/germainux-rum-windows)
[`Agent`](https://docs.germainux.com/main/germainux-agent)

Availability
2017.2

> **[3. Configure Session Replay](#3-configure-session-replay)**
>
> Replay settings and globals

> **[8. Configure Customer Journeys](#8-configure-customer-journeys)**
>
> Journeys as business processes

> **[20. Configure Dashboards](#20-configure-dashboards)**
>
> Audience-specific dashboards

> **[21. Validate the Configuration](#21-validate-the-configuration)**
>
> Test on the live site

**Configuring Monitoring for User Experience on Wix Websites**

Configure how GermainUX monitors, analyzes, and alerts on user experience, performance, customer journeys, conversions, errors, and integrations across Wix websites.

## 1 Open the UX Monitoring Profile

Go to:

**Germain Workspace > Settings > Analytics > UX Monitoring Profiles**

Select the UX Monitoring Profile created for the Wix website.

## 2. Configure Real User Monitoring

Configure the browser telemetry required for the website.

Depending on the configuration, GermainUX can collect:

| | Telemetry |
| - | - |
| 1 | User sessions |
| 2 | Page views |
| 3 | Navigation |
| 4 | Clicks |
| 5 | User interactions |
| 6 | Page performance |
| 7 | Browser performance |
| 8 | Network requests |
| 9 | JavaScript errors |
| 10 | Customer-defined events |

Enable only the telemetry required for your monitoring objectives.

## 3. Configure Session Replay

Enable or disable Session Replay for the Wix UX Monitoring Profile.

Configure applicable settings such as:

* Session timeout
* Maximum recording duration
* Session behavior when username
* Maximum recording duration
* Session behavior when username changes
* IP exclusions

> **Show all 9**
>
> * Included IP ranges
> * Username exclusions
> * Headless-browser exclusion

Global Session Replay settings are available under:

**Germain Workspace > Settings > System > UX and Session Replay Settings**

## 4. Configure Privacy

Configure masking, anonymization, or exclusions according to the website's privacy requirements.

Protect:

* Standard clicks
* Dead clicks
* Error clicks
* Rage clicks

Validate the resulting Session Replay before production rollout.

## 5. Configure Click Monitoring

Analyze:

* Standard clicks
* Dead clicks
* Error clicks
* Rage clicks

Use these signals to identify:

* Unresponsive elements
* Repeated attempts
* JavaScript failures
* Navigation problems
* User frustration

## 6. Configure Performance Monitoring

Analyze:

* Page-load time
* Interaction response time
* Browser processing
* Resource loading
* Network-request duration
* API response time
* Third-party response time

Configure thresholds according to normal website behavior.

## 7. Configure Error Monitoring

Monitor:

* JavaScript errors
* Browser console errors
* HTTP failures
* Failed network requests
* Resource-loading failures
* Integration failures

Analyze errors by user, session, page, browser, device, and workflow.

## 8. Configure Customer Journeys

Define important Wix journeys as GermainUX business processes.

Examples:

### Lead Generation

Campaign
Landing Page
Form
Confirmation

### Wix Stores

Search
Product
Cart
Checkout
Order Confirmation

### Wix Bookings

Service
Date
Booking
Confirmation

### Wix Events

Event
Registration
Payment
Confirmation

For each journey, define:

* Start
* Milestones
* Completion
* Failure
* Abandonment

Analyze:

* Completion rate
* Duration
* Drop-off
* Repeated actions
* Errors
* Performance delays
* Affected visitors
* Business impact

## 9. Configure Conversion Monitoring

Define the events representing the website's important conversions.

Examples include:

* Lead submitted
* Registration completed
* Booking completed
* Event registration completed
* Order confirmed
* Other customer-defined conversion

Analyze:

* Conversion count
* Conversion rate
* Funnel progression
* Abandonment
* Errors
* User friction
* Performance impact

Use server-confirmed data when available for authoritative payment, order, booking, or registration completion.

## 10. Configure Network and Integration Monitoring

Analyze browser-visible requests to:

* Wix services
* APIs
* Payment services
* Authentication providers
* CRM systems
* Marketing platforms

> **Show all 9**
>
> * Email services
> * Third-party integrations
> * Customer-defined endpoints

Monitor:

* Response time
* HTTP status
* Failure
* User interaction associated with the request

## 11. Configure API and Webhook Monitoring — Optional

When GermainUX Engine monitors customer-accessible Wix interfaces, configure:

* Endpoint
* HTTP method
* Authentication
* Headers
* Request parameters
* Timeout

> **Show all 9**
>
> * Expected HTTP status
> * Response validation
> * Monitoring frequency

For webhooks, configure monitoring around the customer-accessible delivery or processing point.

## 12. Configure JS Profiler — Optional

Use GermainUX JS Profiler when deeper browser analysis is required.

Analyze:

* JavaScript execution
* Exceptions
* Browser console events
* Slow functions
* Long-running JavaScript
* Network requests

> **Show all 9**
>
> * Third-party scripts
> * Browser freezes
> * Velo browser code

## 13. Configure Synthetic Monitoring — Optional

Configure synthetic Wix workflows created with RPA Bot Recorder.

Configure:

* Scenario
* Execution location
* Schedule
* Credentials
* Timeout
* Validation steps

> **Show all 9**
>
> * Failure conditions
> * Alerts
> * Maintenance windows

Use controlled test accounts and data.

## 14. Configure KPIs

Configure KPIs relevant to the Wix monitoring objectives.

Depending on the enabled monitoring, these can include:

* User Session
* User Interaction
* Page Performance
* JavaScript Error
* HTTP Request
* Business Process
* Conversion
* Synthetic Transaction

Use the KPIs available in the installed GermainUX version.

## 15. Configure Measures

Measures can include:

* Users
* Sessions
* Page views
* Interactions
* Clicks
* Errors

> **Show all 15**
>
> * Error rate
> * Page-load time
> * Interaction time
> * Network-request duration
> * Workflow duration
> * Completion rate
> * Abandonment rate
> * Conversion count
> * Conversion rate

## 16. Configure Analysis Dimensions

Analyze Wix activity by:

* Application
* Environment
* User
* Session
* Page
* URL

> **Show all 18**
>
> * Interaction
> * Workflow
> * Browser
> * Browser version
> * Device
> * Operating system
> * Geography
> * Error
> * API
> * Integration
> * Conversion status
> * Time period

## 17. Configure SLAs

Configure thresholds appropriate for each website and workflow.

Examples:

### Availability

`Website Availability < Expected SLA`

### Performance

`Page Load Time > Threshold`

### Interaction

`Interaction Response Time > Threshold`

### Errors

`JavaScript Error Rate > Threshold`

### Integration

`Critical API Response Time > Threshold`

### Business Process

`Completion Rate < Expected Threshold`

### Conversion

`Conversion Rate < Expected Threshold`

### Synthetic Monitoring

`Critical Scenario = Failed`

## 18. Configure Rules and Automated Analysis

Create Rules that combine technical, user-experience, and business signals.

Examples:

**Slow Page + Conversion Decrease**

**JavaScript Error + Checkout Abandonment**

**Rage Click + No Navigation**

**Failed API Request + Booking Failure**

**Slow Third-Party Service + Affected Visitors**

**Error Increase + Conversion Decrease**

## 19. Configure Alerts and Watches

Configure notifications for conditions requiring attention.

Examples:

**Website Unavailable → Alert Operations**

**JavaScript Errors Increasing → Notify Engineering**

**Booking Failures → Notify Digital Team**

**Checkout Failures → Notify eCommerce Team**

**Conversion Decrease + Increased Errors → Notify Digital and Engineering Teams**

**Synthetic Transaction Failure → Alert Support**

GermainUX can trigger:

* Alerts
* Watches
* Reports
* Approved diagnostics
* Approved automation

## 20. Configure Dashboards

Create dashboards appropriate for each audience.

### User Experience

Monitor:

* Users
* Sessions
* Interactions
* Dead clicks
* Rage clicks
* Error clicks
* Session Replay

### Performance

Monitor:

* Page performance
* Interaction performance
* JavaScript errors
* Network requests
* Third-party services

### Conversion

Monitor:

* Funnel progression
* Conversion
* Abandonment
* User friction
* Errors
* Performance impact

### Wix Stores

Monitor:

* Product journeys
* Cart activity
* Checkout progression
* Order confirmation
* Conversion

### Wix Bookings and Events

Monitor:

* Journey progression
* Completion
* Abandonment
* Errors
* Performance

## 21. Validate the Configuration

Perform representative activity on the published Wix website and verify:

**1. Sessions are created**

**2. Pages are captured**

**3. Navigation is captured**

**4. User interactions are captured**

**5. Click monitoring works as expected**

**6. Performance data is available**

**7. JavaScript errors are detected**

**8. Network requests are captured as configured**

**9. Session Replay works when enabled**

**10. Sensitive information is protected**

**11. Customer journeys are reconstructed correctly**

**12. Conversion events are correctly identified**

**13. API monitoring works when configured**

**14. Synthetic transactions execute correctly**

**15. SLAs evaluate correctly**

**16. Alerts and Watches operate as expected**

> [!NOTE]
>
> This section provides troubleshooting steps for common issues.

## Troubleshooting — No Monitoring Data

Verify:

* Wix site was published after adding the custom code.
* Correct RUM JS snippet was deployed.
* Custom code is assigned to the required pages.
* Code loads in the page Head.
* Browser requests to GermainUX are not blocked.
* Consent configuration permits monitoring.
* User or IP exclusions do not exclude the test.

## Troubleshooting — Some Wix Pages Are Missing

Verify:

* Custom code is assigned to those pages.
* Wix permits custom code in that browser context.
* Page is not hosted in a restricted iframe or platform-managed context.

## Troubleshooting — Checkout Activity Is Incomplete

Determine whether the checkout or payment step is:

* Wix-managed
* Third-party hosted
* In a restricted iframe

Use API, webhook, integration, or server-confirmed data where direct browser monitoring is unavailable.

## Troubleshooting — Session Replay Is Incomplete

Check:

* Wix page transitions
* Restricted iframes
* Dynamically embedded applications
* Masking
* Exclusions
* Consent configuration

## Troubleshooting — Duplicate Sessions or Events

Verify that RUM JS is deployed only once and is not also injected through another integration or tag manager.

## Troubleshooting — API Monitoring Fails

Verify:

* Endpoint
* Authentication
* Credentials
* Network access
* HTTP method
* Request
* Expected response
* Engine availability

## Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Wix environment.

[Contact GermainUX Support](https://docs.germainux.com/main/support.md).

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.