...
| Row | Optional | Description | Example |
|---|---|---|---|
| 1 | Y | Indicates the author of the file. It can be an email address or a mobile number with prefix included | name.surname@myprovider.com |
| 2 | Y | Date and time of sending, with format "YYYY-MM-DD HH:MM". If the row is empty or the data indicate a time in the past, MailUp schedules an immediate sending. If the format is incorrect, an import error will occur. This row is used only if the field in row 3 is validated as "I" (i.e. sending) | 2012-03-01 14:30 |
| 3 | N | Action to be performed: Sending or Queueing. Allowed values are "I" for sending (capital "i", from the first letter of the Italian word "invio"), and "A" for queueing (capital"a", from the first letter of the Italian word "accodamento"). Queueing option arranges the sending but does not perform it: you will have to access the MailUp system to schedule it. | I |
| 4 | N | ID of the sender. It can be a valid phone number, or an alphanumeric ID (max 11 characters, with restrictions on allowed characters) | MailUp |
| 5 | Y | ID of the MailUp list. It indicates the "environment", the cost center or the category in which messages and recipients will be inserted (the ID of the list must be indicated, and not its name) | 5 |
| 6 | N | Campaign name. It identifies the different sendings when looking through the statistics. If the row is left empty, messages will be automatically associated to the campaign "Default N", where "N" stands for the ID of the MailUp list | Special offers |
| 7 | N | Non-duplication univocal code. This row can be used to assign a univocal code to each file. The system will perform the import only if a file containing that specific code has never been imported to that account. You can freely choose which string to use and the convention according ti to which each new code is generated. | COD-20120312145300 |
...