When faced with duplicate records in your database, the probability increases that old and missing information exists. One employee may use Duplicate Record 1 to log a phone call, while another employee updates the lead status on Duplicate Record 2.
By adjusting Cloudingo‘s automation settings, you have the option to tell Cloudingo what records to merge, when to merge, and what fields you want to pull into the master record. For example, you can tell Cloudingo to make the oldest created record the master record. So, out of a group of duplicate records, the one that was created first will be the master record. From there you can tell Cloudingo how to handle certain fields.
“Override master when blank”
Cloudingo will keep all the field values for the master record with one exception: where there are any empty fields, Cloudingo will pull in the value from a secondary record so that you always end up with the most complete record. This is the most recommended option and also the default.
“Never override master”
This option preserves the field values for the master record and never changes any of the values, including empty fields. From our example, it will simply use the oldest created record as the master.
“Always override master”
If this option is selected, Cloudingo updates the field values based on the record defined in the first drop down menu.