This article explains how to set up a reliable double opt-in (DOI) workflow in Mautic using the Email Verification and Double Opt-In plugin by Leuchtfeuer. It covers why the native Mautic approach is problematic, what the plugin does differently, and how to configure it.
Mautic tracks every website visitor from the first page view (of course only when the tracking code is embedded and consent was given ;) - but until someone submits a form or clicks a tracked email, that visitor is usually anonymous.
The background to this blog post is a master thesis on "Developing a lead scoring model for simple and advanced use cases using the example of the Mautic software" that was recently written here. The contents of this are summarized below. For a more detailed version, the master thesis can also be accessed here.
Mautic is a tool with seemingly endless possibilities, but that is precisely why there can be occasional confusion in some processes. When does a contact leave a campaign, can they come back, and what was that about segments again? In this post, we'll show the common rules for exiting and returning contacts to campaigns and segments.
The Mautic database tends to grow huge very quickly, especially when integrated on higher-traffic web sites. A large percentage is basically junk, though. Here are some simple tricks to reduce that drastically.
Note that at the same time this addresses GDPR requirements for deleting old data.
With our housekeeping plugin for Mautic, you can easily keep your database lean. Which functions the plugin offers and how to use it sensibly is explained in this tutorial!
Double Opt-In (DOI) is annoying, but usually classified as necessary and should at least work as smoothly as possible. It takes the following little tricks to really ensure this, even if no cookie consent was given!
