Table of Contents:

Intro 

This section refers to all the vendors that Ongage has plug & play connections to and you'll find them in the Ongage platform under: 
Vendors Settings → ESP/SMTP Vendors & Vendors Settings → SMS Vendors

Subsection Pages

SMTP Vendor Connections in the Ongage Platform

  1. Amazon SES

  2. InboxRoad
  3. MailGun
  4. MailJet V3

  5. mySMTP

  6. Oracle Dyn

  7. Private SMTP (a generic SMTP connector for connecting to any On-Premise or Cloud SMTP server).

  8. SendGrid

  9. SMTP.com

  10. SocketLabs

  11. SparkPost & SparkPost Enterprise

SMS Vendor Connections in the Ongage Platform

  1. CM.
  2. MessageMedia
  3. Sinch
  4. Twilio

Support for Transactional Emails

Currently Ongage supports sending transactional email messages in the following ESP/SMTP vendor plug-ins ONLY: 

  1. Amazon SES

  2. Oracle Dyn

  3. Elastic Email

  4. InboxRoad

  5. Mandrill

  6. MailGun

  7. MailJet V3

  8. mySMTP

  9. OpenText

  10. Private SMTP (a generic SMTP connector for connecting to any On-Premise or Cloud SMTP server).

  11. SendGrid

  12. SMTP.com

  13. SocketLabs

  14. SparkPost & SparkPost Enterprise

Support for Transactional SMS

Currently Ongage supports sending transactional SMS text messages in the following SMS vendor plug-ins ONLY: 

  1. CM.
  2. MessageMedia
  3. Sinch
  4. Twilio

ESPs that Enforce their Unsubscribe Link

The following ESPs will add an additional unsubscribe link regardless to any custom unsubscribe link you used in Ongage:

SMTPs that Support List-Unsubscribe Header 

Ongage supports adding a List-Unsubscribe header for the following vendors:

SMTPList-Unsubscribe Header Notes
AmazonOngage automatically injects its own List-Unsubscribe Header
Ongage SMTPOngage automatically injects its own List-Unsubscribe Header
Oracle DynNeeds to be configured manually by Ongage Support
InboxRoadOngage automatically injects its own List-Unsubscribe Header
MailgunOngage automatically injects its own List-Unsubscribe Header
Private SMTPOngage automatically injects its own List-Unsubscribe Header
SendGridContact Ongage Support to configure for each of your SendGrid connections to automatically inject the Ongage List-Unsubscribe Header. See more details in following subsection.
SMTP.comOngage automatically injects its own List-Unsubscribe Header
SparkPostSparkPost automatically adds it's own List-Unsubscribe header
SparkPost Enterprise Ongage automatically injects its own List-Unsubscribe Header


Here's a sample List-Unsubscribe header. In the case that Ongage injects this header, the link will be the default unsubscribe link, the same one that appears in the body of the email message.

List-Unsubscribe: <http://track.yourdomain.com/member/unsubscribe/?listname=espc-tech@domain.com?id=12345N>

(warning) This header can also include an email address that you provide, but we recommend not to include it, as then the unsubscribe won't get registered in Ongage, in which case you'll then need to pipe it back to Ongage.  Moreover all unsubscribe stats won't get associated with the campaigns they occurred in unless you pass back the {{ocx_child_id}}.

How to add a List-Unsubscribe header for SendGrid connections in Ongage

  1. In your SendGrid account, go to: https://app.sendgrid.com/settings/tracking .
  2. Then deactivate the Subscription Tracking as illustrated below:
  3. Ask Ongage support to configure for each of your SendGrid connections in Ongage a List-Unsubscribe header.

Which ESPs require Field Mapping and Which Don't

ESPs that require field mapping

The following ESPs require that the fields you setup in your list in Ongage will be mapped to those in the outbound ESP.
(info) Note: You only need to map those field that you plan to use as dynamic fields inside the email message. Typically you only need to do field mapping once when you setup the ESP, and on those less frequent occasions, when you introduce or remove a dynamic field from your email message.

SMTPs & ESPs that DO NOT require field mapping

The following ESPs DO NOT require any field mapping, and you can use any and all your fields in your Ongage list as dynamic fields in your HTML email message.
(info) Note: generally speaking SMTPs do not require any field mapping, while ESPs do. For a list of SMTPs in the Ongage network see section about this above.

Which Vendors Support Ongage Dynamic Hashed Email Field

By and large the Ongage hashed email field {{ocx_email_hash}} is supported in all SMTP relay connections – see above "SMTP Vendors in the Ongage Network".

There are are a few other vendors where this feature is also supported, here is the complete list: