Overview
The Broken Navigations section highlights instances where user navigation failed to complete successfully. This can indicate issues such as missing pages, incorrect routing, or disrupted user flows.
Tracking broken navigations helps identify friction points in the user journey and uncover potential technical or configuration problems that impact user experience.
Metrics Explained
1. Broken Navigations (Total)
This metric represents the total number of navigation attempts that failed within the selected time period.
Use this when you want to:
Measure the overall volume of navigation failures
Identify spikes or anomalies in system behavior
Correlate failures with deployments, releases, or outages
2. Broken Navigations Rate
This metric shows the percentage of broken navigations out of all navigation attempts.
Formula:
Broken Navigations Rate = (Broken Navigations / Total Navigations) × 100
Use this when you want to:
Understand the relative impact of navigation failures
Compare performance across different time periods or segments
Evaluate improvements or regressions independent of traffic volume
Common Causes of Broken Navigations
Broken navigations can occur due to a variety of reasons, including:
Missing or unavailable pages (e.g. 404 errors)
Incorrect routing or URL mismatches
Network issues or timeouts
Client-side errors (JavaScript failures)
Blocked resources (e.g. third-party scripts or APIs)
How to Use This Section
Monitor trends over time
Look for sudden increases in either total or rate — these often signal new issues.
Compare rate vs total
High total + low rate → likely traffic increase
High rate → real degradation in navigation experience
Segment the data
Break down by page, device, geography, or traffic source to pinpoint affected areas.
Investigate root causes
Cross-reference with logs, releases, or performance metrics.
Best Practices
Keep the broken navigation rate as low as possible (ideally near 0%)
Set up alerts for unusual spikes
Regularly review top failing routes/pages
Validate navigation flows after deployments