> ## 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. # Wix Operational Experience Intelligence > Monitor and optimize the availability, performance, user experience, conversion, and critical business workflows of Wix websites with GermainUX. 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 > **[Real User Monitoring](#real-user-monitoring)** > > Understand Wix visitor experience > **[Wix Bookings Monitoring](#wix-bookings-monitoring)** > > Verify confirmed booking outcomes > **[Advanced JavaScript Analysis](#advanced-javascript-analysis)** > > Profile deep browser issues > **[Alerts and Automation](#alerts-and-automation)** > > Respond to detected Wix conditions ## Overview Monitor and optimize the availability, performance, user experience, conversion, and critical business workflows of Wix websites with GermainUX. GermainUX combines Real User Monitoring, Session Replay, conversion analytics, customer-journey analysis, browser performance, JavaScript error monitoring, synthetic transactions, and integration monitoring to help teams identify issues affecting visitors and business outcomes. ![Wix Operational Experience Intelligence](https://mintcdn.com/germain-ux/aRWpCtnP62NYAs5c/images/main/wix-monitoring/workspaceoverview-conversion-ezgif.com-video-to-gif-converter.gif?s=f38d14ea6c95fd9ca10b69e2c2fe981a) ## Real User Monitoring Understand how real users experience your Wix website. GermainUX can monitor: * User sessions * Page views * Navigation * Clicks and interactions * Page-load performance * User interaction performance > **Show all 11** > > * Browser activity > * Network requests > * JavaScript errors > * Customer journeys > * Business workflows Analyze individual user experiences or aggregate activity across larger user populations. ## Session Replay GermainUX Session Replay reconstructs user activity across supported Wix pages. Use Session Replay to investigate: * Navigation issues * Dead clicks * Rage clicks * Error clicks * Repeated actions * Slow interactions > **Show all 10** > > * JavaScript errors > * Form issues > * Failed workflows > * Conversion abandonment Combine Session Replay with searchable events and analytics to locate sessions affected by a specific issue. ## Conversion Analysis Monitor the journeys that lead to important business outcomes. Examples include: Landing Page Product Cart Checkout Order Confirmation Campaign Landing Page Form Confirmation Service Booking Confirmation GermainUX can analyze: * Conversion rate * Funnel progression * Abandonment * Repeated actions * Errors * Performance delays * User friction * Revenue or other business impact when the required business data is available ## Customer Journey Analysis Analyze how visitors move through the Wix website. Depending on the Wix applications used, journeys can include: * Content discovery * Registration * Login * Forms * Wix Stores * Wix Bookings > **Show all 9** > > * Wix Events > * Member activity > * Lead generation Measure: * Completion * Duration * Drop-off * Repeated steps * Errors * Performance * Affected visitors ## Wix Stores Monitoring For customer-accessible Wix Stores pages and events, monitor journeys such as: Search Product View Add to Cart Checkout Order Confirmation Depending on the data available to customer JavaScript and authorized integrations, GermainUX can analyze: * Product views * Cart activity * Checkout initiation * Order confirmation * Conversion * Abandonment * Errors * Performance Platform-managed checkout or payment activity can only be monitored directly when Wix permits customer monitoring code to execute in that context. ## Transaction Performance Comparison When analyzing a slow or failed Wix transaction, use Comparison to compare its performance with another execution of the same transaction, such as the fastest, slowest, most recent, first seen, or last seen. Comparison can reveal: * Differences in execution time for the same Wix transaction * Which steps, checkout stages, or third-party integrations caused the slowdown * Performance differences between successful and failed Wix transactions * Errors or bottlenecks affecting Wix Stores and Bookings * Potential root causes of transaction performance degradation This helps pinpoint why a Wix transaction is slower or failing, identify the underlying bottlenecks, and accelerate resolution to improve conversion and visitor experience. More details on [**Transaction Performance Comparison**](https://docs.germainux.com/main/4-analysis-dashboard.md#comparison-of-bad-vs-good). ## Wix Bookings Monitoring Monitor supported booking journeys such as: Service View Date Selection Booking Start Booking Confirmation Analyze: * Booking progression * Completion * Abandonment * Errors * Performance delays * User friction Server-confirmed booking information should be used when available to validate the final business outcome. ## Wix Events Monitoring Monitor supported event-registration journeys such as: Event View Registration Payment Confirmation Analyze: * Registration progression * Completion * Drop-off * Errors * Performance * User friction ## Form Monitoring Monitor important Wix form workflows. For example: Open Form Enter Information Submit Confirmation Analyze: * Form start * Validation * Submission * Success * Failure * Abandonment * Errors * Performance ## Website Performance Monitor performance experienced by Wix visitors. Analyze: * Page-load time * Interaction response time * Browser processing * Resource loading * Network-request duration * API response time * Third-party service performance * Performance trends ## Error Monitoring Detect errors affecting visitors, including: * JavaScript errors * Browser console errors * HTTP errors * Failed network requests * Resource-loading failures * Third-party integration failures Errors can be correlated with users, sessions, pages, interactions, workflows, browsers, and devices. ## Mobile and Cross-Browser Experience Analyze Wix user experience across: * Desktop * Mobile * Tablet * Browser * Browser version * Operating system This helps identify issues affecting a specific user population rather than assuming a website-wide problem. ## Advanced JavaScript Analysis Use GermainUX JS Profiler when deeper browser troubleshooting is required. Analyze: * JavaScript exceptions * Browser console events * Slow or failed network requests * Third-party scripts * Browser freezes * Long-running JavaScript * Velo and other customer-controlled browser code * Client-side performance bottlenecks ## Wix API and Integration Monitoring GermainUX Engine can monitor customer-accessible Wix APIs, webhooks, and integrations. Depending on the available interfaces and permissions, monitor: * API availability * API response time * HTTP status * Response validation * Authentication failures * Webhook processing > **Show all 14** > > * Payment integrations > * Booking integrations > * Order integrations > * Registration integrations > * CRM integrations > * Marketing integrations > * Email and messaging services > * Customer-defined Velo endpoints Wix manages its underlying SaaS infrastructure. GermainUX cannot directly monitor Wix servers, databases, internal platform logs, or services that Wix does not expose. ## Synthetic Transactions Use GermainUX RPA Bot Recorder to proactively test important Wix journeys. Examples include: Open Website Navigate Verify Critical Page Open Website Submit Test Form Verify Confirmation Open Website Search Product Add to Cart Verify Cart Synthetic monitoring can detect functional or performance issues before real visitors encounter them. ## Third-Party and Platform-Managed Pages Some Wix journeys can move through: * Wix-managed pages * Third-party domains * Restricted iframes * External payment providers * External authentication providers GermainUX cannot directly monitor internal activity in these contexts unless the monitoring code is permitted to execute there. Where direct monitoring is unavailable, analyze available evidence such as: * Navigation into the external context * Return navigation * Redirect duration * Browser-visible success or failure * API responses * Webhooks * Integration data * Synthetic transaction results ## Root Cause Analysis GermainUX can correlate user-experience and technical telemetry. For example: Checkout Abandonment Slow Interaction Failed Third-Party Request or: Form Failure JavaScript Error API Failure or: Conversion Decrease Increased Page Response Time Affected Mobile Visitors This helps teams move from identifying an issue to understanding its likely cause and business impact. ## Analytics Analyze Wix monitoring data by: * User * Session * Page * URL * Interaction * Workflow > **Show all 14** > > * Browser > * Device > * Operating system > * Geography > * Error > * Network request > * Conversion status > * Time period ## Alerts and Automation Configure GermainUX to detect conditions such as: * Website unavailable * Slow page * Slow interaction * JavaScript error increase * Failed API request * Form failure > **Show all 10** > > * Booking failure > * Conversion degradation > * Synthetic transaction failure > * Third-party service degradation GermainUX can: * Send alerts * Notify users through Watches * Generate reports * Trigger approved diagnostics * Execute approved automation ## Additional Resources > **[Deploy Monitoring or automation for Wix](https://docs.germainux.com/main/deploy-monitoring-for-wix.md)** > > Read more > **[Configure](https://docs.germainux.com/main/configure-monitoring-for-wix.md)** > > Monitoring or automation for Wix > **[AI](https://docs.germainux.com/main/ai-driven-insights.md)** > > Insights & Recommendations > **[Analytics](https://docs.germainux.com/main/analytics.md)** > > More Analytics Features > **[Automation](https://docs.germainux.com/main/automation.md)** > > More Automation Features > **[Dashboards](https://docs.germainux.com/main/dashboard-and-report.md)** > > Dashboards and reports overview > **[Reports](https://docs.germainux.com/main/reporting-automatic.md)** > > Automatic and scheduled reports ## 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.