> ## 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 Webflow

> Configure how GermainUX monitors, analyzes, and alerts on user experience, performance, errors, forms, and workflows on a Webflow website.

Components
[`Engine`](/main/germain-ux-engine)
[`JS Profiler`](/main/germain-ux-js-profiler)
[`Mobile App`](/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](/main/germain-ux-rpa-bot-recorder)
[`RUM JS`](/main/germain-ux-rum-js)

Availability
2017.2

> **[2. Configure Real User Monitoring](#2-configure-real-user-monitoring)**
>
> Choose browser telemetry to collect

> **[3. Configure Session Replay](#3-configure-session-replay)**
>
> Replay checks before rollout

> **[9. Configure Conversion Monitoring](#9-configure-conversion-monitoring)**
>
> Define website conversion events

> **[22. Configure Dashboards](#22-configure-dashboards)**
>
> Dashboards for each audience

**Configuring Monitoring for User Experience and Performance on Webflow with GermainUX**

Configure how GermainUX monitors, analyzes, and alerts on user experience, performance, errors, forms, network activity, and business workflows across a Webflow website.

## 1 Open the UX Monitoring Profile

Go to:

**Germain Workspace > Left Menu > Analytics > UX Monitoring Profiles**

Select the UX Monitoring Profile created by the Webflow Wizard.

Use this profile to configure the applicable Real User Monitoring and Session Replay behavior.

## 2. Configure Real User Monitoring

Configure the browser telemetry required for your monitoring objectives.

Depending on the configuration, GermainUX can collect:

* User sessions
* Page views
* Navigation
* Clicks
* User interactions
* Page performance

> **Show all 11**
>
> * Browser performance
> * Network requests
> * HTTP errors
> * JavaScript errors
> * Customer-defined events

Enable only the telemetry required for your monitoring use cases.

## 3. Configure Session Replay

Configure Session Replay for the Webflow UX Monitoring Profile.

Depending on your GermainUX version and global settings, configure:

* Session Replay enabled or disabled
* Session timeout
* Recording behavior
* Privacy exclusions
* IP exclusions
* Included IP ranges
* Excluded usernames
* Headless-browser exclusion

Validate the resulting replay before production rollout.

* Session Replay enabled or disabled
* Session timeout
* Recording behavior
* Privacy exclusions
* IP exclusions
* Included IP ranges
* Excluded usernames
* Headless-browser exclusion

## 4. Configure Privacy and Sensitive Data Protection

Review information captured from the Webflow website.

Configure masking or exclusions for sensitive information such as:

* Form values
* Names
* Email addresses
* Phone numbers
* Authentication data
* Payment-related information
* Customer-defined sensitive fields

Collect only information required for the monitoring use case.

## 5. Configure Click Monitoring

GermainUX can analyze click behavior such as:

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

Use these signals to identify:

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

Analyze these events together with Session Replay and performance telemetry.

## 6. Configure Performance Monitoring

Configure performance analysis for:

* Page-load time
* User interaction time
* Browser processing
* Network-request duration
* API response time
* Third-party service response time

Use thresholds appropriate for the normal behavior of each page or workflow.

## 7. Configure Error Monitoring

Configure analysis of:

| Error Type |   |
| - | - |
|   | Ja |
| Browser errors |   |
| HTTP errors |   |
| Failed network requests |   |
| Resource-loading failures |   |

Analyze errors together with:

* User
* Session
* Page
* Interaction
* Workflow
* Browser
* Device

## 8. Configure Form Monitoring

For important Webflow forms, define the interaction and workflow events required to determine whether users can successfully complete them.

Examples include:

Open Form
Enter Information
Submit
Confirmation

Monitor:

* Form interaction
* Submission attempt
* Errors
* Network request
* Response time
* Completion
* Abandonment

When available, define the confirmation condition that indicates successful completion.

## 9. Configure Conversion Monitoring

Define the events that represent conversions on the Webflow website.

Examples include:

### Lead Generation

Landing Page
Service Page
Form
Confirmation

### Contact Request

Content
Contact Page
Form Submission

### Registration

Landing Page
Registration
Confirmation

Configure:

* Funnel entry
* Intermediate steps
* Conversion
* Abandonment
* Failure

This enables analysis of conversion and friction across sessions and user populations.

## 10. Configure Customer Journeys

Define important visitor journeys beyond individual forms.

Examples:

Homepage
Product
Pricing
Contact

Campaign Landing Page
Content
Call to Action
Conversion

Analyze:

* Journey progression
* Duration
* Repeated steps
* Abandonment
* Errors
* Slow interactions
* User friction

## 11. Configure Mobile and Browser Analysis

Analyze experience by:

* Desktop
* Mobile
* Tablet
* Browser
* Browser version
* Operating system
* Screen or device characteristics available to the monitoring component

Use this analysis to identify issues affecting a specific population rather than assuming a website-wide problem.

## 12. Configure Network and Third-Party Monitoring

Analyze browser requests made by the Webflow site.

Depending on the available data, monitor:

* Request URL
* Request duration
* HTTP status
* Failed request
* API
* Third-party provider
* Interaction associated with the request

This can help identify problems associated with customer-controlled or third-party dependencies.

## 13. Configure JS Profiler — Optional

When deeper JavaScript analysis is required, configure GermainUX JS Profiler.

Use profiling to investigate:

* Slow JavaScript execution
* Browser processing
* Network activity
* Integration activity
* Slow interactions

Use profiling selectively where additional technical detail is required.

## 14. Configure Synthetic Monitoring — Optional

Use GermainUX RPA Bot Recorder to configure synthetic Webflow scenarios.

Examples:

Open Website
Navigate
Verify Critical Page

Open Website
Submit Test Form
Verify Confirmation

Configure:

* Scenario
* Monitoring location
* Schedule
* Timeout
* Expected result
* Failure conditions
* Alerting

Use safe test scenarios and dedicated test data where appropriate.

## 15. Configure REST API Monitoring — Optional

When Webflow REST API monitoring is required, configure the GermainUX Engine with the approved endpoint and authentication.

Configure:

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

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

Use read-only API calls when possible.

## 16. Configure KPIs

Configure KPIs appropriate for the Webflow monitoring objectives.

Depending on the configuration, these can include:

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

Use KPIs available in your GermainUX version.

## 17. Configure Measures

Measures can include:

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

> **Show all 16**
>
> * Error rate
> * Page-load time
> * Interaction time
> * Network-request duration
> * Form submissions
> * Form completion rate
> * Conversion count
> * Conversion rate
> * Abandonment rate
> * Workflow duration

## 18. Configure Analysis Dimensions

Analyze Webflow activity by dimensions such as:

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

> **Show all 18**
>
> * Interaction
> * Form
> * Workflow
> * Browser
> * Device
> * Operating system
> * Geography
> * Error
> * API
> * Third-party provider
> * Conversion status
> * Time period

## 19. Configure SLAs

Configure thresholds for conditions requiring attention.

Examples include:

### Availability

`Website Availability < Expected SLA`

### Performance

`Page Load Time > Threshold`

### JavaScript

`JavaScript Error Rate > Threshold`

### Network

`Critical Request Response Time > Threshold`

### Form

`Form Completion Rate < Expected Threshold`

### Conversion

`Conversion Rate < Expected Threshold`

### Synthetic Monitoring

`Critical Scenario = Failed`

Use environment- and workflow-specific thresholds.

## 20. Configure Rules

Use GermainUX Rules for conditions requiring more advanced analysis.

Examples:

**JavaScript Error + Form Abandonment**

**Slow Page + Conversion Decrease**

**Rage Click + No Navigation**

**Failed Third-Party Request + Affected Users**

**Slow Network Request + Slow User Interaction**

Rules can combine technical, user-experience, and business signals.

## 21. Configure Alerts and Watches

Configure notifications for conditions requiring attention.

Examples:

**Website Unavailable → Alert Operations**

**Form Submission Failure → Notify Website Team**

**JavaScript Error Increase → Notify Engineering**

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

**Synthetic Transaction Failure → Alert Support**

GermainUX can trigger:

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

## 22. Configure Dashboards

Create dashboards appropriate for the audience.

### Website Operations

Monitor:

* Availability
* Page performance
* Errors
* Network requests
* Third-party services

### User Experience

Monitor:

* Sessions
* User interactions
* Dead clicks
* Rage clicks
* Error clicks
* Session Replay
* Mobile and browser experience

### Conversion

Monitor:

* Funnel progression
* Form completion
* Conversion rate
* Abandonment
* User friction

### Engineering

Monitor:

* JavaScript errors
* JS Profiler data
* HTTP failures
* Slow network requests
* Third-party failures

## 23. Validate the Configuration

Current Webflow implementation matches the workflow definition.

## JavaScript Errors Are Missing

Verify:

* RUM JS is active.
* The error occurs in the monitored browser context.
* Error monitoring is enabled.
* Filtering or privacy settings do not suppress the event.

Verify:

* RUM JS is active.
* The error occurs in the monitored browser context.
* Error monitoring is enabled.
* Filtering or privacy settings do not suppress the event.

## Third-Party Request Is Missing

Verify:

* The request originates from the browser.
* Network monitoring is enabled.
* Filtering rules are not excluding the request.
* Browser security restrictions do not prevent the required visibility.

## Get More Information

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

[Contact GermainUX Support](/main/support.md).

## Get Help

> **[Contact GermainUX Support](/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.