Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
...
...
...
...
Info | ||
---|---|---|
| ||
(S)FTP-based data |
...
synchronizations are not available |
...
out-of-the-box (additional |
...
To have a data synchronization set up, you need to have an active MailUp account (not a free trial).
...
costs may apply), contact your sales representative for an estimation. (S)FTP Data synchronization are not available to MailUp trial accounts |
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.
...
The system awaits for a csv file to be uploaded and then it is immediatelly handled and imported, so there's no actual schedulation to set as the system will run and import any file as soon as it is submitted.
An instance of a
...
(S)FTP
...
Import Datasync (hereinafter referred as to an Instance) will be configured to
...
import /wiki/spaces/MUG/pages/36866874 addresses, /wiki/spaces/MUG/pages/36864980 mobile numbers or both
...
, in one or more MailUp Lists. Along with the key fields Email and Mobile number, specific subset of recipient fields 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
Every import session handled by the SFTP Datasync will be logged in the MailUp web application so that the result of each import process can be checked from the MailUp user interface at the Import status section.
Info | ||
---|---|---|
| ||
The standard behavior of the MailUp recipients import process is that:
|
...
An (S)FTP import datasync can overcome the subscription bevahiors as described below |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
(S)FTP Data Sync Import 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
...
- going to be imported into one defined MailUp list.
...
- In this very case you can import recipients into a specific MailUp Group, too.
- into several MailUp Lists and Groups
Destination lists and the groups can be indicated for each and every single recipient included in the csv file, so that it won't be necessary to create more than one file in order to import recipients that belong to different lists or groups.
In this case
...
- the CSV file must include
...
- the specifc columns (i.e. idList and IdGroup or ExternalGroupName) that indicate the destination list and optionally the destination groups, when needed.
The Instance will be configured at the setup stage to read and use these fields.
...
Info | ||
---|---|---|
| ||
Destination groups must be created beforehand in the MailUp web application, 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 implies a csv file containing only the changes since the last import, while the Full import mode imports the entire database every time, replacing previous data.
The Full 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 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 included in the file will be added to the group.
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
Anchor | ||||
---|---|---|---|---|
|
It is possible
- to import all of the 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 will be imported in a specific subscription registration status.
Info | ||
---|---|---|
| ||
|
- or to import recipients contained in the file as subscribed or unsubscribed based on data provided in the CSV file.
Recipients' subscription status can be specified for 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 column (optout) to indicate the Subscription Status of each recipient.
The Instance will be configured at the setup stage to read and use that column value to rule the subscription status as follows: - When the value of the column is 1, the recipients will be imported as subscribed.
- When the value of the column is 0, the recipients will be imported as unsubscribed.
Info | ||
---|---|---|
| ||
|
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Anchor | ||||
---|---|---|---|---|
|
It is possible to import all recipients
...
- only into MailUp email context: recipients are going to be imported using only their Email address
- only onto MailUp SMS context: recipients are going to be imported using only their Mobile address
- or into both MailUp email and MailUp SMS contexts, where the recipients are imported using both Email and Mobile number as a key.
Based on how the instance
...
is configured the CSV
...
file is to include columns that display 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
|
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
Anchor |
---|
...
|
...
|
...
It is possible to import all recipients to the destination channel in the destination lists only as subscribed or as unsubscribed.
...
Fields Mapping
The Instance will be be configured at the setup stage so
...
Info | ||
---|---|---|
| ||
TDB gestione disiscritti |
It is possible to import recipients to the destination channel in the destination lists as subscribed or unsubscribed based on data provided in the CSV file.
In this case:
- the CSV file must include field to provide the Subcription Status of each recipients.
- 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.
- the Instance will be configured at the setup stage to read and use this field.
Info | ||
---|---|---|
| ||
|
Examples:
Code Block | ||||
---|---|---|---|---|
| ||||
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.
Recipient fields Mapping
TBD
Import file properties
...
that it can associate the colums of the CSV file with the personal fields of your MailUp account.
The CSV file structure/layout is 100% configurable, it 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.
Expand | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||
In this case, the columns in every row will be bound to the following personal data fields:
|
In case of empty personal data fields, their column has to be specified anyway
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Anchor | ||||
---|---|---|---|---|
|
Recipients’ fields Data is always imported as text and fields must not contain more than 200 characters.
it is possible to set:
- the character to be used as a field separator, 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.
Expand | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
|
Anchor | ||||
---|---|---|---|---|
|
For every configured data sync, once a file is uploaded to the SFTP location (on the MailUp server), the import process will be carried out and completed as soon as possible (the execution time depends on the number of recipients and the columns the csv contains).
If preferred, a third party FTP / SFTP server can be used for the file exchange. If you are using your personal FTP server, the import will be executed at the schedule defined in the configuration.
- The instance can be configured to overwrite existing field value saved in MailUp when then csv columns are empty, as opposed to having the data sync to ignore entirely the csv columns displying no value.
- You can configure one or serveral email addresses that will be notified with an email message with the result of the import process every time a file is imported.
Multiple addresses must be added separated by ; (semicolon).
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Table of Contents |
---|