Page Comparison

Data Sync (S)FTP import allow you to import recipients and related data into your MailUp Account by simply 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 MailUp.

An instance of a Datasync (S)FTP Import (hereinafter referred to as Instance) will be configured to import data in one or more MailUp Lists and in one or more MailUp channel (/wiki/spaces/MUG/pages/36866874, /wiki/spaces/MUG/pages/36864980or both) and a specific subset of recipient fields

During the setup process you can define:

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

Anchor
wah wah

Where and how you want to import recipients

Anchor
LG LG

Lists and Groups

It is possible to setup Data Sync Import in order to add and update recipients:

• into one specific MailUp List
  The Instance will be configured at the setup stage so that all the recipients are imported to a certain list.
  In this case you can choose to import contacts 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 MailUp Lists and Groups
  Destination list and the group can be specified for every single contact within the file so that it won't be necessary to create more than one file to import contacts to different lists/groups.
  In this case the CSV file must include fields (idList and IdGroup or ExternalGroupName) to provide the destination list and possibly the destination groups if foreseen.
  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 containing only the changes since the last import, while the Full mode import imports the entire database every time, replacing the previous data. 

The Full mode import can be configured at

• List Level
  • The subscription status of any existing subscribed recipients not included in the file will be updated to unsubscribed
  • 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 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 the contacts contained in the file as subscribed or as unsubscribed.
  The Instance will be configured at the setup stage so that all the recipients are imported in a certain subscription status and only in that subscription status.

• or to import contacts 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 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 (optout) to provide the Subscription Status of each recipient.
  The Instance will be configured at the setup stage to read and use this field.
• When the value of the field is 1, the recipients will be imported as subscribed.
• When the value of the field 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
• only onto MailUp SMS channel
• or into both MailUp email and MailUp SMS channels

Based on how the instance is configured the CSV file must include fields to provide 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 of the CSV file with the personal fields of your MailUp account.

CSV file structure is free, but it is necessary to arrange the 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 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 possible to choose:

• 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.

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 import, once you upload your file in the common space (on the MailUp SFTP space), the import process will be executed 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 perform). 

If preferred, a different FTP / SFTP space can be used. If you are using your personal FTP space the import will be executed at the frequency defined at setup.

• The instance can be configured for overwrite existing field value saved in MailUp if import fields are empty, rather than ignore empty values provided in the CSV file.
  
• You can configure email addresses to receive notification email messages with the result of the import for each file managed by the instance.
  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.