Crash Analytics for Matomo Cloud (beta)

The Matomo Crash Analytics feature collects information about crashes and unexpected errors that occur on your website or application. By analysing Crash Analytics data, you can identify stability issues that affect user experience, conversions, and revenue. Teams can then prioritise fixes based on real usage. Learn more about Crash Analytics.

The following guide details crash tracking in Matomo Cloud, feature activation, and configuration of the maximum crash hit percentage.

Enable Crash Analytics in Matomo Cloud

Crash Analytics is currently in beta. If the Crashes menu is not available in your Matomo Cloud instance, contact Matomo Support to enable the beta version for your instance.

1. Log in to Matomo as a superuser.
2. From the main dashboard, navigate to Crashes.
3. Click Activate to enable Crash Analytics.
   

After activating, allow up to 5 minutes for Matomo to begin recording crashes and errors. You will only see report data if any errors occur.

Change the Crash Analytics quota percent

When Crash Analytics is enabled, crash tracking is limited to 5% of your Cloud Hits quota by default. Once the quota percentage is reached, Crash Analytics stops collecting new crash data until the Cloud Hits quota resets the following month. Read more about Crash Analytics and Matomo Cloud billing.

Existing reports are still available for viewing, even after the limit is reached. You can change the Maximum hits for Crash Analytics at any time.

• Lowering the percentage reduces the maximum number of crash hits that can be tracked in a month. If you reduce the percentage and this new limit is already exceeded for the current month, crash tracking will pause automatically until the start of the next month.
• Increasing the percentage allows more crashes to be tracked each month.

Regular monitoring, prompt error fixes, and best development practices can help control Crash Analytics costs and maintain site or application stability.

1. Log in to Matomo as a superuser and navigate to Administration > System > General Settings > Crash Analytics.
2. Select the maximum percentage of your Cloud hits quota that can be used for Crash Analytics.
   
3. Click Save.

Disable Crash Analytics

1. To stop using this feature, select the option Disable Crash Analytics in your Crash Analytics settings.
2. Click Save and crash tracking will be deactivated.

Versioning URL Parameters

This setting tells Matomo which URL parameters to ignore when identifying crashes. Some websites add parameters to file URLs to manage caching or versioning, such as v=123 or cb=456. These parameters do not change the actual source file, but they can cause the same crash to appear multiple times in reports.

By ignoring these parameters, Matomo groups crashes from the same source file together. This makes your Crash Analytics reports easier to read and avoids duplicate entries caused by version or cache-busting values.

Group Source Files with Hashes

Select this option to group crash source files that use hashed filenames. Some systems name JavaScript files using long hash values, for example 900150983cd24fb0d6963f7d28e17f72.js. Each new deployment can change the hash, even though the underlying code is similar. A file is treated as hashed if its name contains at least 20 letters or numbers in a row.

When this option is enabled:

• Matomo groups hashed filenames under a single entry.
• Reports show these files as [grouped-hash].
• Duplicate crash entries caused by changing hashes are removed.
• It becomes easier to spot new crashes and see which ones no longer occur.

Crash Analytics gives you visibility into client-side errors while keeping usage predictable. By defining the percentage of your Cloud Hits quota for crash tracking, you control how much impact it can have on billing.

Crash Analytics and Matomo Cloud billing

Crash Analytics data contributes to your Matomo Cloud Hits quota. Each crash report sent from a website or application is processed as a tracking hit and counts towards the total hits included in your subscription period.

• If Crash Analytics is enabled, crash tracking is limited to 5% of your Cloud Hits quota by default.
• You can change the limit by setting the maximum percentage of your cloud quota for Crash Analytics.

Matomo adheres to this limit automatically ensuring Crash Analytics does not exceed the configured percentage. Once the limit is reached, crash tracking will pause until the start of the following month, and other configured tracking continues as normal. This prevents unexpected billing increases caused by crash spikes.

Crash Analytics quota examples

Matomo Cloud subscriptions can be billed monthly or annually. For Crash Analytics limits, Matomo always uses the monthly hits quota included in your plan, even if you pay annually. The following three examples show how Crash Analytics usage is calculated against the monthly quota derived from your plan:

1. No impact on billing, monthly billing

• Plan: 1 million hits per month
• Billed: Monthly
• Total Cloud Hits quota for billing period: 1 million hits
• Maximum monthly hits for Crash Analytics: 5% (50,000 hits)
• Tracked crashes: 30,000 hits
• Other tracked hits: 920,000 hits
• Total tracked hits: 950,000 hits
• Billing impact: Total billing period hits remain within quota, so there is no impact on billing.

2. With overage charges, monthly billing

• Plan: 1 million hits per month
• Billed: Monthly
• Total Cloud Hits quota for billing period: 1 million hits
• Maximum monthly hits for Crash Analytics: 5% (50,000 hits)
• Tracked crashes: 50,000 hits (crash tracking paused during the month as the limit was reached)
• Other tracked hits: 980,000 hits
• Total tracked hits: 1,030,000 hits (30,000 hits more than the Cloud Hits quota)
• Billing impact: Total hits exceeds the billing period hits quota and triggers overage charges.

3. No overage charges, annual billing

• Plan: 1 million hits per month
• Billed: Annually
• Total Cloud Hits quota for billing period: 12 million hits
• Maximum monthly hits for Crash Analytics: 5% (50,000 hits)
• Tracked crashes: 0.5 million hits
• Other tracked hits: 10.7 million hits
• Total tracked hits: 11.2 million hits
• Billing impact: Total billing period hits remain within quota, so there is no impact on billing.

The Crash Analytics hit volume typically decreases as crashes are fixed. Each resolved crash reduces the number of repeat crash events sent to Matomo. Over time, this lowers Crash Analytics hit usage and reduces its impact on your Cloud Hits Quota.

Feedback and beta access

Crash Analytics is currently in beta and your feedback helps improve the feature and shape future development. If you have suggestions, encounter issues, or need beta access for your Matomo Cloud instance, please contact Matomo Support.