Imports

Creating the Import File

Your import file must meet the following requirements:

• Format: When you create the file of subscriber data to be imported into the application, you must save it as a tab-delimited TXT file or a comma-delimited CSV file. (Many applications, such as Excel, offer these formats as "save as" options.) A CSV file is a format used to store tabular data in which numbers and text are stored in plain-text form that can be easily written and read in a text editor. 
• File location: Save the import file on a locally mapped drive. You need to browse to this file from within the application, and only files located on a locally mapped drive are supported ( C:\, D:\, etc.); you cannot upload a file from a UNC path (such as \\ abcfiles\).
• Header row: A header row (a row at the top of the file labeling the columns in the file) 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 for you by default. For example, if you're importing a group of Unsubscribed subscribers, you'll need a column labeled "Subscriber Status" with "Unsubscribed" in each row. See Mapping Attributes for more information. 
• Attribute data type: If you're importing subscriber attributes, the data in the import file must be of the same data type (text, date, or numeric) as the attribute field in the application.
  

  Note: If you're importing an attribute that already exists in the application, a warning will appear telling you that attribute already exists.

• Attributes with restricted values: If you're 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.
• Preferences: If you're importing subscriber preference data, your import file should use only the values Yes and No.

For an example, view this sample import file. 

Tips for Successful Imports

Follow these tips for creating a successful import file:

• Delete any columns in the file that are not being 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. Given that email address is a required field and every row in your file must contain an email address value, 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 contains 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 Microsoft Excel-created files. If your import file was not created in Excel, you can avoid most errors by opening the file in Excel and resaving it, as follows:

• Paste into a new spreadsheet: If you're having trouble importing a file and you can't figure out why, try copying all of the cells containing data from your problematic file into a brand-new spreadsheet. When you paste the data into the new spreadsheet, use the Paste Special option and choose to paste just the Values in the Paste Special dialog box in Microsoft Excel.

Mapping Attributes

Mapping attributes refers to matching the columns in your import file to the attributes names you created in the ExactTarget application. In essence, you "map" the import column to the attribute. For example, if you have an attribute in ExactTarget called First Name, your import file should contain a column called First Name. When you import, any value in the First Name column will live in the First Name attribute.