Give your import process a name and choose ‘Realtime – updates happen as the user makes them’
Select which audience to pull changes from. Mailchimp audiences will populate the dropdown.
Select the date and time from which changes should be processed.
Choose how records should be matched:
- ‘Match against all constituents found’; so if this email is shared by two or more constituents in your CRM the changes will be imported to all records containing this email address
- Match on email according to duplicate email settings; if you have defined a ‘main contact’ for an email address in the configuration this record will be updated
- ‘Match on constituent id mapped to the following merge field’; select the Mailchimp field from the drop-down containing your ConsID/LookupID , this is obviously the most accurate way of matching records
If a record is not found by the ConsID/LookupID (e.g. new sign ups) they will be looked up by email address, if a match is found that record will be updated. If no match is found a new record will be created and the new ConsID/LookupID written back to Mailchimp.
Here you can map your Mailchimp merge fields to the appropriate place in your CRM. In order to reduce the number of fields you see in the dropdown we have grouped the CRM fields into categories, you will need to select the area the field you require is in to see the options in the field dropdown.
If you do not wish to import certain Mailchimp fields simply ignore them in your mapping.
The ConsID/LookupID field must be matched to the appropriate Mailchimp field (at the bottom of the screen) in order for the import to proceed.
You may have certain business rules set up on your CRM around the creation of new records, here you can set up default values to fulfil those rules.
Click ‘done’ and your import will be set up, it will run next time a change is made, or a new subscriber is added in Mailchimp.