de en


Subscribers: Import

You have probably already compiled a list of addresses that you want to send newsletters to.

The universal CSV file format lets you export your addresses from almost any database or spreadsheet program (e.g. Microsoft Office or OpenOffice) and then import them into emma.

To make it easier to map the columns (e.g. first name, last name, email) during the import, the first line of your CSV file should contain meaningful column headings. An example:

When saving your data, choose the export format CSV UTF-8 (Comma delimited) or CSV (Comma delimited), depending on the version of your Office package.

The import step by step

To import your CSV file into emma, select 'Import' in the 'Subscribers' menu:

Step 1 - Import file

Select the CSV file you want to import. To speed up the upload of large files, you can compress the file as a ZIP archive first. The name of the ZIP file must be identical to the name of the CSV file it contains.

Note: The CSV file should not be larger than 200 MB. Please split larger files before importing them.

Then click 'Next'.

Step 2 - File structure

Step 2 shows a preview of the first lines of your CSV file. Here you can check what the import will look like with the current settings.

Set the 'Field separator' and 'Text separator' so that the columns you need (e.g. first name, last name, email) are displayed side by side. In most cases, the default settings (semicolon as field separator, quotation marks as text separator) already fit.

emma usually detects the 'Character set' automatically from the special characters in the CSV file (e.g. German umlauts). Please check how the characters are displayed in the preview.

If characters are displayed incorrectly in the preview, proceed as follows:

  • Select the matching character set manually. If that does not solve the problem ...
  • ... save your data as a CSV file again and choose the character encoding 'Unicode (UTF-8)'. This is the default setting of emma and lets you import the CSV file without problems. In Microsoft Excel, for example, choose 'Save As' --> file type 'CSV (Comma delimited)' --> open the 'Tools' menu ('Extras' in German versions of Excel) and choose 'Web Options' --> 'Encoding' --> save this document as 'Unicode (UTF-8)'.
  • If your software does not offer this setting, you can use the free software OpenOffice, for example, to open your CSV file, select the matching character set and save it again with the character encoding 'UTF-8'. OpenOffice is available free of charge for all major operating systems.

 

The 'First line contains column headings' option specifies whether the first line of your CSV file contains the column headings (e.g. first name, last name, email) or starts directly with subscriber data.

Then click 'Next'.

--> Tip: If you are unsure about the format of your CSV file, open it in a text editor. Here is an example of a CSV file with column headings, semicolon as field separator and quotation marks as text separator:

Step 3 - Subscriber lists

Now select the emma subscriber list your CSV file should be imported into.

If you have not created a subscriber list of your own in emma yet (see the Subscriber lists menu), you can start right away with the empty subscriber list 'Demo-Liste'. This list is usually created when your emma account is set up and contains one sample subscriber for demonstration.

You can also select several subscriber lists if you want to import into several lists at once. After selecting the list(s), click 'Apply' and then 'Next'.

You can change the name of a subscriber list at any time in the Subscriber lists menu.

Step 4 - Field mapping

In step 4 you tell emma which column of your CSV file (e.g. first name, last name) should be imported into which emma subscriber field. Typical subscriber fields such as 'Email', 'Salutation', 'First name' and 'Last name' already exist in emma.

The left side shows the content of your CSV file once more, using the first two subscribers as an example. On the right side, select the 'Field type' that matches each content.

emma maps the fields automatically if the CSV column heading and the name of the emma subscriber field are identical.

If no matching subscriber field is found, the new field content is set to 'ignore'. In this case, either select one of the existing fields or use the 'New subscriber field' option to create a new field and give it a name. New fields created here always get the type 'Multi-line text', see also the tip below.

Then click 'Next'.

--> Tip: Ideally, take the time before your first import to create all fields in the emma menu 'Subscriber fields' so that field names and field types match your imported data. You will then benefit from automatic field mapping, which saves time on recurring imports and prevents errors caused by unsuitable field types or manual mapping.

Step 5 - Import type

Here you define how your newly imported data is matched against the existing 'old' data of the selected emma subscriber list(s).

 

Four different import types are available. The examples below use Max and Lina ('old' data) and Alex and Leon (new data):

--> Import type: Add

All new records are added, regardless of the existing records. All old records are kept. Any duplicates created this way can be removed later using Duplicate matching.

In the example, Alex and Leon are added, Max and Lina are kept.

--> Import type: Replace

All data in the selected list(s) is deleted and replaced by the content of the imported CSV file. Please note that deleting subscribers from the list also deletes their previous user behavior (opens, clicks, bounces), e.g. 'received last mailing', and any target group definitions based on it. If you do not want this, use 'Import type: Update and add' instead.

In the example, Max and Lina are deleted, then Alex and Leon are created.

--> Import type: Update

