Versions Compared

Old Version 22

changes.mady.by.user MailUp Dev Team

Saved on

compared with

New Version 23

changes.mady.by.user MailUp Dev Team

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page:

...

(warning) = available with restrictions (see specific notes for each case)

 

 

Manage lists and groups

 HTTP, FormsSOAPRESTSMTP+FTPList+Frontend
Create/Delete/Update lists (tick)     
Create/Delete/Update groups (tick)(tick)    
Read lists and groups (tick)(tick)    

 

Subscriptions

 HTTP, FormsSOAPRESTSMTP+FTPList+Frontend
Import recipient (single)(tick)(tick)(tick)(warning)1(warning)2  
Import of recipients (bulk) (tick)(tick) (tick)(warning)3 
Bulk import limit
(Mega Bytes )		 

MailUpImport : Multiple import by splitting in blocks,
up to 1,5 MB per block

SendMessageNL: as FTP case

Multiple import by splitting in blocks,
up to 7 MB per block		 N/A, but successfully
tested either with 50 MB or with
a single import file containing 4 millions email addresses		10 MB 
Force optin of unsubscribed recipient (single)(tick)(warning)2(tick) (warning)2  
Force optin of unsubscribed recipients (bulk) (tick)  (tick)  
Unsubscribe recipient (single)(tick)(tick)(tick) (warning)2  

Unsubscribe recipient (bulk)

 (tick)  (tick)  
Read personal data fields settings (tick)(tick)    
Update recipients' personal data fields(tick)(tick)(tick) (tick)  
Check recipient's subscription status(tick) (tick)    
Add to group (single)(tick)(tick)(tick) (warning)2  
Add to group (bulk) (tick)(tick) (tick)  
Remove from group (single)  (tick)    
Remove from group (bulk)    (warning)4  

 

Email

 HTTP, FormsSOAPRESTSMTP+FTPList+Frontend
Create email message (tick)(tick)(tick) (tick) 
Read email messages (tick)(tick)    
Manage tags  (tick)    
Manage attachments (tick)(tick)(tick) (tick) 
Manage both embedded and not embedded images in the same message   (tick)   
Manage dynamic fields (tick)(tick)  (tick) 
Manage dynamic content (tick)?  (tick) 
Manage image upload (i.e. make them hosted by MailUp)  (tick)(tick) (tick) 
Manage attachments (tick)(tick)(tick) (tick) 
Full content customization for each recipient   (tick)   
Allow mixing embedded and not embedded images in one email message   (tick)   
Transactional emails (account credentials after signup, password reminders...) (tick)5 (tick)   
Transactional emails (newsletters, customized messages) (warning)5 (tick)   
Promotional emails (tick)(tick)    
Send to a single recipient (tick)(tick)(tick) (warning)2,3 
Send to a group (tick)(tick)  (tick) 
Send to all list subscribers (tick)(tick)  (tick) 
Scheduled sending (tick)     
Manage queue of messages to be sent (tick)     
Get email statistics in real time (tick)(tick)   (tick)
Get email statistics (with scheduled process)    (tick)  

 

SMS

 HTTP, FormsSOAPRESTSMTP+FTPList+Frontend
Create SMS (with dynamic fields) (tick)  (warning)6  
Manage dynamic fields (tick)     
Send SMS to a recipient (tick)  (warning)6  
Send SMS to a group/list (immediate & scheduled) (tick)  (warning)6  
Get SMS statistics in real time       
Get SMS statistics (with scheduled process)    (tick)  

 

Other features

 HTTP, FormsSOAPRESTSMTP+FTPList+Frontend
SecurityHTTP with encrypted querystring
parameters and IP restriction9 in
most of the pages7

HTTP, user authentication, and IP
restriction9 for MailUpImport web service


HTTPS and user authentication for
other SOAP web services

OAuth2 with refresh tokenSTARTTLS Encryption is supportedsFTP and FTPs are supported

Authorization workflow
at application level
(sender and mailing
shall be approved before
before sending) 		HTTP with encrypted querystring
parameters in most of the pages8
New trial account activation  (tick)    
        

...

Expand
titleClick here to expand and see available methods
HTTP GET/POST and subscription forms

Subscription forms are based on HTTP GET/POST methods, which allow subscription unsubscription, check subscription status and update for a single recipient. These methods supports optin, confirmed optin, optout, fields update, unsubscription

