Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Important Note

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

Where and how you want to import recipients

For each instance of Datasync (S)FTP import (from here on referred to as Instance) will be defined in which Lists, Groups, Channels and subscription status a recipient is imported into

Lists and Groups

It is possible to import all recipients in a fixed MailUp List.
In this case the Instance will be configured at the setup stage so that all the recipients are imported to a certain list.
If the import is based on a fixed MailUp List, will be possible to define the import in a fixed MailUp Group too. In this case the Instance will be configured at the setup stage so that all the contacts are imported to a certain group of the defined list.

It is possible to setup the Data Sync (S)FTP import to add and update recipients in more lists and groups.
In this case:

  • the CSV file must include fields 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.


Examples:

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;


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;


Destination list and the group can be also specified for every single user within the same file when importing subscribers to different groups: this way it won't be necessary to create more than one file.

Channels

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.

Important Note

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


Examples:

Subscribers have to be subscribed for email channel only, to list 2
email;idlist;idgroup
name.surname@myprovider.com;2;105
name2.surname2@myprovider.com;2;106
name3.surname3@myprovider.com;2;


subscribers have to be subscribed for SMS channel only, to list 2
phonenumber;idlist;idgroup
+39XXXXXXXXXX;2;105
+49YYYYYYYYYY;2;106
+30ZZZZZZZZZZ;2;
subscribers have to be subscribed for 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;


Subscription Status

It is possible to import all recipients to the destination channel in the destination lists only as subscribed or as unsubscribed.

In this case 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.

Important Note

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.

Important Note

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


Examples:

some subscribers 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.

Recipient fields Mapping

TBD

Import file properties

TBD





  • No labels