Mandrill (Legacy) Icon

Mandrill (Legacy)

App Documentation
Last updated on February 28, 2016

Details

Please note: As of February 8, 2017 Mandrill is no longer required to initiate a Vextras workflow. Customers may still use Mandrill as the sending engine for existing workflows, or switch over to the Vextras sending engine. Going forward we will no longer support development using Mandrill’s technologies.

FAQ’s

Is it mandatory to remove my Mandrill app?
No. You don’t have to move away from Mandrill. At the present time, it’s still a viable way to deliver workflow messages. However, changing to our sending engine will most likely save you a few bucks and allow you to get the most out of our new features.

How much does it cost to use Vextras to send my workflow messages?
Absolutely nothing. We are including free, unlimited e-mail messages with all of our plans.

What if I have messages already queued to be sent? Can I still switch?
Yes, nothing will be interrupted. If there’s any messages queued and you switch over to the new sending engine, we’ll send those e-mails out as normal.

Why are you guys moving away from Mandrill?
We did this to simplify the activation of our workflows. It was just way too complicated to setup and we needed to overhaul the user experience.

Will there be any problems or changes with deliverability?
No. It should be just as good as what you’re used to, maybe even better. We’ve partnered with Sendgrid behind the scenes to deliver workflow e-mail messages. Sendgrid powers some of the world’s most recognizable brands including Uber, Spotify, AirBnB and Yelp.

Do I need to make any DNS updates?
You don’t have to, but it is recommended. To make it completely transparent to your customers where the e-mail came from (i.e. [email protected]), you may white label your sending domain like you did before with Mandrill. White labeling is easy, and here’s more information about how you can add the new CNAME records.

Ok sounds good, how do I make the switch?
Login to your Vextras account, click “Workflows”, “Settings” and change the Sending Engine to “Vextras”.

Requirements

  • 3dcart, Bigcommerce, WooCommerce or Volusion shopping carts
  • Vextras account
  • Activated Mandrill add-on in MailChimp
  • Ability to modify your DNS records for domain verification

Domain Verification

Mandrill has made “domain verification” mandatory for all accounts created after 12/1/15. In order to use the Mandrill app and any workflows, you must verify your sending domain in Mandrill by adding a few (TXT) DNS records.

Volusion Domain Verification Notes
  • Put both the DKIM and SPF record in quotes for the hostname records to take effect.
  • You must encode the plus (+) sign found in the DKIM record that Mandrill gives you.
  • The encoded value for a plus sign is %2B
Volusion SPF Example
  • Add a new TXT record using the “@” symbol
  • Put quotes around the SPF record in Volusion: "v=spf1 include:spf.mandrillapp.com ?all”
Volusion DKIM Example
  • Add a new TXT record with the name mandrill._domainkey
  • Mandrill instructions will have something that looks like this: v=DKIM1; k=rsa; p=JIGfMA0GCSqGSIa3DQEBAQUAA4GNAD CBiQKBgQCrLHiExVd55zd/IQ/J/ mRwSRMAocV/ hMB3jXwaHH36d9NaVynQFYV8NaWi69 c1veUtRzGt7yAioXqLj7Z4TeEUoOLg rKsn8YnckGs9i3B3tVFB+Ch/ 4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y 78dHZj1YeRXXVvWob2OaKynO8/ lQIDAQAB;
  • Put quotes and encode the plus sign when adding the record to Volusion: “v=DKIM1; k=rsa; p=JIGfMA0GCSqGSIa3DQEBAQUAA4GNAD CBiQKBgQCrLHiExVd55zd/IQ/J/ mRwSRMAocV/ hMB3jXwaHH36d9NaVynQFYV8NaWi69 c1veUtRzGt7yAioXqLj7Z4TeEUoOLg rKsn8YnckGs9i3B3tVFB%2BCh/ 4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y 78dHZj1YeRXXVvWob2OaKynO8/ lQIDAQAB;”
Other Notes
  • After your DNS is updated with verification records, it may take up to 48 hours for DNS (and Mandrill) servers to recognize the changes
  • You can only send from an email address on the domain that is verified. For example, if you’ve verified rickybobby.com, you can’t send from gmail.com. You could send from [email protected] or [email protected], etc.

Recommended Sending Defaults

  • Track Opens
  • Generate Plain-Text From HTML Emails
  • Inline CSS Styles In HTML Emails
  • Remove Query String When Aggregating URLs
  • Expose The List Of Recipients When Sending To Multiple Addresses
  • Add Unsubscribe Footer

Unsubscribes

  • It is recommended to include an unsubscribe link in your templates
  • Unsubscribes will be populated in the Mandrill black list
  • Customers who unsubscribe to a Mandrill generated workflow will not be synced with your MailChimp account

Logs

Event logs are generated in the Vextras Mandrill app log area on any successful (or failed) event.

Completed
  • Customer email
  • Rule name
  • Date
  • Opens
  • Clicks
  • Status – success or failure
  • Order ID (if applicable)
  • Customer ID (if applicable)
  • Message status
  • Details – linkage to message in Mandrill
Pending
  • Customer email
  • Rule name
  • Queued date
  • Scheduled to send date
  • Actions – promote or delete
Conversions
  • Customer email
  • Rule name
  • Date
  • Revenue
  • Order ID
  • Customer ID

More Information

  • If you have multiple stores, you may use the same Mandrill API key to send messages
  • If you have multiple sending domains, you are required to verify each one of them

Best Practices

  • If you’re coding templates on your own, keep a copy of your templates offline and in Mandrill
  • If you’re working with templates using the MailChimp drag-n-drop editor, keep a copy in MailChimp and use the “Send To Mandrill” option when it’s ready for use in Mandrill
  • It is recommended to drop in your merge variables at time of template creation vs. on the “fly” in the Vextras WYSIWYG editor. This way, you’ll always have them ready for use if you create new rules for the same workflow type.

News & Updates

Subscribe today for recent news and tips to grow your business

We don’t share your personal info with anyone