Skip to main content
ServiceAnalytics
Availability2014.1 or later

KPIs for Web User Experience

Core web experience metrics

Measures

Calculations for each KPI

Pivots

Segment by dimension

Combining KPIs, Measures and Pivots

Drill into sessions and replays
GermainUX provides preconfigured KPIs, pivots and measures for monitoring real user experience across web and native desktop applications. These analytics help teams understand what users experienced, where they encountered friction, how application behavior affected them, and which issues have the greatest impact on adoption, conversion or productivity. Preconfigured analytics can be used as provided or customized for your applications, workflows and business objectives. Watch the User Experience KPI overview.

What User Experience Analytics Help You Understand

GermainUX UX analytics can answer questions such as:

KPIs for Web User Experience

AI-Driven Session Insights

Frustration and Ineffective Interactions

User Interactions

Browser Health and Activity

Journey and Replay

UX-Level and Technology-Level Signals

Some KPIs describe what the user did or experienced, while others also expose an underlying technical condition. This distinction helps teams determine whether an issue should be addressed through design, content, workflow, application code, infrastructure—or a combination of these areas.

KPIs for Native Desktop User Experience

GermainUX also provides KPIs for monitoring user interactions in native operating-system and desktop applications. Native user activity can be correlated with application events, errors, performance and supporting Windows technology to explain what happened and why.

Measures

A measure is the numerical calculation applied to a KPI. Available measures depend on the selected KPI and its data model.

Session and Audience Measures

Engagement and Experience Measures

Drop-Off Measures

Statistical Measures

For duration, activity, errors, feedback, pages visited and other numerical values, GermainUX can calculate:
  • Minimum and maximum
  • Average and total
  • Standard deviation
  • 50th percentile
  • 90th percentile
  • 95th percentile
  • 99th percentile
  • 99.9th percentile
Percentiles reveal degraded experiences that averages may hide. For example, a satisfactory average duration can coexist with severe delays affecting the slowest 5% of users.

# Distinct Counts

GermainUX can count distinct values across available dimensions, including users, sessions, applications, pages, campaigns, referrers, browsers, devices, operating systems, systems, environments and geographic locations.

Pivots

A pivot segments KPI results by a selected dimension. The available pivots depend on the KPI, data model and captured context.

Application and Experience Pivots

  • Application name and component
  • Access method
  • Status and configured color
  • Drop-off state
  • Session and correlation IDs
  • End time and provenance

Page and Journey Pivots

  • Landing-page path, query and title
  • Exit-page path, query and title
  • Referrer URL, type and subtype
  • New or returning user
  • Campaign name, source, medium, content and term

Environment and Technology Pivots

  • Browser and browser family
  • Device and operating system
  • System name, type and environment
  • Target name, type, hostname and environment
  • Client or target city, region, country and continent

User and Organization Pivots

  • User
  • User role and type
  • User group and department
  • User city, region, country and continent
These pivots help identify whether friction is widespread or concentrated within a page, workflow, application, technology, audience or location.

Combining KPIs, Measures and Pivots

Teams can drill from an aggregate result into affected segments and individual sessions, then use Session Replay, event context and technical traces to understand root cause.

Filters

Filters narrow an analysis to the population, condition or time period relevant to the investigation. Filter options vary by KPI and captured data. Examples include:
  • Drop-off or non-drop-off sessions
  • New or returning users
  • Application, page or workflow
  • Browser, device or operating system
  • User group, role or location
  • Campaign or referrer
  • Status, severity or error category
  • Time range or environment

Analyze Drop-Offs

A drop-off occurs when a user abandons a page, journey or workflow before completing the intended action. GermainUX supports the following analysis workflow:
  • Quantify drop-offs at scale on an Aggregate Dashboard.
  • Identify the journey stage where users abandon through a Focused Flow or flow visualization.
  • Compare affected populations using pivots and filters.
  • Examine individual drop-offs on a Drill-through Dashboard.
  • Open the Analysis Dashboard to investigate leading factors, related signals and possible causes.
  • Replay relevant sessions to see what users experienced before abandoning.
This connects the drop-off rate with direct evidence of UX, workflow and technology friction.

Customize the Analytics

GermainUX can support custom:

Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

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.