...
The database of contacts (full or diff), with status indication (subscribed/unsubscribed) and insertion in lists or groups (infinite groups can be created within a list) must be moved from the CRM to a FTP space. The status (subscribed/unsubscribed) is list-specific. For further details please see the chapter “Batch FTP synchronization”. MailUp generates the flow of statistics and unsubscriptions towards the CRM in two ways:
...
via batch FTP mode. Unsubscriptions could also be exported via API call to customer’s public procedure (following specifications provided by the customer).
Web services or APIs
Pros: real time
...
A code section is added to all the CRM pages where the user file is modified (personal data and status subscribed/unsubscribed in particular). This section updates the MailUp database via standard APIs or Web Services. MailUp generates the flow of statistics and unsubscriptions towards the CRM in two ways:
...
via batch FTP mode
...
. Unsubscriptions could also be exported via API call to
...
customer’s public procedure (following specifications provided by the customer).
The user can then switch from the CRM to MailUp by just pressing one button (an auto log-in procedure can be activated), manage the contacts inside the CRM but then needs to access to MailUp in order to send the message. The user logs in to the MailUp console without password, composes the message, chooses the target (browsing by group, list or applying filters), then sends the message and analyzes sending statistics.
...