It currently supports WooCommerce using our Sync Mautic plugin, but it can be integrated with other eCommece platforms by passing order information into the mtc.js.
A really useful solution and a great market to invest in, especially considering the lack of solid plugins connecting WooCommerce and Mautic (and the good ones require a yearly subscription).
I definitely need to try this on a demo Mautic instance. Congrats on the great work and for supporting the community!
Thanks. We’ve actually just released an updated version which can attribute sales to specific contacts and even segment contacts based on if they have placed orders, how much they have spent, and more. We’ve also submitted it to be a part of the plugin Marketplace. Until then, the latest version can be found here:
Wanted to flag a fatal error we hit after updating from Mautic 7.2 RC → 7.2 stable (this plugin, v1.2.0, was already installed and working fine on 7.1.3 and on the 7.2 RC — it only broke going from RC to the final 7.2 release):
The service "mautic.integration.ecommerceconnector" has a dependency on a non-existent service "mautic.helper.encryption".
Root cause was on the Mautic core side, not the plugin: in app/bundles/CoreBundle/Config/services.php, EncryptionHelper is registered by class (Mautic\CoreBundle\Helper\EncryptionHelper::class), but the legacy string alias mautic.helper.encryption — still referenced by this plugin’s Config/config.php, and still documented in Mautic’s own plugin-dev tutorials/examples — is missing in 7.2 stable. Other helpers registered the same way, like CookieHelper, keep both the class registration and the alias, so this looks like something that got dropped specifically between the RC and the final 7.2 tag.
Workaround (fixed it without touching the plugin): added the missing alias back manually, right after the EncryptionHelper service definition:
Has anyone else seen this appear specifically going from 7.2 RC to 7.2 final? Might be worth a core issue too, since any plugin/integration still using the documented mautic.helper.encryption alias would hit the same thing.
We had not upgraded to 7.2 final yet as it just came out today, so we have not reproduced this ourselves, but I agree a missing alias between RC and stable should not break plugins. We will do some additional testing on our end.
The workaround you used is a valid short-term fix. We will update the plugin so it keeps working on older 7.x versions and on 7.2, and this may also be worth flagging as a core issue as I would not expect a breaking change from an RC to a stable release. We are wrapping up 1.3.0, which adds quite a bit, such as order line items, merchant/location on orders, contact eCommerce tab and timeline order details, segment filters for purchased products, a total revenue column on the contacts list, and an optional webhook email field that only links orders to existing contacts. We are still adding settings so some of those options stay off by default for GDPR. Once those settings, this 7.2 fix, and testing are done, we expect to release this week. If we don’t finish 1.3.0 this week we will at least get a fix for this issue out that also maintains backwards compatibility.
Thanks for flagging this up @dalmasont and posting the workaround - I’ve highlighted it for the core team. Indeed, BC breaks should be reserved for major releases, we’ve merged a huge volume of code improvements and deprecation removals recently (several hundred PRs!) so it’s possible that something slipped through on the wrong branch, or there is a bug which hasn’t been picked up. Either way, we’ll look into it.
We’ve released our latest version which fixes the incompatibility with 7.2 along with added features. If you use Sync Mautic you’ll need to update it as well. Since some have automatic updates, it does disable the plugins upon update since policies should be reviewed before activating additional features.
Do note that mtc has limitation on how many products can be passed if you want to track line items. If you want to track more, you’ll need to use the signed webhook, but this too has a downside of needing an additional cookie in order to track which email to attribute the sale too.