This is a precaution that we take to ensure that the same file cannot be imported twice.
Auto-import configurations which were set up prior to the release of Emarsys version 8.2 (February 2015) can still have settings which are either not yet supported by the new import feature, or which have since been superseded by improved functionality. Examples of such features are ‘Newsletter opt-in’, ‘on-import campaign’ or ‘no duplication handling’. If you want to edit these auto-imports, please contact Emarsys Support.
No. To do this you should include a unique field in the import file (e.g. named after the auto-import name) and create a segment that filters for contacts with the appropriate value for this field.
You cannot import more than one file manually via the import wizard – for this you will have to set up an Auto-import. Auto-imports will pick up all the files that are correctly uploaded to the storage folder.
CONFIGURING YOUR AUTO-IMPORT
A WebDAV is an SSL-secured source hosted and maintained by Emarsys. This is convenient for many clients because Emarsys Support will set it up for you (free of charge) and all you need to do is use a suitable client application such as Bitkinex or Cyberduck to access the folder, or program automatic updates directly from your CRM. Emarsys checks the WebDAV of each account every minute and processes any new files it finds there. Processed files are saved back on the WebDAV with the following naming convention:
- filename.csv.done – for successful imports
- filename.csv.error – for unsuccessful imports. A notification with details of the error will be sent to the Notification Center.
- filename.csv.ignore – for files whose names do not match the naming convention defined for any of the enabled auto-imports.
Note: if you use a compression file, the import file will be extracted to the WebDAV and renamed as above, and the compression file deleted.
SFTP or FTPS servers are the most secure transfer protocols available and should be used if you have the technical resources available. Emarsys checks these external sources once every hour and successfully imported files are deleted from the source.
We recommend including both static and dynamic parts in the file names. The static part should be clear and easily understandable, ideally relating to some aspect of your customer lifecycle strategy, while the dynamic part (e.g. a timestamp) will differentiate individual files. The dynamic part is represented by a wildcard asterisk * in the naming convention field.
- If you will only ever need one auto-import configuration, you can use a simple naming convention such as .csv. This will mean that every .csv file placed on the source folder will be processed.
- If you use more than one auto-import, then we recommend to match the static part to the auto-import name, and keep the dynamic part for a timestamp. In this way you could define the naming convention for the converted leads auto-import as: converted-leads-*.csv, and then name each individual file as: converted-leads-2015-02-12.csv
Note: File names are case sensitive.
A sample file is necessary so that Emarsys knows which fields to expect in the import files, and how to map them and their values to existing fields in the Emarsys database. If you make any changes to the import files, however minor, you should upload a new sample file based on the new import file.
A sample file must contain all the expected fields, in the correct order and with all the possible values for any multiple- and single-choice fields.
No. Emarsys is only interested in the file settings and the fields and values.
For most Emarsys accounts, only UTF-8 encoding is supported. The only exceptions are the accounts on the environment www.emarsys.net, which supports only Latin1. Please note that Emarsys does not verify the encoding used; if you use any other encoding, the contact data you import may be corrupted and unusable.
The import file itself must be a .CSV file. However, you can compress this file. The following compression formats are supported: .ZIP, .ARG, .GZIP, .TAR, .TGZ, .BZIP2, .7Z. If you do want to use a compressed file format, make sure you include the naming convention for the compression file and any password required to open it.
None. This is purely in case you want to segment your contacts via language, for example when sending newsletters in multiple languages.
Changing the language setting of the import file can affect two things:
- The field names and values. If a file language is defined, Emarsys will use that language to match the fields and their values in the import file. Please note that this requires you to provide the relevant translations for any custom fields included, in the respective language(s).
- The date format. Certain date formats are associated with different languages. Emarsys will check the sample file for the date format and if this does not match the language, an error will be shown in the auto-import wizard. The supported date formats are:
In order for Emarsys to be able to access your external source, please ensure that:
- Emarsys Support have the external source IP and domain so that they can whitelist them on the Emarsys firewall.
- Emarsys is whitelisted on your own firewall (contact Emarsys Support for all the necessary information).
- The external source username and password are correct, and have the correct user rights (read and write access for downloading and removing files).
Emarsys will check these credentials when you exit the wizard and save your configuration. If there is a problem you will receive a notification within minutes.
You will soon notice if the wrong delimiters are used, as the entire sample file will show up as one single field with all the values in each line:
If you get a notification that Emarsys could not reach the server, please check:
- That the credentials you entered are correct
- That Emarsys is whitelisted and not blocked by your firewall
- That your server is working properly
If you get a notification that the import failed because of an issue with the import file, please check that the encoding, delimiters, fields and rows of the import file are correct. If this error persists, upload a new sample file and check the configuration again.
es, key-based SFTP authentication is possible for imports. For more information see Security Settings.