You are here:
Import File Requirements for Email Studio
To ensure compatibility with Email Studio in Marketing Cloud Engagement, import files have some detailed requirements.
| Requirement | Description |
|---|---|
| Format | When creating the file of subscriber data to be imported into the application, save it as a tab-delimited .txt file or a comma-delimited .csv file. Many applications, such as Excel, offer these formats. |
| File location | Save the import file on a locally mapped drive. Browse to this file from within the application. Only files on a locally mapped drive are supported. You cannot upload a file from a UNC path, such as \\ abcfiles\. |
| Header row | A header row is recommended for mapping purposes. If the labels in the header row exactly match the names of the attributes in your account, the application maps the data by default. For example, if importing a group of unsubscribed subscribers, you need a column labeled "Subscriber Status" with "Unsubscribed" in each row. |
| Attribute data type | If you're importing subscriber attributes, the data in the import file must be of the same data type, that is, text, date, or numeric, as the attribute field in the application. If you're importing an attribute that exists in the application, you receive a warning. |
| Attributes with restricted values | If importing subscriber data into attribute fields that restrict the possible values, the import data must exactly match one of the values defined as allowable for that attribute. |
| Use correct values for subscriber preference data | If you're importing subscriber preference data, use one of the following value pairs:
|
| Delete any columns in the file that are not used in the import | Limiting the import file to only the data that is imported ensures that the system processes the file as efficiently as possible, saving time. |
| Make the email address the last column in the file | Email address is a required field and every row in your file must contain an email address, making it the last column in the file ensures that the last column of every row contains data. The system can process the file more efficiently when the last column of the row contains data because the system can then recognize how many columns each row has. |
| If in doubt, save the file in the tab-delimited format rather than the comma-delimited format | If any of the values in your file contain a comma (as part of the value), you must use the tab-delimited format rather than the comma-delimited format. |
| Save the file in Microsoft Excel | The application is designed to handle files created in Microsoft Excel. If you didn't create the import file in Excel, avoid most errors by opening the file in Excel and resaving it. |
| Paste into a new spreadsheet | If you have trouble importing a file and can't figure out why, copy all the cells containing data into a new spreadsheet. When you paste the data into the new spreadsheet, use the Paste Special option and choose to paste just the values in Excel. |
| Use the supported date formats | Download a list of supported date formats. Use a supported date format when you upload into a date-type field in a subscriber attribute or data extension. When you import dates into lists or a data extension, enter the date in the same format as is indicated on your account. If the userdate format is different from the account, use the format of the account. |
| Map the columns in your import file to the attribute names in Email Studio | To map attributes, match the columns in your import file to the attributes names you created. In other words, map the import column to the attribute. For example, if you have an attribute in Email Studio called First Name, the import file should contain a column called First Name. When you import, any value in the First Name column lives in the First Name attribute. |
