Propose new Mautic features
#MauticRoadmap Building Mautic together!
Änderungen an „Mautic 5 Bounce Management“
Titel
- -Better Bounce Management
- +Mautic 5 Bounce Management
Haupttext
-
-
Hello there,
please take a look at the proposal on the Google Drive link: https://docs.google.com/document/d/1FvzEtBmp-7kXjfIAnBo8ntFtWandzW3pdlfcmBVnR4M/edit
The document is still iterating, I am just putting it here, so that the proposal hopefully gets an attention from community.
Best, Matic
- -gid://app/Decidim::Hashtag/2/_Mautic gid://app/Decidim::Hashtag/3/_MauticFeatures
-
+
Extract from Google Document ( document version: 9 | Date: 2024-07-01 )
please take a look at the full proposal on this link: https://docs.google.com/document/d/1FvzEtBmp-7kXjfIAnBo8ntFtWandzW3pdlfcmBVnR4M/edit
The document is still iterating, I am just putting it here, so that the proposal hopefully gets an attention from community.
Introduction
My name is Matic Zagmjaster, I have been working with Mautic since version 2.x. I have written some plugins for Mautic and maintain a couple of instances. Over the years I managed to gain some knowledge about Mautic core.
I am looking for funding for implementation of the solution proposed in this document.
In addition to the high level overview of new features and time estimate, the document also includes my research and technical breakdown of things we need to do in order to bring bounce management in Mautic to the next level. Appendix sections at the end are not something you have to be concerned about unless you care about the implementation process/details.
The Problem
Mautic processing of email webhooks from Omnivery, Mailgun and similar providers is a bit limited due to insufficient underlying model where we store information coming from webhooks. This proposal aims to add ability to the Mautic core in a way so that transport plugins can leverage them and map it more precisely to the Mautic core model.
I am looking for funding for implementation of the solution proposed in this document.
Proposed Solution
For the problem described above I am suggesting that we add a complaint flag into the DNC entity so transport plugins can use it when the provider (Omnivery, Mailgun, etc.) suggests so.
We would also like to introduce soft bounces into Mautic core in a way so that we still send to contacts that soft bounces, but if the soft bounce happens multiple times that translates to the DNC entity for that lead with a hard bounced flag.
How many times contact soft bounces consecutively before it translates to hard bounced is configurable with the setting in Configuration -> Email Settings.
We introduce soft bounce categories so that transport plugins can categorize and we can display that data to the end user.
We would add the following filters on segments: filter for DNC complaint reason, soft bounce filter and soft bounce of specific category.
We would like to show some more statistics about bounced, soft bounced and complaint contacts on the email list page.
We would like to show the count of soft bounces & complaints on the contact page. Also show how many soft bounces until the hard bounce for the given contact.
Show count of soft bounces & complaints on email list view.
Estimate
I divided required work into separate milestones. Here is the estimate for each milestone:
Milestone 1: Add basic components for soft bounces and complaints - Estimate: 81 - 110 h
Milestone 2: Enable transport plugins to leverage new components - Estimate: 18 - 20 h
Milestone 3: Display info in UI - Estimate: 38 - 60 h
See the “Appendix: Technical Breakdown” section for breakdown of separate milestones.
Contact
If Mautic brings value to your business and you are interested in financing me either for part of the solution or for the entire solution, please reach out. Thank you for your consideration.
- Email: [email protected] (preferred)
- LinkedIn: https://www.linkedin.com/in/matic-zagmajster/
- Mautic Slack: gid://app/Decidim::User/260
- Mautic Forum: https://forum.mautic.org/u/mzagmajster/summary
- +gid://app/Decidim::Hashtag/2/_Mautic