Mautic 7 Compatible Plugins: What to Check Before Upgrade

Verify the publisher’s exact Mautic 7 claim

Some plugin publishers explicitly document Mautic 7 support, but a Marketplace listing alone does not establish compatibility. Mautic says its Marketplace does not verify version compatibility (retrieved August 23, 2026). Check the vendor’s current support statement and declared PHP and mautic/core-lib constraints for the release you plan to run. On August 23, 2026, Mautic listed 7.1.2 as active with PHP 8.2–8.5. Anything not listed below remains unknown, not incompatible.

What compatibility actually means on Mautic 7.x

A useful compatibility record has more than a package name. It ties a plugin release to the Mautic major version, the PHP range, and the core-library dependency range the publisher says it tested. Mautic’s developer listing documentation tells authors to declare tested PHP versions and mautic/core-lib constraints (retrieved August 23, 2026).

Use four separate checks:

1. Discoverability: whether the package appears in the Marketplace or the vendor’s catalog.
2. Declared constraints: which PHP and Mautic core versions its current package accepts.
3. Published support: whether the publisher explicitly names Mautic 7 for that plugin release.
4. Instance verification: whether the plugin’s real workflows pass on a representative staging copy of your installation.

Plugin categories to include in the upgrade inventory

Group extensions by the work they change so the staging plan exercises the right workflows. The verified source set for this guide provides examples in five categories:

• User-interface customization: plugins that change screens, navigation, widgets, or other administrator-facing behavior.
• Campaign link tagging: plugins that apply tracking parameters to links used in emails and content.
• Mail transport: plugins that add or select delivery transports.
• Account-based marketing: plugins that add account-level marketing workflows.
• Revenue operations: plugins that add deal and pipeline workflows inside Mautic.

This is an evidence-bounded set of examples, not a complete plugin catalog. Add every integration, connector, reporting extension, authentication extension, theme-related extension, and custom bundle installed on your own instance to the inventory even when its category is absent here.

Named plugins with a published Mautic 7 statement

Each row reports what the named publisher currently says. It does not extend that statement to another release, another plugin from the same vendor, or a different environment.

What to do when a plugin’s status is unknown

If a plugin is not in the table, its status is unknown for this guide. That is not a statement that the plugin fails on Mautic 7. It means the source set checked on August 23, 2026 did not establish a publishable compatibility claim for it.

Look for a current compatibility page, release note, changelog, package constraint, or Marketplace listing controlled by the publisher. If the available material does not explicitly cover Mautic 7, ask the publisher and keep the status unknown until a primary source or your own controlled test resolves the operational decision.

How to verify the installed plugin set before upgrading

1. Inventory every extension. Record the installed version, publisher, source URL, and the workflow it changes.
2. Check current primary documentation. Capture the exact Mautic and PHP versions the publisher names, with the retrieval date.
3. Inspect declared constraints. Compare the tested PHP range and mautic/core-lib constraint with the planned Mautic 7 environment.
4. Label gaps as unknown. Do not turn missing documentation into an incompatibility claim.
5. Test the real workflows in staging. Follow the source-backed Mautic 5-to-7 upgrade workflow, then exercise every plugin-specific screen, job, event, integration, and data path before production.

For the support window behind that planning work, see the dated guide to Mautic 6 security support.

Sources checked August 23, 2026

• Mautic Marketplace documentation — Marketplace compatibility-verification policy.
• Mautic developer listing documentation — tested PHP and mautic/core-lib declarations.
• Mautic releases — active release and PHP support range.
• Mautic Extendee Customizer documentation.
• Mautic Extendee Auto Tagger documentation.
• Mautic Extendee Multiple Transport documentation.
• Leuchtfeuer Mautic ABM documentation.
• Deal Flow installation documentation.

All sources above were retrieved August 23, 2026. Compatibility statements can change; recheck the publisher’s current page when approving an upgrade.

Frequently asked questions

What does Mautic 7 compatible mean?

A useful Mautic 7 compatibility statement identifies Mautic 7 support and declares dependency constraints for the target environment. Mautic's Marketplace documentation says it does not verify version compatibility. Check the publisher's current documentation, tested PHP range, mautic/core-lib constraints, and the exact release you plan to run. The Marketplace and listing documentation were retrieved August 23, 2026.

Does a Marketplace listing prove that a plugin works on Mautic 7?

No. Mautic's Marketplace documentation says the Marketplace does not verify plugin version compatibility. Use the listing to discover the package, then verify the publisher's dated support statement and declared dependency constraints. The source was retrieved August 23, 2026.

What if a plugin is not listed in this guide?

Treat its Mautic 7 status as unknown, not incompatible. Check the publisher's current primary documentation and package constraints, then test it on a representative staging copy before changing production.

Which plugin categories have a verified Mautic 7 example here?

This guide includes source-backed examples for user-interface customization, campaign link tagging, mail transport, account-based marketing, and revenue operations. The list is evidence-bounded, not a complete catalog of Mautic 7 plugins.