Engage supports a variety of file formats and data within subscriber import files. Below are requirements and best practice tips for creating those files.


Import File Requirements


Your import file must meet the following requirements to be imported either manually or via a scheduled import in Engage.



When you create a file of subscriber data to be imported in to Engage, you must save it in one of the following file formats.


Format    
File Extension(s)
Details/Notes
Text (tab-delimited) 
.txt/none
Text format. Tab-delimited. Supports either no text qualifiers or double quotes. Supports UNIX (LF), Windows (CRLF), and Macintosh (CR) end-of-line characters.
Text (pipe-delimited)  
.txt/none
Text format. Pipe-delimited. Supports either no text qualifiers or double quotes. Supports UNIX (LF), Windows (CRLF), and Macintosh (CR) end-of-line characters.

CSV (comma-delimited)

.csv
Text format. Comma-delimited. Supports either no text qualifiers or double quotes. Supports UNIX (LF), Windows (CRLF), and Macintosh (CR) end-of-line characters.
Excel Workbook
.xlsx
Default Office Excel 2007+ XML-based file format.

Excel 97-2003 Workbook  

.xls
The Excel 97 - Excel 2003 Binary file format (BIFF8).

      


Header row:

A header row is advised for mapping purposes. If the labels in the header row exactly match the names of subscriber attributes in your account, the Engage application will automatically map the data for you by default. If a Header Row is not included, you will need to manually map each column in the file to a data column in Engage.


Tips for a successful import

  • Delete any columns in the file that are not being used in the import. Reducing the amount of extra data that is imported and processed will greatly improve the speed of your imports and reduce the likelihood of import errors.

  • If in doubt, save your file in tab-delimited text format. Commas and other special characters in your customer data can cause parsing errors and import failures. The tab-delimited text format is the least likely to cause these import errors.

  • Remove duplicate rows. Most Engage accounts use email address as a unique identifier for each subscriber. Remove duplicate email addresses from your import file to cut down on time and complexity of the imports. If an email address exists multiple times within a file with different attribute data associated, attribute values from the last row in the file for that email will be retained.