| Tip | ||
|---|---|---|
| ||
Start choosing the use case that better fits your needs and then select a technical solution that covers your requirements. For each use case listed below, more technical solutions may be available, but they differ in some aspects. Check them out and follow the links they contain. A wide comparison matrix between available techincal solutions is available here. |
On this page:
Toc maxLevel 4
...
Manage single recipients (subscribe, unsubscribe, update)
MailUp provides several ways to add a new subscriber and manage either data fields or subscription status.
| Expand | ||
|---|---|---|
| ||
HTTP GET/POST and subscription formsSubscription 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 APIRest 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. WebhooksYou 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 APIYou 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. bulk 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 | ||
|---|---|---|
| ||
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 APIWebService 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) 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. |
...