Features
A drop-off occurs when a user abandons a page, feature, or workflow before completing their intended action.
It represents intent interrupted, whether the intent was to buy, explore, or use.
Drop-offs are essential for understanding both conversion and adoption behaviors.
Types of Drop-Offs
|
Type |
Typical Users |
Definition |
Example |
Main Insight |
|
Conversion Drop-Off |
Visitors, customers |
Abandon a revenue-related goal |
Leaves /checkout before payment |
Lost sales / revenue leakage |
|
Adoption Drop-Off |
Employees, logged-in users |
Abandon a workflow or feature mid-use |
CRM user quits before “Submit Quote” |
Poor feature adoption or UX friction |
|
Engagement Drop-Off |
Visitors or users |
Stop exploring deeper content |
Lands on dashboard but doesn’t open reports |
Low engagement depth |
|
Exploration Drop-Off |
First-time or low-intent visitors |
Exit immediately after arrival |
Visit home page and leave after one click |
Weak first impression / relevance issue |
Core Metrics
To analyze drop-offs effectively, GermainUX standardizes two complementary measures:
|
Metric |
Formula |
Meaning |
Use Case |
|
Drop-Off Share |
dropoffs_in_segment / total_dropoffs_on_page |
How much this segment contributes to all exits |
Identify which performance range or cohort drives most drop-offs |
|
Drop-Off Rate |
dropoffs_in_segment / sessions_in_segment |
Probability that a user in this segment will drop off |
Quantify risk per user experience type |
Example
16 drop-offs among 56 sessions (26 total drop-offs):
-
Share = 61.5 % (
100 * 16 / 26) → Impact among all exits -
Rate = 28.6 % (
100 * 16 / 56)→ Risk among users
Share = where most drop-offs happen.
Rate = how risky that experience is.
Why It Matters
|
Context |
Business Value |
|
Conversion Drop-Offs |
Reveal where revenue leaks occur and what performance issues drive abandonment |
|
Adoption Drop-Offs |
Show where employees or customers give up mid-task, guiding UX and process optimization |
|
Unified Drop-Off Analytics |
Enables GermainUX to correlate UX, performance, and process friction under one framework |
Example of a GermainUX Portlet
Service: Analytics
Feature Availability: 2025.2 or later