Batch FTP synchronization is a file exchange between the customer's system and MailUp, usually in .csv format. This exchange takes place through a FTP protocol. (available as sFTP e FTPs as well, on request).
Synchronization modes described in this section are not available by default, but our technical team can set them up and activate them following customers' requests. To have a batch synchronization set up, an active account is required (not a free trial) and technical details have to be agreed with our support team (email@example.com). No extra fee will be charged, except for personalizations, or should a huge amount of space on MailUp FTP servers be required to exchange the data. In order to have a quick quote, please contact our sales department (firstname.lastname@example.org).
Once the synchronization has been set up, it is possible to decide how often and at what time the automatic file exchange process will be executed.
As this synchronization can go in both directions (i.e. from the customer's system to MailUp and vice versa), it can be set up in one direction only or both, depending on the customer's needs.
Batch synchronization allows to automate the following processes:
- Moving to MailUp the recipients list taken from a file provided by the customer and importing it to a MailUp list
- Extracting from MailUp a list of unsubscribers and saving it in a file stored in a repository shared with the customer
- Extracting from MailUp statistics down to the user and to the message level (opens and clicks) and saving them in a file stored in a repository shared with the customer
- Extracting the data at (2) and (3) in one single file
- Extracting statistics about text messages delivery and saving them in a file stored in a repository shared with the customer
- Extracting a list of subscribers in MailUp and saving it in a file stored in a repository shared with the customer
Example: every day at 4 am, the customer's system exports a .csv file containing the latest update for the recipients' personal data, to be moved to MailUp. At 4:30 am MailUp accesses the file via FTP protocol and imports its content to a predefined list. The fields in each row of the file must be mapped the same way as MailUp personal data fields, so that they can update the MailUp database. At 5 am a procedure extracts unsubscribers and statistics and saves them in separate files stored in a repository shared with the customer
Please not that this example refers to a synchronization in two directions, but as explained above it can be set up in one direction only.