REST API

Rest API is the most complete solution for managing a single subscriber (subscription status, group mebership and personal data fields) and it is the only MailUp solution that allows removal of a single recipient from a group. Adding a new recipient is an asynchronous process.

Webhooks

You can configure webhooks to enable a fast callback to your website when a recipient changes the subscription status or the personal data fields (e.g. by accessing to an autoprofile form). Callback method can be configured in order to include recipient's details as method parameter. Webhooks are managed by a worker process that is like a "frequent cron": you may experience some minutes of delay between the action and the corresponding callback. Bounces cannot be notified through webhooks

SOAP API

You can extend StartImportProcess method of MailUpImport SOAP API, that is designed for bulk import, to work with a single recipient. This method supports optin, confirmed optin, forced optin, optout, fields update, unsubscription. Adding a new recipient is an asynchronous process.

Synchronize recipients between your application and MailUp (i.e. import and/or export)

You may need to transfer a set of recipients, eventually with their personal data, from your application to MailUp; or viceversa. Solutions that work well with a single recipient may not be suitable for big numbers of recipients, in this case bulk solutions are needed.

...

Expand
titleClick here to expand and see available methods
FTP based integrations

You can use FTP Batch Processes for massive data transfer using files in CSV format. This feature can be used with very high numbers of recipients (import has been successfully tested with 4 millions of recipients in a single file) and it is configured on request by MailUp support team.

Expand
titleClick here to know more about available FTP transfer types

You can request this feature to

Data transfer is not in real time: it is usually configured as daily or weekly, but for specific cases even hourly data transfer can be done)

SOAP API

You can use MailUpImport SOAP API for an immediate import of recipients. In particular, you can use StartImportProcess method, eventually combined with NewImportProcess if the number of recipient is higher than 5000. These methods also allow a batch import as "pending", with the confirmation email that has to be manually sent using the adimin console account. SOAP API is not bidirectional, since it does not allow export of recipients.

SOAP API + FTP

You can get the best of FTP and SOAP API by using SendMessageNL API method, which performs scheduled sending to a group of recipients that is specified on a file. In this case you have to transfer the file to MailUp before calling the method. Export of recipients can be done with an FTP based integration.

REST API

Rest API allows immediate and bidirectional import and export of recipients. Due to restriction on HTTP channel, no more than 7MB can be uploaded with a single import. For the export of recipients the paging feature is recommended to keep control on maximum size of tranferred data. REST API is the only MailUp solution that allows removal of a single recipient from a group

Manage suppression lists (i.e. "do not email" lists of recipients)

You can contact MailUp support and ask configuration of an FTP based integration with a batch process that is configured to run hourly. This process has to be set to import in a new group (group name = file name) the recipents that are listed in the file to be imported. Then, when you access to MailUp admin console, you can schedule your campaign to be sent to "all subscribers except for the recipients that belong to a certain group". It should be easy for you to identify the right group because it has the name of the imported file plus a timestamp.

...

Expand
titleClick here to expand and see available methods
SMTP+

Email only. SMTP+ offers a scalable solution that is valid also for high volumes of transactional email messages to be sent. Delivery time depends on the bandwidth agreed for that console account.

SOAP API

SOAP API offers a good and scalable solution for transactional SMS with SendDirectSMS, while for email you can use SendSingleNewsletter or SendNewsletter but you must be aware of the existing limitations (refer directly to the documentation of these methods or check out the API use policy

...

Extract or display statistics

Email statistics are mainly the number and the details about opens and clicks, usually grouped by message. About SMS we can only know the delivery status and, in case of error, the error code.  

Expand
titleClick here to expand and see available methods
REST API

REST API offer the best suite about MailUp statistics, also allowing filtered and paged searches  

FTP

A batch export can be configured to periodically export on a CSV file the statistics of email and/or SMS messages. Export frequency can be set from 1 hour to 2 weeks. Contact us to ask a batch export for your console account (non standard configurations may require an extra fee). 

SOAP API 

WebService MailupReport provides a couple of methods to retreive statistics by message or by recipient. This solution works well only when returned data size is relatively small (e.g. lower than 100 items)

Frontend

Frontend pages provide a reduced version of some statistics pages of the console account, so that an external application can embed them. Available pages are similar to Summary Report and Opens report.

...