Configure tracking for Crash Analytics

Cloud On-Premise

From Matomo 6, additional options allow you to configure Crash Analytics in the Matomo user interface. For Matomo 6 On-Premise, these settings are available from version 6.1.0 of the Crash Analytics plugin.

This guide explains how to configure the number and types of crashes that are tracked and whether stack traces are stored.

Advanced users can configure these options manually using the JavaScript tracking code. See the Crash Analytics tracking options developer guide.

Crash Analytics settings

  1. To open the crash tracking settings, go to Administration admin gear icon> System > General settings > Crash Analytics.
  2. Configure the following tracking settings.
    crash analytics ui configuration
⚠ Note
If any of these settings are already defined in your website’s tracking code, the value in the tracking code takes precedence.

Set the maximum number of crashes tracked per pageview

Enter the Maximum number of crashes per pageview to set a limit that prevents generating excessive tracking requests for the same pageview.

The limit resets when a new pageview is tracked or the current page reloads. Default limit is 50 crashes per pageview.

Only track errors from specific domains

Add one or more domains to Only track errors from specific domains. This can be useful for excluding errors caused by third-party scripts, such as external libraries or embedded widgets.

Disable stack trace logging

You can Disable stack trace logging to prevent crash stack traces from being stored in Matomo, especially if they could contain Personally Identifiable Information (PII) or other sensitive information. Stack traces recorded before you disable this setting are retained.

When this setting is disabled, Matomo discards stack traces when a crash is received, even if the stack trace was sent by the tracker. This also prevents stack traces from being stored for crashes reported from outside the browser or from browsers using a cached tracking file.

Track errors from browser extensions

By default, Crash Analytics does not track errors caused by browser extensions as they can inject scripts or modify page content and cause errors not generated by the website.

Enable this setting, Track errors from browser extensions if you want to identify and investigate errors that occur when visitors use browser extensions. This can help you diagnose issues where an extension interferes with your website or affects the visitor experience.

Other Crash Analytics configuration options

You can further configure Crash Analytics to control how crashes are collected, grouped and displayed. Refer to the following guides for additional configuration options: