Crash Analytics

Broken carts, glitchy checkouts, unresponsive contact forms – they're not just annoyances; they're revenue pitfalls waiting to happen.

13% of all pageviews come with lurking JavaScript errors that can cripple your visitors' experiences and jeopardise your revenue potential. Recent statistics reveal that 58% of visitors are inclined to abandon purchases as a result of bugs, while an astonishing 75% are driven to completely abandon websites due to these frustrating experiences.

To provide some context, consider a website that usually earns 25,000 EUR per month. If this site is encountering errors in 13% of all pageviews, it could potentially result in a monthly loss of 1,855 EUR.

With Crash Analytics, you can improve the user experience, boost conversion rates and grow revenue with 100% website reliability.

Even with the most rigorous tests, you can't foresee every glitch across diverse browsers, setups and scenarios. Factors like ad blockers, fluctuating internet speeds and evolving browser versions compound the complexity. This is where Crash Analytics excels.

 

Getting started

What does Crash Analytics do?Getting started

Create and manage

What does it mean when a crash is ignored?Ignore or unignore a crashWhat is a first party crash vs. a third party crash?What do I do if I can’t reproduce an error I see?What does it mean when a crash is disappeared/reappeared?

Analyse Crashes

Analyse crashes

How to

Hide the crash context from being displayed to Matomo usersControl how many days must pass before a crash is considered disappeared/reappearedTrack JavaScript errors that occur before Matomo JS tracking code is loaded

On-Premise FAQs

Make sure old crash data is regularly deletedMake sure very old crashes that reappear are considered newControl how many rows are shown in Crash Analytics reports

Troubleshoot

What is a “Script Error” and why isn’t there more information?