This section refers to all the vendors that Ongage has plug & play connections to and you'll find them in the Ongage platform under: |
Amazon SES
mySMTP
Private SMTP (a generic SMTP connector for connecting to any On-Premise or Cloud SMTP server).
SendGrid
SMTP.com
SocketLabs
SparkPost & SparkPost Enterprise
Currently Ongage supports sending transactional email messages in the following ESP/SMTP vendor plug-ins ONLY:
Amazon SES
Oracle Dyn
Elastic Email
Mandrill
MailGun
mySMTP
Private SMTP (a generic SMTP connector for connecting to any On-Premise or Cloud SMTP server).
SendGrid
SMTP.com
SocketLabs
Currently Ongage supports sending transactional SMS text messages in the following SMS vendor plug-ins ONLY:
The following ESPs will add an additional unsubscribe link regardless to any custom unsubscribe link you used in Ongage:
Benchmark
BlueHornet (is now Mapp Digital)
Elastic Email
SmartFocus
Teradata (aka eCircle)
The following ESPs require that the fields you setup in your list in Ongage will be mapped to those in the outbound ESP.
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.
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.
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.
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: