Page tree
Skip to end of metadata
Go to start of metadata

FTP Scheduler Instructions

Please use this utility with caution.  ALWAYS have backups of your data before attempting to use this utility.   It's very easy to select an incorrect option and delete a list or overwrite subscribers.

Requirements:

  • The file being imported must be zipped.  This will ensure the integrity of the CSV or TSV data file being imported.
  • The filename with the subscriber information (located on your FTP server), must contain the API ID for the list - anywhere in the name of the zip file.  This is just a “double check” on your side to make sure the data is imported into the correct list.
    • You can find the API id for the list under the Subscribers & Lists -> Edit List - API id: 1234567890
  • We will automatically uncompress the zip file, take the first file in the zip file, and process ONLY that first file.  This file does not need to have a specific naming convention.
  • Your data file must contain column name headers in the first row.
  • You must notify your Technical Services Manager when adding a new FTP schedule in order for the import to "go live".

Automatic Column to Custom Field Mapping:

  • The FTP Scheduler will automatically map column names in your data file to custom fields in the system, based on the first row column names in your data file. 
    • We always recommend testing the CSV/TSV file first using the manual import "Subscribers & Lists" -> "Import".  If the columns auto-map to your custom fields, and the import is successful, it's likely setup correctly.
  • In order for column names in the import file to map to fields in the system automatically, the import file MUST contain headers that match the column names in your custom field section.  See "Subscribers & Lists" -> "Custom Fields".  The file must also have at least a single column named "email" which contains an email address for each row in your import file.  If there are columns that do not match custom field names they will be ignored.  A column name can only be used once, e.g. you cannot have two email columns.

Concatenate Functionality:

You have the optional ability to concatenate a single field as you import subscribers.  This means, if an email address is repeated in the import file, we will automatically append new information to the concatenate field you select.  e.g. If I choose a custom field called "Item Purchased" as my concatenate field, and my file looks like the following:

emailfirstnameItem Purchased
lauryn@test.comLauryn515
lauryn@test.comLauryn519
sue@test.comSue109
jim@test.comJim173
jim@test.comJim173
lauryn@test.comLauryn1201
lauryn@test.comLauryn515

 

The subscriber records will look like the following after the data is imported:

emailfirstnameItem Purchased
lauryn@test.comLauryn515,519,1201,515
sue@test.comSue109
jim@test.comJim173,173

Please note, the "Concatenate" field will always be "refreshed" on import, assuming the import file contains this field.  This means it's not possible to retain data for that column from import to import.  Any new import will overwrite and refresh that column. In addition, custom fields can store a limited amounts of information, and aren't intended as a data repository, so it's not possible to store data over 255 characters in length in most custom fields.

 

 

  • No labels