Page Comparison

Data Sync An (S)FTP import datasync allows to import recipients and related demographic data into your MailUp account by uploading a .csv file onto an SFTP server.
Using this service you can decide when running the file exchange to import data coming from an external application to MailUpfile exchange that leads to importing data in the account's database.

An instance of a Datasync (S)FTP Import Datasync (hereinafter referred as to as an Instance) will be configured to import data import email addresses, SMS mobile numbers or both, in one or more MailUp Lists and in one or more MailUp channel (email, SMS or both) and a . Along with the key fields Email and Mobile number, specific subset of recipient fieldsDuring the setup process you can define can as well be imported.

The setup process includes:

• Where and how you want the recipient to be imported
• Field mapping
• File properties
• Additional properties

All the import operation executed Every import session handled by the SFTP Datasync will be logged in the MailUp web application , in so that the result of each import process can be checked from the MailUp user interface at the Import status section.

Anchor
wah wah

Where and how you want to import recipients

Anchor
LG LG

Lists and Groups

It is possible to setup (S)FTP Data Sync Import in order to  to add and update recipients:

• into one specific MailUp List
  The Instance will be configured at the setup stage so that all of the recipients are imported to a certain going to be imported into one defined MailUp list.
  In this very case you can choose to import contacts recipients into a specific MailUp Group, too.
  The Instance will be configured at the setup stage so that all the contacts are imported to a certain group of the defined list.
  
  
