Info |
---|
|
FTP-based data synchronization is not available by default (additional charge), but our technicians can set it up for you upon request, contact your account manager to get a quote. To have a data synchronization set up, you need to have an active MailUp account (not a free trial). |
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 system or application to MailUp.
An instance of a Datasync (S)FTP import 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 to import recipientsLists and Groups
It is possible to import all recipients in a fixed MailUp List.
In this case the Instance 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 list and possibly the destination groups if foreseen.
the Instance The Instance will be configured configured at the setup stage to read and use these fields.
...
Code Block |
---|
language | text |
---|
title | some subscribers have to be subscribed to list 2, group 105 some others in group 106 and some others in no group |
---|
|
email;idlist;idgroup
name.surname@myprovider.com;2;105
name2.surname2@myprovider.com;2;106
name2.surname2@myprovider.com;2; |
Code Block |
---|
language | text |
---|
title | some subscribers have to be subscribed to list 2, groups 105 and 120, some others to list 3, in no group |
---|
|
email;idlist;idgroup
name.surname@myprovider.com;2;105,120
name2.surname2@myprovider.com;2;120
name.surname@myprovider.com;3; |
...
It is possible to import all recipients only in the /wiki/spaces/MUG/pages/36866874 channel, or in the /wiki/spaces/MUG/pages/36864980 channel, or both.
The Instance will be be configured at the setup stage so that all the recipients will be imported only in the /wiki/spaces/MUG/pages/36866874 channel or in the /wiki/spaces/MUG/pages/36864980 channel or both.
Based on how the instance in configured the CSV file must include fields to provide the email address and/or the SMS phone number that identify the recipients.
Info |
---|
|
If the SMS phone number provided in the CSV file doesn't have the international prefix, MailUp will import the recipients using the default prefix defined for the destination list |
...
Panel |
---|
borderColor | black |
---|
borderWidth | 1 |
---|
borderStyle | solid |
---|
|
Destination groups must be created in advance in the MailUp console, at the page Recipients > Groups
List IDs and group IDs are listed at the page Settings > Codes table |
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.
Expand |
---|
|
Code Block |
---|
language | text |
---|
title | subscribers have to be subscribed for EMAIL AND SMS channel, to list 2 |
---|
|
| Subscribers Some contacts have to be subscribed |
|
| for email channel only, to list 2, group 105 some others in group 106 and some others in no group |
| email;idlist;idgroup
name.surname@myprovider.com;2;105
name2.surname2@myprovider.com;2;106
| name3surname3@myprovidersurname2@myprovider.com;2; |
| subscribers Some contacts have to be subscribed |
|
| for SMS channel only, |
phonenumber;idlist;idgroup
+39XXXXXXXXXX;2;105
+49YYYYYYYYYY;2;106
+30ZZZZZZZZZZ;2; |
phonenumber;, groups 105 and 120, some others to list 3, in no group |
| email;idlist;idgroup
| +39XXXXXXXXXX;name.surname@myprovider.com;2;105
| +49YYYYYYYYYY;name2.surname2@myprovider.com;2;106
| +30ZZZZZZZZZZ;name3.surname3@myprovidername2.surname2@myprovider.com;2; |
|
Subscription Status
It is possible possible
...
...
- contacts contained in the
...
...
- 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.
Info |
---|
|
TDB gestione disiscritti |
...
- TBD Disiscritti, verificare perché non sono sicuro in questo caso
|
- or to import recipients as subscribed or unsubscribed based on data provided in the CSV file.
In this case:
- the 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 Subcription Subscription Status of each recipients. recipient.
The Instance will be configured at the setup stage to read and use this field. - When the value of the field
is - is 1, the recipients will be imported as subscribed.
- When the value of the field is 0, the recipients will be imported
as unsubscribed.the Instance will be configured at the setup stage to read and use this field
Info |
---|
|
- If a subscriber is already present in the destination list as unsubscribed and will be imported as subscribed, its subscription status will be updated to subscribed. Subscription status of Recipients unsubscribed due to hard bounce won't be changed.
- If a subscriber is already present in the destination list as subscribed and will be imported as unsubscribed, its subscription status will be updated to unsubscribed.
|
...
|
| some subscribers Some contacts have to be subscribed to list 2, some others have to be unsubscribed from list 2 |
| email;idlist;subscription_status
name.surname@myprovider.com;2;1
name2.surname2@myprovider.com;2;0
name3.surname3@myprovider.com;2;1 |
|
In this case subscribed and unsubscribed recipients can be also specified within the same file: this way it won't be necessary to create more than one file.
...
ChannelsIt 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.
Info |
---|
|
- If the SMS phone number provided in the CSV file doesn't have the international prefix, MailUp will import the recipients using the default prefix defined for the destination list
- It is very important to check the correct syntax of email addresses, i.e. that there are no forbidden characters or spaces. Spaces before and after the address are removed automatically during the import process.
|
Expand |
---|
|
Code Block |
---|
language | text |
---|
title | Some contacts have to be subscribed to EMAIL channel, to list 2 |
---|
| email;idlist;idgroup
name.surname@myprovider.com;2;105
name2.surname2@myprovider.com;2;106
name3.surname3@myprovider.com;2; |
Code Block |
---|
language | text |
---|
title | Some contacts have to be subscribed to SMS channel only, to list 2 |
---|
| phonenumber;idlist;idgroup
+39XXXXXXXXXX;2;105
+49YYYYYYYYYY;2;106
+30ZZZZZZZZZZ;2; |
Code Block |
---|
language | text |
---|
title | Some contacts have to be subscribed to EMAIL AND SMS channel, to list 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; |
|
Fields MappingThe 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 identifiers fields (email address or phone number),
...
- the recipients destination fields (lists, groups, subscriprion status) of the MailUp console.
...
...
|
- The CSV produced by your CRM have the following structure:
Code Block |
---|
| 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 |
- Your are interested read that data from the CSV file to Update the recipients data in your MailUp account.
- In your MailUp Account are provided the following Recipient fields:
- email address,
- field 1: name,
- field 2: second name,
- field 3: Title;
- you aren't interested to store the location of subscribers.
In this case, the fields in every row will be associated with the following personal data fields: Csv Fields | MailUp fields |
---|
position | title | id | field | 1 | email |
| email address | 2 | name | 1 | name | 3 | second name | 2 | second name | 4 | Location |
|
| 5 | Job Title | 3 | Title | 6 | idlist |
| destination List | 7 | subcription_status |
| subscription |
|
...
Import file properties
...
File PropertiesRecipients’ 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.
Additional PropertiesFor 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.
TBD Non sovrascrivere campi vuoti e notifica