Transactional Emails

JangoMail provides a robust mechanism for sending single-recipient transactional messages.

Examples of transactional emails are order confirmations, appointment reminders, "be my friend" requests on social networking sites, and other single-recipient email messages that result to facilitate a transaction between the sending organization and the recipient.

JangoMail sends transactional emails in two ways:

  1. Via the API/Web Service

      Two methods are available:
    1. SendTransactionalEmail passes the full details of the email message. There is a test form for the SendTransactionalEmail method that can be used to send test transactional emails, and a technical specification for this method.
    2. SendTransactionalEmailFromTemplate passes the Campaign ID of a message created using the JangoMail interface and uses that message as a template. There is a test form for the SendTransactionalEmailFromTemplate method that can be used to send test transactional emails, and a technical specification for this method. There is more information on this method in our template-driven transactional emails overview.

  2. Via the JangoMail SMTP Relay

JangoMail's transactional messaging reporting allows a user to view reporting data, such as Opens, Clicks, Unsubscribes, Bounces, and Complaints organized by groups of transactional emails. The reporting data can be retrieved in the JangoMail web interface or with the Web Service's reporting methods.

What are the benefits?

Typically, organizations send transactional emails either manually (using a desktop or web-based email program) or programatically through server-side scripting on a web page. The email message is routed through an SMTP server to the recipient.

There are many advantages to using JangoMail's SendTransactionalEmail methods or SMTP relay service:

  1. Authentication: The transactional emails are signed with DomainKeys and DomainKeys Identified Mail (DKIM).
  2. Reporting: The transactional emails are tagged such that Open Tracking and Click Tracking data is available on the email messages.
  3. Compliance: The transactional emails are checked against your account's unsubscribe and bounce lists, ensuring that emails are not sent to recipients that do not want emails from your organization. This saves you money and makes sure that you are following CAN-SPAM requirements.
  4. Deliverability: The email messages can be routed through our high-reputation sending IP addresses. Additionally, if your account qualifies, your email messages may be routed through servers whitelisted with the Return Path Certification Program (additional cost may apply).

How do I use this feature?

To send transactional emails through the JangoMail API, you must have some programming experience working with a Web-based API. Here is a tutorial on how to use the JangoMail API. Calling the SendTransactionalEmail or SendTransactionalEmailFromTemplate API methods are similar to calling the the SendMassEmail API method. While SendMassEmail is meant for sending email campaigns to multiple recipients (from two recipients to millions of recipients), these methods are designed for sending single recipient email messages.

If you do not have programming experience, consider using the JangoMail SMTP Relay to send transactional emails. This requires less technical expertise. You will need to set up your emails to send through relay.jangosmtp.net. For full instructions, see our SMTP Tutorial.

Create a Free Trial Account and Start Sending Now

1. Create a free trial account.
2. Use your assigned username/password in the Send Transactional Email or SendTransactionalEmailFromTemplate test form or call the API method programatically using HTTP POST, HTTP GET, or SOAP.

Documentation on Transactional Messaging