Track Mandrill (Mailchimp Transactional) email delivery with ParseBounce. Monitor hard bounces, soft bounces, spam complaints, and rejections in real-time.
| Mandrill Event | ParseBounce Type | Description | Suppression |
|---|---|---|---|
| hard_bounce | bounce | Permanent delivery failure - invalid email | Auto |
| soft_bounce | bounce | Temporary delivery failure | — |
| spam | complaint | Recipient marked email as spam | Auto |
| reject | reject | Mandrill rejected the email before sending | — |
| send | delivery | Email sent to recipient server | — |
| deferral | deferred | Recipient server temporarily rejected | — |
| open | open | Recipient opened the email | — |
| click | click | Recipient clicked a link | — |
| unsub | unsubscribe | Recipient unsubscribed | Auto |
Events marked "Auto" are automatically added to your suppression list
Follow these steps to start monitoring your Mandrill emails
Log in to Mandrill → Settings → Webhooks. Click "Add a Webhook".
Enter your ParseBounce webhook URL as the Post To URL.
Check the events you want to track: Message is Bounced (hard/soft), Marked as Spam, Sent, Opened, Clicked, etc.
After creating the webhook, copy the Webhook Key and add it to your ParseBounce project settings for signature verification.
Click "Send Test" on your webhook to verify ParseBounce receives events correctly.
No, Mailchimp Transactional (formerly Mandrill) is a separate product for transactional emails. Regular Mailchimp marketing campaigns use different webhooks.
Rejects happen before sending - Mandrill blocks the email due to policy. Bounces happen after sending - the recipient server rejected delivery.
Use the metadata field when sending emails via API. Include parsebounce_id in your metadata for campaign tracking in ParseBounce.
Yes, the webhook key is required for ParseBounce to verify that events are genuinely from Mandrill and haven't been tampered with.