Configure Monitoring for Webflow

⚙️ 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:

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:

Validate the resulting replay before production rollout.

🔒 4. Configure Privacy and Sensitive Data Protection

Review information captured from the Webflow website.

Configure masking or exclusions for sensitive information such as:

Collect only information required for the monitoring use case.

🖱️ 5. Configure Click Monitoring

GermainUX can analyze click behavior such as:

Use these signals to identify:

Analyze these events together with Session Replay and performance telemetry.

🚤 6. Configure Performance Monitoring

Configure performance analysis for:

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

🐛 7. Configure Error Monitoring

Configure analysis of:

Analyze errors together with:

📋 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:

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:

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:

📱 11. Configure Mobile and Browser Analysis

Analyze experience by:

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:

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:

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:

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:

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:

Use KPIs available in your GermainUX version.

📏 17. Configure Measures

Measures can include:

🔎 18. Configure Analysis Dimensions

Analyze Webflow activity by dimensions such as:

⏰ 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:

📊 22. Configure Dashboards

Create dashboards appropriate for the audience.

🖥️ Website Operations

Monitor:

👥 User Experience

Monitor:

🏆 Conversion

Monitor:

🧰 Engineering

Monitor:

✅ 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.