When you import a mailing list, ATG Outreach examines the records to determine if any already exist in the profile repository. By default it uses the email property to do so -- if any profile contains an email property whose value is the same as one that already exists, the import record is considered to be a duplicate, and a new profile is not added. The application administrator can configure any property or several properties to be used in this way.
If an existing record is found, its data is not overwritten by default. However, data that does not exist in the record is added by the import. Consider this example:
The following profile already exists in the repository:
first name | last name | home state | |
|---|---|---|---|
jrodriguez@example.com | Jenn | Rodriguez |
The import file contains the following:
email,name1,name2,state
jrodriguez@example.com,Jennifer,Rodriguez,MA
After the import, during which the columns are mapped to appropriate profile properties, the profile appears as follows:
first name | last name | home state | |
|---|---|---|---|
jrodriguez@example.com | Jenn | Rodriguez | MA |
E-mail addresses are considered to be unique if they use different capitalization from existing entries or include extra blank spaces. For example, the three addresses shown below are treated as different items:
mmiller@example.comMmiller@example.commmiller@example.com_
A new profile is created in each case.
