Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

name.surname@myprovider.com;name;surname;Mycompany Inc;0
namesurname@myprovider.com;name;surname;Mycompany Inc;1

MailUp automatically receives spam reports from the main international ISPs (Yahoo, Hotmail , AOL…) when recipients click the button "Junk" o "Spam" in order to unsubscribe. It is very important to promptly remove these users from your contacts, to avoid reputation problems that would end up in all the messages sent to that specific provider being tagged as "spam". For these reasons, forcing a user as subscribed is not recommended.

Subscription to lists or groups

...

File exchange takes place by means of a FTP repository located on MailUp's servers, but the following solutions are possible as well:

Protocol

Shared repository on customer's servers

Shared repository on MailUp's servers

FTP

Available
You share the access credentials with the MailUp staff

Available: please check with our sales department if an extra fee for the storing space is to be charged
The MailUp staff shares the access credentials with you

sFTP (FTP

su

over SSH, port 22)

Available
You share the access credentials with the MailUp staff

Available
The MailUp staff shares the access credentials with you

FTPs (FTP

su

over SSL)

Not available

Not available

The MailUp system deletes the file after the import, so it will have to be able to access the shared repository with a user that has deletion permission on the shared FTP folder.

...

This value cannot be handled as a personal data field, but it will be stored in a backup table and included in the output data (outcomes) to allow the customer's system to track a campaign. Should you need such a field in the file, reporting this kind of requirement at setup stage is highly recommended. 


Example with specific codes for the pair (user, campaign):

When importing, the records specify that John Smith and Mary Johnson have respectively the codes COD0001 and COD0002 for sending the message A1 scheduled for a certain day

john.smith@myprovider.com;COD0001;A1
mary.johnson@myprovider.com;COD0002;A1

A week later, the same message with code A1 is scheduled again for sending, but this time different codes are used

john.smith@myprovider.com;COD0011;A1 
mary.johnson@myprovider.com;COD0012;A1 

 
The use of different codes allows the user to get different outcomes (see Data Sync FTP exports from MailUp for details) in order to differentiate the feedback on the first and the second sending of the same message

Special cases and personalizations

...

Import works the same way; when importing contacts for text messaging, the field containing the phone number is mandatory and univocal, i.e. there must not be two recipients with the same phone number. Imported phone numbers should always be preceded by the international prefix. The MailUp system adds the predefined international prefix for the destination list, should the prefix be missing in the import file.
It is also possible ti perform a multichannel import, i.e. of both email addresses and phone numbers. Please note that importing contacts for two channels makes import last longer. 


Should you need any further information or custom integrations please do not hesitate to contact your account manager.