• into different into several MailUp Lists and Groups
  Destination list lists and the group groups can be specified indicated for each and every single contact within recipient included in the csv file, so that it won't be necessary to create more than one file in order to import contacts recipients that belong to different lists /or groups.
  In this case the CSV file must include fields (the specifc columns (i.e. idList and IdGroup or ExternalGroupName) to provide   that indicate the destination list and possibly optionally the destination groups if foreseen, when needed.
  The Instance will be configured at the setup stage to read and use these fields.

Incremental mode or Full mode

Incremental import consists of files implies a csv file containing only the changes since the last import, while the Full mode import mode imports the entire database every time, replacing the previous data. 

The Full mode import mode can be configured at

• List Level
  • The subscription status of any existing subscribed recipients not included in the file will be updated to unsubscribedunsubscribed 
  • The subscription status of any existing unsubscribed recipients included in the file as subscribed (optout field =1. See subscription status paragraph for further details) will be updated to subscribed, with the exception of the Subscription status of Recipients unsubscribed due to hard bounce.
• Group Level
  • Any existing recipient in the group who is not included in the file will be removed from the group
  • Any recipients includet included in the file will be added to the group.

email;idlist;idgroup
name.surname@myprovider.com;2;105
name2.surname2@myprovider.com;2;106
name2.surname2@myprovider.com;2;

email;idlist;idgroup
name.surname@myprovider.com;2;105
name2.surname2@myprovider.com;2;106
name2.surname2@myprovider.com;2;

Anchor
SS SS

Subscription Status

It is possible 

• to import all of the contacts contained recipients contained in the file as subscribed or as unsubscribed.
  The Instance will be configured at the setup stage so that all of the recipients are will be imported in a certain specific subscription registration status and only in that subscription status.

• or to import contacts recipients contained in the file as subscribed or unsubscribed based on data provided in the CSV file.
  Recipients' subscription status can be specified for every single contact within the each recipient contained in the csv file so that it won't be necessary to create more than one file to import subscribed and unsubscribed contacts.
  The CSV file must include a field column (optout) to provide indicate the Subscription Status of each recipient.
  The Instance will be configured at the setup stage to read and use this field.that column value to rule the subscription status as follows:
• When the value of the field column is 1, the recipients will be imported as subscribed.
• When the value of the field column is 0, the recipients will be imported as unsubscribed.

email;idlist;subscription_status
name.surname@myprovider.com;2;1
name2.surname2@myprovider.com;2;0
name3.surname3@myprovider.com;2;1

Anchor
C C

Channels

It is possible to import all recipients

• only into MailUp email channel context: recipients are going to be imported using only their Email address
• only onto MailUp SMS channel context: recipients are going to be imported using only their Mobile address
• or into both MailUp email and MailUp SMS channelscontexts, where the recipients are imported using both Email and Mobile number as a key.

Based on how the instance is configured the CSV file must include fields to provide is to include columns that display the email address and/or the SMS phone number that identify the recipients in MailUp.

email;idlist;idgroup
name.surname@myprovider.com;2;105
name2.surname2@myprovider.com;2;106
name3.surname3@myprovider.com;2;

phonenumber;idlist;idgroup
+39XXXXXXXXXX;2;105
+49YYYYYYYYYY;2;106
+30ZZZZZZZZZZ;2;

phonenumber;email;idlist;idgroup
+39XXXXXXXXXX;name.surname@myprovider.com;2;105
+49YYYYYYYYYY;name2.surname2@myprovider.com;2;106
+30ZZZZZZZZZZ;name3.surname3@myprovider.com;2;

Anchor
FM FM

Fields Mapping

The Instance will be be configured at the setup stage so that it can associate the fields colums of the CSV file with the personal fields of your MailUp account.

The CSV file structure/layout is free100% configurable, but it is necessary to arrange the requires to comply to a correct correspondence between the fields in the file and:

• the recipients personal fields, 
• the recipients identifiers fields (email address or phone number),
• the recipients destination fields (lists, groups, subscriprion status) of the MailUp console.

email;name;second name;Location;Job Title;idlist;subscription_status
name.surname@myprovider.com;John;Smith;Everywhere;Manager;2;1
name2.surname2@myprovider.com;Martha;Smith;Anywhere;Manager;2;0
name3.surname3@myprovider.com;Gordon;Smith;Anywhere;Operative;2;1

In case of empty personal data fields, they have their column has to be specified anyway, without any value.

email;name;second name;Location;Job Title
name.surname@myprovider.com;John;Smith;Everywhere;   -> Last field is empty
name2.surname2@myprovider.com;Martha;Smith;;Manager  -> fourth field is empty
name3.surname3@myprovider.com;;Smith;;Operative      -> second and fourth field are empty

Anchor
FP FP

File Properties

Recipients’ fields Data is always imported as text and fields must not contain more than 200 characters. 

Is it is possible to chooseset:

• the character to be used as a field separator can be chosen, keeping in mind that just one type of separator is allowed in a file and that the separator ";" should not be used at the end of a line, after the last field.
• the text delimiter enclosing the column values

If needed, the first row of the file can contain a header row that gives the columns a name.

email,name,second name,Location,Job Title
name.surname@myprovider.com,John;Smith,Everywhere,   
name2.surname2@myprovider.com,Martha,Smith,,Manager
name3.surname3@myprovider.com,,Smith,,Operative

email;name;second name;Location;Job Title
name.surname@myprovider.com;John;Smith;Everywhere;
name2.surname2@myprovider.com;Martha;Smith;;Manager
name3.surname3@myprovider.com;;Smith;;Operative

email;name;second name;Location;Job Title
name.surname@myprovider.com;John;Smith;"Here;There;someplace";HouseKeeper
name2.surname2@myprovider.com;Martha;Smith;;Manager
name3.surname3@myprovider.com;;Smith;;Operative

name.surname@myprovider.com;John;Smith;Everywhere;HouseKeeper
name2.surname2@myprovider.com;Martha;Smith;;Manager
name3.surname3@myprovider.com;;Smith;;Operative

Anchor
AP AP

Additional Properties

For every configured importdata sync, once you upload your file in the common space a file is uploaded to the SFTP location (on the MailUp SFTP spaceserver), the import process will be executed carried out and completed as soon as possible (the execution time depends on the number of contacts you are going to import and the operations you are going to performrecipients and the columns the csv contains). 

If preferred, a different third party FTP / SFTP space server can be used for the file exchange. If you are using your personal FTP space server, the import will be executed at the frequency defined at setupschedule defined in the configuration.

• The instance can be configured for to overwrite existing field value saved in MailUp if import fields when then csv columns are empty, rather than ignore empty values provided in the CSV fileas opposed to having the data sync to ignore entirely the csv columns displying no value.
  
• You can configure one or serveral email addresses to receive notification email messages that will be notified with an email message with the result of the import for each file managed by the instance.
  Addresses process every time a file is imported.
  Multiple addresses must be added separated by ; (semicolon).

email1@mailup.com;email2@mailup.com;email3@mailup.com  -> The instance will sent a notification email to these three addresses for each processed csv file.