Which plugins is Matomo for WordPress known to be not compatible with?

This list applies to Matomo for WordPress, it does not apply to Connect Matomo Integration.

If you are using Matomo for WordPress 5.0.3 or greater:

• Minify HTML: Sparkline graph images in Matomo reporting pages will not load while this plugin is active.

If you are using Matomo for WordPress 4.15.3 or lower:

• Background Manager (background-manager/background-manager.php). Uses an old version of twig which may cause issues in the Matomo reporting and admin pages.
• All-In-One Event Calendar. Uses an older version of Twig.
• tweet-old-post-pro (Revive Old Posts Pro Add-on). Archiving (report generation) may fail. A workaround might be to follow the last step in this faq which suggests to add « define( 'MATOMO_SUPPORT_ASYNC_ARCHIVING', false ); » to wp-config.php.
• WP RSS Aggregator: There is an incompatibility because they are using an older version of a library (Twig).
• Age Verification System for WooCommerce: Uses an older version of Twig.
• Minify HTML: Sparkline graph images in Matomo reporting pages will not load while this plugin is active.
• BigBuy Dropshipping Connector for WooCommerce: Includes an incompatible version of monolog.
• Google Listings and Ads: Includes an incompatible version of monolog.
• Post-SMTP: The PDF report files from the email reports will be missing when the PostSMTP mode is selected but it works when the PHPMailer mode is selected.
• Adshares: Uses an older version of Twig.
• bluehost-wordpress-plugin: Uses an incompatible version of the ContainerInterface.
  If you experience issues with any of these plugins the workaround is to:
• backwpup: There is an incompatibility in the Monolog versions embed by this plugin and our own one, which breaks the archiving process.
• fs-poster: The paid version of this plugin embeds an incompatible version of the LoggerInterface.
• PublishPress Blocks: Uses a PHP-DI version that conflicts with Matomo’s.

To resolve a plugin incompatibility issue:

• disable the plugin that is causing the problem,
• or disable Matomo for WordPress plugin and instead use Matomo On-Premise or Matomo Cloud in combination with our Connect Matomo Integration.