Statistics for Transactional Emails
Travis Pflanz
Currently MailPoet does not log the transactional emails, so website owners don't know which emails are getting through, opened, clicked, bounced, etc.
Logging ALL emails will give a lot more info and control to website owners, as the website owner will be able to make necessary changes to keep their list/emails in good standing.
K
Kelly
I suspect this ties into a Feature Request I just opened - allowing segmenting on Welcome emails. I imagine without logging stats on transactional emails, you can't do segmenting - so we can't check opens and send appropriate timed, contextual re-engagement emails.
This is such basic functionality for an email system that handles e-commerce/membership systems (or any site for that matter).
Ján Mikláš
open
Ján Mikláš
closed
We have a separate plugin just for the logging -https://wordpress.org/plugins/wp-mail-logging/
Travis Pflanz
Ján Mikláš: No. That is not how the logging plugin works and MailPoet documentation outlines this, as well. Discuss with your developers and reopen this feature request. It's disheartening when employees don't understand how their own company's products function.
Ján Mikláš
Travis Pflanz: now that I read it again, you'd like the same open/click statistics (not logging) for transactional emails, as there are for newsletters?
Ján Mikláš
Travis Pflanz: after a brief discussion with the team, I'm keeping this request closed, as there is no plan to support statistics or any kind of tracking for transactional emails
Travis Pflanz
Ján Mikláš: MailPoet needs to function like a normal transnational email service provider - if it is going to have any use for a serious website/business. Each email sent to each email address needs to be accompanied by statistics and data as it pertains to each individual email sent and email address.
Please reopen this feature request - That is the whole point of this system, right? To get feature request from your users. Why would a company ever close a feature request unless they plan to implement it? If your company says it wants feedback and input from users, it doesn't make sense to close a request that is relatively new and has some traction.
To be honest, I'm not really surprised. A lot of companies do this type of crap after running a lifetime deal offer. Promise the world and promise to listen to user feedback, but then shut it down after the refund period has passed and too many real in-depth users giving relevant and necessary feedback.
I used MailPoet years ago before your huge security issues, which at the time led to the largest WordPress website infection instance, so I stayed away for years. It looks like you've made an attempt to become truly relevant in the email marketing game, but refusal to properly track and attribute the emails your platform sends results in it only being useful for bloggers. Truly disappointing.
Ján Mikláš
Travis Pflanz: I understand your point of view, and just so there is enough time for others to vote on this, I reopened it. But could you please elaborate, what useful data you plan to get from transactional emails, that would convince us it's worth spending time on developing this feature and would be useful for many customers?
Travis Pflanz
Ján Mikláš: Other than everything already mentioned in the original post and the replies?
P
Pat Bell
Travis Pflanz: the only indication of transactional emails bouncing is the warning about too many. And there is NOTHING you can do about it. Nowhere can you find a log of bouncing or the blacklist. Since ALL transactional emails are likely to be contact emails to the site owner then this is a major problem and one that could ruin a business. Far from the marketing ploy of "Better deliverability" transactional email by Mailpoet is not fit for purpose.