On this page:
...
Since email statistics are aggregated per by message, be aware that when you reuse a previously sent message then it is likely that you will not be able to split the aggregated statistics. You can make a copy of the message instead of reusing it.
| Expand | ||
|---|---|---|
| ||
SOAP APIYou can use CreateNewsletter to create a new email message, Clone Message to make a copy of an existing one and finally you can use SendNewsletter to program an immediate or scheduled sending (at sending time you will be able to specify who will receive that campaign). For SMS you can use a similar approach with CreateSMS and SendSMS methods. Since SMS statistics are very poor when compared to email, there was no need to implement a "clone SMS" method SOAP API + FTPEmail only. As an alternative to importing recipients and then calling SendNewsletter , method SendMessageNL allows a bulk import and the scheduling of a specified email message with a single operation. Refer to method documentation to learn more about this method and its known limitations REST APIEmail only. REST API offers the most complete suite form creating and managing an email message, but it still has some limitations about sending that are going to be removed in some of the next product releases:
FTPSMS Only. FTP solution offers the capability to import (bulk) recipients and send them SMS messages that can be fully customized for each recipient. Refer to "Text message (SMS) sending from .CSV file" for more info. |
Send transactional emails/SMS
SMTP+
The term "transactional" is usually used to distinguish messages that do not belong to "Promotional" or "Bulk" categories.
| Expand | ||
|---|---|---|
| ||
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 APISOAP API offers a good and scalable solution for transactional SMS with SendDirectSMS, while for email you can |
...
...
...
but you must be aware of the existing limitations (refer directly to the documentation of these methods or check out |
...
the API use policy |
Read 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 | ||
|---|---|---|
| ||
REST APIREST API offer the best suite about MailUp statistics, also allowing filtered and paged searches FTPA 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 |
...
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. |
...
REST API
...
lower than 100 items) FrontendFrontend 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. |