MailerSend is missing the logs I need

If MailerSend’s logs aren’t giving you what you need, the usual fix is to add your own tracking layer rather than relying on the dashboard alone.

A few options:

1. Capture events via webhooks

   • Set up MailerSend webhooks for sent, delivered, opened, clicked, bounced, complained, etc.
   • Store those events in your own database.
   • This gives you a complete audit trail you control.

2. Log message metadata when sending

   • Save the recipient, subject, template ID, campaign ID, internal user ID, and MailerSend message ID when you send the email.
   • Then correlate webhook events back to your app records.

3. Use API response + retries logging

   • Record the raw API request/response for each send attempt.
   • If MailerSend accepts the message but later fails delivery, your webhook logs will show that.

4. Add a fallback SMTP/app log

   • If you’re sending through SMTP or from a backend job, log each attempt before and after send.
   • Include timestamp, environment, and any error messages.

5. If you need deeper SMTP-level logs

   • MailerSend may not expose the full detail you want in the UI.
   • In that case, a dedicated email observability tool or your own SMTP relay logs may be better.

If you want, I can help you design:

• a simple webhook logging schema,
• a database table for email events, or
• a Node/PHP/Python example to capture MailerSend events end to end.