Transactional Campaigns

Table of Contents:

Introduction

Transactional Campaign Configuration

The transactional campaign configuration page, is for setting up statistical containers for the various types of transactional messages you might send in Ongage.

For example:

Transactional welcome messages, for new sign-ups, subscribers, customers, etc.
Transactional purchase receipts, reservation confirmations (typically issued via API).
Change in a list field value – e.g., membership package change, address change confirmation message, area of interest change, etc. (typically issued via Automation Rules or Website/CRM API).
Behavioral transactional messages – for transactional follow-ups messages to openers, clickers (typically issued via Automation Rules).
For all of these different types of transactional messages, you'll want to setup a separate transactional campaign (statistical container), so you can track the separate sending, delivery and performance statistics for each type of transactional message.

Every List in Ongage comes with 1 Default Transactional campaign already setup, and is used for aggregating the stats of the built-in transactional welcome message. Also, for any transactional API call, where the transactional campaign id was not specified in the API call, the transactional stats of that API call, will get aggregated in this default transactional campaign.

Transactional messages in Ongage can be issued from 3 primary places

The Built-in Transactional Welcome message. See the List Settings help page for more about that.
Automation Rules. We recommend setting up a separate transactional campaign for each separate Automation Rule that contains a Transactional Message Action.
API – where you can issue transactional messages from your Back-end / Website / CRM / etc. using the Transactional Mailing API method.

How to Setup a Transactional Campaign

Go to Campaigns >> Transactional Campaigns >> and click on New Transactional Campaign.
You can choose the Transactional Type you want, that is Email or SMS. Also, you need to provide the name and description for the same.

Advanced Configuration

Sending Connection

In the advanced configuration section of the Transactional Campaign, you can choose the default sending connection. The connection indicated in this section will be used as the default Vendor connection when using this Transactional Campaign ID via the API.

Select a Whitelist Segment to send Cc and Bcc transactional messages

In this feature marketers can setup to send an exact copy of the original messages sent via this transactional campaign, as a Cc and/or Bcc, to a list of staff members/stake holders, for legal or monitoring purposes. To implement, select a Whitelist Segment containing the contacts you want to send the Cc/Bcc to, for this particular Transactional Campaign.
- For more about Whitelist segments see our online Segments help page.
Note: Not all SMTPs support the Cc/Bcc feature, see the Appendix in our Transactional Mailing API doc for a list of those that do.

Campaign Level Suppression Lists

You can also configure a campaign level suppression list for each/any of the transactional campaigns you setup on this page. See our Lists Management help page for more about suppression lists.
Note: The campaign level suppression feature is not supported for the built-in Welcome Email/SMS (which is configured in the List Settings -> General page).

Appendix

SMTP vendors that support sending transactional messages

Amazon SES
Oracle Dyn
Elastic Email
InboxRoad
Mandrill (deprecated).
MailGun
MailJet V3
mySMTP
OpenText (limited availability).
Private SMTP (a generic SMTP connector for connecting to any On-Premise or Cloud SMTP server).
SendGrid
SMTP.com
SocketLabs
SparkPost & SparkPost Enterprise

SMS vendors that support sending transactional messages

CM.
MessageMedia
Sinch
Twilio