Mailchimp Transactional Email, formerly Mandrill, helps you send customized email to your recipients using the API or an SMTP integration. After you send, you can view report data in your Mailchimp account or with the Transactional Email API.
Depending on your Mailchimp plan, you may not have access to Transactional Email as a paid add-on. To learn more, check out About Mailchimp Pricing Plans.
In this article, you'll find some resources to help you send email with Transactional Email.
Design and send
You'll design your email outside of Transactional Email and then use the delivery API to send it to recipients. Whether you code your own HTML template or use one of Mailchimp's, you may need to tweak the template's HTML to use with Transactional Email.
How to Code Transactional Email Templates
Transactional Email supports mc:edit regions from the Mailchimp Template Language, but editable images, repeatable areas, and variants don't work.
Many Mailchimp merge tags don't work in Transactional Email because they're tied to an audience or campaign. You can use merge tags to personalize emails in Transactional Email, but you have to provide the information to populate merge tags when you send.
I use Mailchimp templates.
If you have a template you created in your Mailchimp account, you can export the template to Transactional Email. Templates aren't linked, so if you make any changes to your Mailchimp template, you'll need to push the updated version to Transactional Email again.
With Mailchimp Transactional Email, you'll use the Transactional Email API or an SMTP integration to send emails to your recipients. You'll need to add SPF and DKIM records and verify ownership of all sending domains in Transactional Email. Transactional Email will not send any email from unverified domains or domains without valid SPF and DKIM records, including public domains like gmail.com and yahoo.com.
Transactional Email allows you to manage unsubscribes and view report activity in Transactional Email or your connected Mailchimp account.
The Transactional Email unsubscribe merge tag consists of the word UNSUB, followed by a colon, and a full web address (with http:// or https://) where recipients should be redirected after the unsubscribe is processed.
Transactional Email doesn't automatically add unsubscribed recipients to the unsubscribed portion of a Mailchimp audience. If you want Transactional Email recipients who unsubscribe to be unsubscribed in Mailchimp also, create a Transactional Email webhook and use the Mailchimp API to remove people from your Mailchimp audience programmatically.
Transactional Email can also perform more complex email marketing functions, like A/B Split Testing and email scheduling.
A/B Split Testing
A/B Split Tests in Transactional Email are a powerful and easy way to track and optimize recipient engagement with your emails. For example, create different versions of your website registration email and see which version gets the most opens and clicks over time.
When passing message information to Transactional Email, you can specify a particular time and date that an email should be sent. Transactional Email stores the message for you and sends it at the chosen time.
Use this process to create a highly customized series of emails based on a recipient action you track in your application, like registration date, purchase date, or product purchased. Send these emails to Transactional Email at your convenience, and it'll send them at the time specified in your API request or SMTP message parameters.
For example, when someone registers on your website, you might send a confirmation email through Transactional Email right away. After this initial request, you could configure a second request to have Transactional Email send a follow-up email at a specific date and time, like seven days after the registration.