Deploy Monitoring for Wix

⚙️ Deploy Monitoring for Wix

Deploy GermainUX monitoring on Wix to capture real-user experience, Session Replay, customer journeys, conversions, performance, browser errors, user feedback, and third-party service activity.

GermainUX can also execute synthetic scenarios and monitor customer-accessible Wix APIs, webhooks, and integrations.

📋 Select the Required Deployment

📋 Prerequisites

• An authorized Wix administrator can manage custom code and publish the website.

• The Wix plan and site configuration support custom JavaScript.

• The GermainUX environment is accessible through HTTPS.

• Visitor browsers can download RUM JS and send monitoring data to GermainUX.

• Wix permits custom code on the pages that need to be monitored.

• Consent requirements have been defined.

• Sensitive pages, fields, URLs, and user attributes have been identified.

• Required GermainUX domains and connections are authorized.

1️⃣ Open the Wix Wizard

Go to:

Germain Workspace > Left Menu > Settings > Wizards > Wix

Start the Wix Wizard.

2️⃣ Configure the Wix Application

Configure the required application information, including:

• Application Name

• Website URL

• Environment

• UX Monitoring Profile

• Privacy configuration

• Bot and crawler handling

• Allowed domains

The Website URL should identify the published Wix website using HTTPS.

3️⃣ Complete the Wizard

Complete the Wizard and obtain the generated GermainUX RUM JS snippet.

Use the snippet generated specifically for the customer's:

• GermainUX environment

• Wix application

• UX Monitoring Profile

Do not use a generic or example monitoring URL in production.

4️⃣ Deploy RUM JS in Wix

Sign in to Wix as an authorized administrator.

Select the website to monitor and open the website settings.

Open:

Custom Code

under the applicable advanced or developer settings.

Then:

1. Select Add Custom Code.

2. Paste the RUM JS snippet generated by GermainUX.

3. Enter a recognizable name such as GermainUX RUM.

4. Configure the code to load in the Head.

5. Apply it to all supported pages that must be monitored.

6. Select the option that loads the code once per page when available.

7. Save the configuration.

8. Publish the Wix website.

The exact Wix administration labels can vary by site type and Wix interface version.

5️⃣ Select the Monitored Pages

Apply RUM JS to supported pages involved in important visitor journeys, including:

• Home and landing pages

• Content and service pages

• Search results

• Forms

• Registration and login

• Member pages

• Booking pages

• Event-registration pages

• Product and collection pages

• Cart

• Customer-controlled checkout pages

• Confirmation and success pages

Do not deploy monitoring to sensitive or restricted pages until privacy and security controls have been validated.

Account for Wix-Managed Pages

Wix can prevent customer code from running in certain:

• Platform-managed pages

• Payment interfaces

• Applications

• Cross-origin iframes

RUM JS cannot directly monitor these contexts unless Wix permits the monitoring code to execute there.

Configure alternative evidence when appropriate, including:

• Entry and return navigation

• Browser-visible success or failure

• API responses

• Webhooks

• Integration data

• Synthetic transaction results

🔒 Configure Consent

Coordinate GermainUX monitoring with the site's consent configuration.

Depending on organizational requirements, configure RUM JS to:

• Start after required consent is granted

• Respect consent withdrawal

• Avoid starting when applicable consent is rejected

• Apply appropriate rules by geography or website

• Avoid collecting visitor identifiers before authorization

Test monitoring with consent:

• Accepted

• Rejected

• Withdrawn

🛡️ Configure Privacy Before Production

Before enabling Session Replay in production, configure appropriate masking, anonymization, and exclusions.

Protect information such as:

• Passwords

• Authentication tokens

• Payment information

• Names

• Contact information

• Addresses

• Account information

• Sensitive form fields

• URL parameters containing identifiers

• Restricted member content

• Regulated information

Also configure appropriate retention and access controls.

6️⃣ Configure Wix Events

After RUM JS is collecting data, configure the events required for customer-journey and conversion analysis.

Examples include:

🌐 General Website

• Page view

• Navigation

• Call-to-action click

• Content interaction

• File download

📝 Forms

• Form start

• Validation

• Submission

• Success

• Failure

👥 Member Area

• Registration

• Login

• Account access

• Target activity

📅 Wix Bookings

• Service view

• Date selection

• Booking start

• Booking confirmation

🎫 Wix Events

• Event view

• Registration start

• Payment

• Confirmation

🛒 Wix Stores

• Search

• Product view

• Add to cart

• Remove from cart

• Checkout start

• Order confirmation

Event availability depends on the Wix application, page structure, browser context, and information exposed to customer JavaScript.

⚙️ 10. Deploy API and Integration Monitoring — Optional

Deploy a GermainUX Engine when monitoring needs to extend to customer-accessible Wix APIs, webhooks, or integrations.

Depending on the available interfaces, monitor:

• API availability

• Response time

• HTTP status

• Response validation

• Authentication

• Webhooks

• Payment integrations

• Booking integrations

• Order integrations

• CRM integrations

• Marketing integrations

• Email and messaging

• Customer-defined Velo endpoints

Wix's private infrastructure is outside the monitoring boundary unless Wix exposes an authorized interface.

🔧 11. Deploy JS Profiler — Optional

Deploy GermainUX JS Profiler on selected diagnostic browsers when deeper analysis is required.

Use it for:

• JavaScript exceptions

• Browser console events

• Slow network requests

• Failed network requests

• Third-party scripts

• Browser freezes

• Long-running JavaScript

• Velo browser code

• Client-side performance bottlenecks

JS Profiler is normally used on selected administrator, QA, development, or support browsers rather than every public visitor browser.

🤖 12. Deploy Synthetic Monitoring — Optional

Use GermainUX RPA Bot Recorder to record representative Wix scenarios.

Examples include:

• Open website

• Navigate to critical page

• Search for content or products

• Submit test form

• Register or sign in

• Book a service

• Register for an event

• Add product to cart

• Begin checkout

• Complete an approved test transaction

• Verify expected result

Deploy the recorded scenario through a GermainUX Engine.

Use controlled test accounts, products, bookings, payment methods, and cleanup procedures for production scenarios.

✅ 13. Validate the Deployment

After publishing the website:

1. Open it in a supported browser.

2. Confirm that RUM JS loads.

3. Confirm that monitoring requests reach GermainUX.

4. Navigate through representative pages.

5. Perform representative user actions.

6. Verify sessions, pages, clicks, events, errors, and performance data.

7. Open Session Replay.

8. Verify that sensitive information is protected.

9. Test consent behavior.

10. Validate desktop and mobile layouts.

11. Test synthetic transactions when enabled.

12. Test API monitoring when enabled.

13. Verify alerts when configured.

Once deployment is validated, continue with Configure Monitoring for Wix.

ℹ️ Get More Information

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

Contact GermainUX Support.