If you think you found a bug in Matomo, please report it on Matomo GitHub Issues, so our team can investigate. We track all bugs and feature requests in GitHub where developers can review and prioritise issues transparently. When you submit a clear and complete report in GitHub, it saves time, reaches the right people, and helps us quickly understand the problem.

However, before you submit a bug report, check the following to ensure your reported issue is actionable:

  1. You are using the latest Matomo release. Bugs may already be fixed in newer versions.
  2. Search the Matomo forums and GitHub issue tracker to see if the same problem has already been reported.
  3. If it exists, add a comment with your details instead of creating a new issue.
  4. If the problem has not been reported, you will need to create a new bug report.

How to write a detailed bug report

  1. Open the Matomo GitHub Repository and go to the Issues tab.
  2. Click New issue and an issue template will open to guide you on what information to provide.
    new github issue
  3. Write a descriptive title and summary and include any recent changes to your setup.
  4. Describe the problem, what you expected to happen, and include the steps needed to reproduce the issue.
  5. Include supporting information such as screenshots, error messages, and environment details like the Matomo version, browser, operating system, and hosting environment, if relevant.

If you are unsure about using GitHub, you can still report bugs using the support form. Please include as much detail as possible using the points above and the GitHub issue will be created for you. We appreciate your feedback.

Previous FAQ: Accessing helpful advice within Matomo