When importing a CSV file, there are a few useful settings:
Existing contacts
The mode for existing contacts can be "update" or "ignore". If "update" is selected, the data from the CSV file will overwrite the existing data in CamBuildr.
Only data that is assigned for import is considered. For example, if you import only email addresses, other data (first name, last name, etc.) will not be altered.
In "ignore" mode, only new email addresses from the CSV file are considered. Already existing ones in Cambuildr will be ignored.
What the import can and cannot change
In update mode the import writes exactly the columns you map: first name, last name, gender, birthdate, phone, titles, ZIP, street, city, country, and your custom fields (custom fields are not available for import on the Campaigner plan). A cell that is empty in the file leaves the existing value untouched.
An import cannot unsubscribe, block or delete anyone, and it cannot remove tags. There is no status column to map, and existing blocked people stay blocked. To unsubscribe or delete a list of people, see Deleting people and cleaning up your database.
Column separator
Since the CSV standard allows both comma (,) and semicolon (;) as separators for column values, you can easily set which one your file uses here.
Tags
Often you want to be able to select all contacts of an import easily later. On the one hand, this is possible via the action, which is automatically saved during the import. On the other hand, CamBuildr also allows you to add tags to an import.
Each contact that is affected by the import will get all the tags specified here. Caution: In ignore mode, the ignored contacts are not tagged!
Starting a workflow from an import
Every import records a was imported action on each affected person, whether the person is new or was updated. A workflow can start on that action, so an import can kick off an automation: a welcome series for new people, tagging, or the list cleanup described in Deleting people and cleaning up your database. Use a tag on the import together with a has tag condition so the workflow only reacts to that import. In ignore mode, ignored contacts get no action and do not enter any workflow.