Only the data of existing subscribers is updated. New subscribers are ignored, i.e. not added. You define in Step 6 - Options which data identifies a subscriber as 'already existing' (e.g. customer number or email address).

In the example, Max is updated (+music), Lina stays unchanged. Alex is ignored because he did not exist before.

If the option 'Delete recipients from subscriber list who are missing in the import file' is activated, subscribers missing from the CSV file are treated as 'please delete'. Only subscribers who are in both the old and the new list are kept. In the example, this option updates only Max. Lina is removed because she is missing from the CSV file.

--> Import type: Update and add

In addition to the update described in the previous section, new subscribers from the CSV file are added if their data could not be matched to any subscriber already in the list.

In the example, Max is updated (+music), Lina stays unchanged. Alex and Leon are added.

Combined with the option 'Delete recipients from subscriber list who are missing in the import file', this works like 'Import type: Replace', but keeps existing subscribers. This means: the new content of the CSV file is taken over completely, but unlike 'Import type: Replace', existing subscribers are recognized and their previous user behavior (opens, clicks, bounces) is kept.

With this option, in the example, Max is updated (+music), Alex and Leon are added. Lina is removed because she is missing from the CSV file.

You define in Step 6 - Options which data identifies a subscriber as 'already existing' (e.g. customer number or email address).

Click 'Next'.

Step 6 - Options

Here you define the final details of the import.


--> Matching with opt-outs

This option prevents subscribers who have already unsubscribed from being imported again (recommended). You can choose which opt-outs are taken into account:

  • All lists (global): The opt-out matching checks all subscriber lists in your account. This means: email addresses that have already unsubscribed are not imported again, no matter in which list they unsubscribed.
  • Selected lists of the current import: The opt-out matching checks only the subscriber lists currently selected for the import. This means: email addresses that have already unsubscribed are only skipped if they unsubscribed from one of the lists currently selected as import target.


--> Subscriber backup

If the option 'Export subscriber data automatically before new import' is activated, a backup of the subscriber list(s) currently selected for the import is created.

You will find the backup under 'Subscribers' --> 'Export' --> 'Exported subscribers'. If you later notice that something went wrong with the import, you can export this backup as a CSV file at any time and use it to replace the faulty subscriber list via import. In this case, use the import type 'Update and add' with the option 'Delete recipients from subscriber list who are missing in the import file' activated. This updates the remaining subscribers to the state of the backup and creates the missing subscribers again. However, data on previous user behavior (opens, clicks, bounces) cannot be restored.


--> Duplicate matching

Duplicate matching removes or merges addresses that exist more than once. If you have already created a duplicate matching setup ('Setups' --> Duplicate matching setup), you can select it here.

You can also run duplicate matching later at any time via 'Subscribers' --> 'Clear lists' --> Duplicate matching.

 

--> Check for invalid email addresses

If this option is activated, the import checks which email addresses are certainly undeliverable because of obvious typos (e.g. a missing domain ending or a missing @ sign). After the import, you can either delete the invalid addresses found or export them for editing in the menu 'Subscribers' --> 'Clear lists' --> Invalid addresses.

 

--> (Update only) Identification fields and update fields

If you selected one of the two "Update" import types in the previous step, the following additional options are shown. Otherwise this step is skipped automatically.

For an update to succeed, emma must recognize the subscribers already in the list by unique identification fields (e.g. email address or customer number) and assign the newly imported data to them as an update. A subscriber is matched if the values of all selected identification fields are identical in the import file and in the existing subscriber list.

An example: if you select the four fields "Email", "Salutation", "First name" and "Last name" as identification fields, all four must match exactly. If, for example, the salutation field is empty in the newly imported data, the match fails. Instead of an update, a new subscriber with the same email address, first name and last name, but without salutation, is created.

The update fields define which fields of the subscriber record are updated with the new data from the CSV file.

Step 7 - Import

Before you start the import, please check your settings once more in the overview.

 

Start the import by clicking 'Import'. Your import is now queued and keeps running in the background, even if you leave the page.


Important: How long the import takes depends on the size of the CSV file and of the list(s) you import into. This applies especially if one of the "Update" import types is selected and actions such as backup, duplicate matching or opt-out matching are activated. You can follow the current status in the progress bar.

Once the 'Current progress' column shows the status 'Done', your subscriber data has been imported successfully.

The overview shows the total number of imported records, the import type used and the list(s) you imported into. If you activated follow-up actions in the import options (check for invalid email addresses, duplicate matching), the 'Following action' column contains links to their results. Click the details icon in the last column to see more details and settings of the import.

 

--> After the import: clear lists

If you did not activate the clean-up actions for your new subscriber lists during the import, you can run them later at any time in the 'Subscribers' --> Clear lists menu.

This is recommended: it makes your sending more effective with higher delivery and open rates, and you avoid unnecessary bounces and complaints.