Skip to main content

Prerequisites

Setup

1

Create a Mandrill API key

In Mailchimp Transactional, follow the quick start to create an API key.
2

Configure in Courier

Open the in Courier, enter your API key, From Address, and From Name, then save.
Addressing a recipient and sending are the same on every email provider, so they are documented once: and .

Overrides

covers the two levels and which one wins. lists the fields every email provider takes. Use a provider override to change what Courier sends to Mandrill’s Messages API. This example adds an attachment.
Overrides are deep-merged into the request. Fields you set replace their counterparts, and everything you leave out is still sent. See the full field list in the Mandrill Messages API docs.

Template import

Import your Mandrill templates from the .
Enter your Mandrill credentials on the configuration page to load your saved templates.
Templates ready for import appear as checkboxes.

Template import page

Troubleshooting

Check the to debug provider errors. For anything else, contact Courier Support.

Mandrill click tracking not working

Three likely causes:
  • Click tracking is off.
  • The URL is too long, so Mandrill disabled click tracking.
  • The clicks are recorded but not updated in real time.
Solution Check whether click tracking is enabled:
1

Log into Mandrill

Log in to your Mandrill account.
2

Open Sending defaults

Go to Settings, then Sending defaults.
3

Check the Track Clicks setting

Set the “Track Clicks” dropdown to anything other than “No click tracking”.
Mandrill tracks opens and clicks in real time, but status updates can lag. Delays run from a few minutes to much longer, such as when their system is under load. for clicks on your Templates.

Mandrill BCC not working

Mandrill is ignoring the BCC headers. Solution
  1. Use the to field rather than the bcc field, and set X-MC-PreserveRecipients to false.
  2. Or put the BCC address in the to field with its type set to bcc. Add preserve_recipients: true under the message section, as below.
For more on X-MC-PreserveRecipients, see Mailchimp’s SMTP headers documentation

Mandrill CC emails not present

Pass CC fields to Mandrill’s API or through an API override. As with BCC, set preserve_recipients to true in the override request. Without it, CC emails will not be sent. Solution

Mandrill merge vars not working

Merge variables usually fail because of how they are nested. Solution Nest the variables inside the message struct, as below.

Provider details

Courier recommends routing to the channel. Naming this key in routing.channels instead is supported, and sends through just this provider.

Send to a specific provider

When that is worth doing, and what you give up: failover, channel priority, and providers you add later.