Loading
Email in Marketing Cloud Engagement
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Import File Requirements for Marketing Cloud Engagement

          Import File Requirements for Marketing Cloud Engagement

          Add subscribers by placing the data using specific columns before importing. Ensure that the file meets the proper requirements to successfully import the subscriber data into Email Studio.

          Review your import file to ensure that you meet these requirements:

          Example
          Example The columns and data shown are a sample of how these columns and data are populated for correct importing of subscriber data:
          Columns for a subscriber import csv file

          File Requirements

          Follow these guidelines for the import file:

          • Format: When you create 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\.
          • We recommend a header row 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 need a column labeled "Subscriber Status" with "Unsubscribed" in each row.
          • Attribute data type: If you're importing subscriber attributes, ensure that the data in the import file is the same data type as the attribute field used. The data type can be text, date, or numeric.
            Note
            Note If you're importing an attribute that exists in the application, you receive a warning.
          • Use correct values for subscriber preference data: If you're importing subscriber preference data, use one of the following value pairs:
            • Yes or No
            • Y or N
            • True or False
            • 1 or 0
          • 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 the email address 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. 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), 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 your 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.
            Note
            Note When you import dates into lists or a data extension, the date must be in the same format as is indicated on your account. If your user date format is different from the account, you must still 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, have a column called First Name. When you import, any value in the First Name column exists in the First Name attribute.
           
          Loading
          Salesforce Help | Article