Salesforce

Transactional emails

« Go Back

Information

 
Body

Permissions required to use this feature: transactional

Transactional emails are triggered to send by events that happen in your own website or application. You write the code for an event that needs an email to be sent, then use Campaign Monitor's API or SMTP servers to send the email.

Examples of transactional emails include order confirmations, shipping notifications, membership renewal notices, password resets and account status messages.

To use our transactional email service, you must use email authentication and be on a monthly plan.

We offer two types of transactional email: smart and classic. See the table below for a feature comparison.

FeatureSmart transactional emailClassic transactional email
Hosted by us
Sent viaAPIAPI or SMTP
Can use our email builder
Supports variablesNot required
Supports Liquid templating languageYes, if you import your own HTML
Advanced reportingYes, if you group emails

Switching from another provider

If you're already using SMTP to send with another provider, switching is as simple as changing the server, username, and password details. In addition to our own SMTP group headers, Campaign Monitor supports those from Mailgun, Mailjet, Mandrill, Postmark and Sendgrid, so you get reporting straight away without having to redeploy code.

If your existing transactional provider allows for multiple group names, Campaign Monitor only uses the first.

TitleTransactional emails
URL Nametransactional-emails

Powered by