Versions Compared

Key

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

...

Campo

ID

Indirizzo email

111

prefisso sms

222

numero sms

333

numero completo sms (prefisso sms + numero sms)

444

...

Campo

...

ID

...

Indirizzo mail

...

111 – Valore fisso

...

Cognome

...

2

...

Nome

...

3

...

Data di Nascita

...

4

...

Nazionalità

...

5

...

Sesso

...

6

...

Telefono

...

7

...

Campo

Posizione nei record del file

Nome

1

Cognome

2

Data di Nascita

3

Codice fiscale

4

Sesso

5

Nazionalità

6

Indirizzo mail

7

Telefono

8

Come si può vedere, il codice fiscale non compare in anagrafica e quindi non potrà essere importato. Per esso si dovrà indicare un campo vuoto nella riga di mappatura che sarà
3;2;4;;6;5;111;7
Mentre le altre righe del file (cioè dalla seconda in poi) avranno un formato di questo tipo:
Mario;Rossi;1975-07-3;rssmro75g13f103h;M;ITALIAN;mario.rossi@provider.com;12345678
Paola;Verdi;1981-01-11;vrdpol81h11f234u;F;ITALIAN;paola.verdi@provider.com;987654321
Pierino;Prati;1945-03-12;prtprn45c12o256h;M;ITALIAN;pierino.prati@provider.com;
Manuela;Cabrini;1990-04-29;cbrmnl90h29m945i;M;ITALIAN;manuela.cabrini@provider.com;
| The CSV file must contain a header row that maps the values contained in that column to a corresponding field in the MailUp system. In MailUp there are:

  1. Some special fields that are reserved for e-mail, mobile phone number, and mobile phone number + country code.
  2. Customizable personal data fields. Personal data fields (e.g. first name, last name, etc.) have a numeric ID that goes from 1 to 39 (it could be less than 39 for some subscription plans, please ask if you need an uprgade to 39).

Special Fields

MailUp contains the following special fields, which cannot be modified.

Field NameField ID
E-mail address111
Mobile phone number's country code222
Mobile phone number333
Complete mobile phone number (country code + number)444

Example

A file to be imported shall contain a header row and one record for each recipient to be imported. The '|' (pipe) symbol is used as a separator and each row must contain exactly the same number of columns.

Basically, as soon as you respect the rules above, you are free to choose the type, order and number of columns you prefer. In this paragraph you can have a look at some examples, 

Subscription on Email channel

Let's say that your CSV file contains these columns:

Field Name

Column position

Field ID*Example
First Name11Peter
Last name22Smith
Date of Birth3101978-03-16
Gender49M
Country68UK
E-mail address7111psmith02@example.com
City86London

*MailUp personal field ID or special field ID (refer to previous table for special fields)

This is an example of the file content

Code Block
titleUse 111 in the header row for the email address. For the other columns use the ID of the corresponding field in MailUp.
1|2|10|9|8|111|6
Peter|Smith|1978-03-16|M|UK|psmith02@example.com|London
Maria|Rossi|1963-12-21|F|IT|rossi@example.com|Roma
...

 

Subscription on SMS channel

For international prefix and mobile number you can either use two separate fields or a single field

Code Block
titleTwo separate fields (use 222 and 333 in the header row). If you leave the int. prefix empty, the default list settings will be used
1|2|10|9|8|222|333|6
Peter|Smith|1978-03-16|M|UK|123000000|123000000|London
...
Code Block
titleOne single field for mobile number (use field ID 444 in the header row)
1|2|10|9|8|444|6
Peter|Smith|1978-03-16|M|UK|+44123000000|London
...


Subscription on both Email and SMS channels

Mixing the scenarios described above, here is an example with both email and SMS

Code Block
titleOne single field for mobile number (use field ID 444 in the header row)
1|2|111|10|9|8|444|6
Peter|Smith|psmith02@example.com|1978-03-16|M|UK|+44123000000|London...