Sending Transactional Emails

Sending Transactional Emails

It is now possible to send both marketing and transactional emails from the same Delivra account—no more toggling between accounts or maintaining multiple email lists. This new feature brings simplicity to your email strategy by keeping everything in one place, while respecting the unique needs of transactional messaging.

What Are Transactional Emails?

Transactional emails are non-promotional messages triggered by specific user actions or events, such as order confirmations, password resets, or shipping notifications. These messages are essential for operations and do not include unsubscribe options or marketing content. Due to the nature of Transactional messaging, not all types of campaigns are able to be sent as Transactional. Types that can be sent as Transactional include: Regular, Automated - Triggered, and Automated - API.


How It Works

When creating a new campaign, you’ll now see a toggle in the Email Setup section:
  • Marketing Emails: Standard promotional emails
  • Transactional Emails: Non-promotional messages used for system-triggered messages such as receipts or alerts

Key differences between Marketing and Transactional messages are:

  • No Footer: You won’t be prompted to add a footer. We recommend using Snippets if including support or contact info is needed, 

  • Not Just Subscribed Contacts: Transactional emails can still be sent to contacts that have unsubscribed from your marketing emails or are marked as expired. Contacts in held status will still be excluded.

  • Not included in Analytics: Transactional messages are not included in any analytics reporting as to not skew your Marketing analytics.

  • Send Cap Frequency: Transactional mailings can optionally be excluded from counting against your account's send cap frequency settings.

Best Practices & Tips

  • Use Snippets to include contact or support information when needed, especially since footers are removed in transactional sends.

  • Clearly name and label transactional campaigns to maintain internal organization and avoid confusion.

  • Avoid promotional language to preserve the transactional nature of these messages and maintain compliance.

Use Case Examples

  • Order Confirmations: Sent immediately when a customer completes a purchase

  • Account Notifications: Password changes, login alerts, or subscription updates

  • Service Alerts: Downtime or maintenance notifications that require urgent deliver

Info
If you are interested in enabling this feature, contact your Customer Success Manager or email success@delivra.com to learn more!

    • Related Articles

    • Advanced Sending Options for Campaigns

      When you reach the final step of creating a campaign in Delivra, you’ll decide when to send your email. Beyond the standard options like Send Now or Schedule for a Future Date, Delivra also offers advanced sending options designed to maximize ...
    • Sending MMS Messages

      MMS (Multimedia Messaging Service) allows you to enhance your mobile marketing by sending messages that include images, GIFs, and emojis alongside your text. It’s a great way to engage your audience with more vibrant, eye-catching content, right from ...
    • Sending SMS Campaigns

      Quickly create and send SMS campaigns using a guided workflow that requires a few simple steps. To get started, navigate to your Campaigns dashboard and click the Create Campaign button (top-right). Setup Enter a Campaign name & choose the Campaign ...
    • Suppressing Contacts from Mailings

      In Delivra, there are several ways to suppress contacts—either manually or automatically—from receiving your mailings. These options help you manage communication frequency, maintain compliance, and protect your sender reputation, all while ...
    • Can I recall a sent campaign?

      No, there is no way to undo the sending of a campaign or recall sent emails or unopened emails. No ESPs have the capability to pull back emails that have been sent. Depending on how severe the error is, you could send a second "Oops" email if the ...