OneMerge Duplicate Management Match Confidence

Previously the options for controlling whether duplicates followed the data stewardship or auto-merge paths were twofold; the global flag which requires all duplicates to be data stewarded and dynamic data driven conditions which reference attributes of the duplicate records. With the latter option the conditions could reflect the type of customer, their CLV or membership of a loyalty programme as examples where a data steward may wish to review the duplicates before accepting or rejecting the merge.

To create a Required Match Confidence, follow these steps:   

1. From the OneMerge Application Home Page, click Guided Setup in the footer.
2. On the select action screen, you should choose the Manage Application Settings option, and then click the Next button.
3. On the next screen, there is the option to select a Required Match Confidence (as shown below).

With the 75% value (shown in the screenshot above), Duplicate Record Sets with a Match Confidence of 74% and below will require data stewardship whereas 75% and above will auto-merge; unless a data stewardship condition is applicable (e.g. VIP Customer).

The Match Confidence Field is also shown on the Duplicate Record Set Object (as shown below). NOTE: If it is not showing, it may need adding to the Page Layout.

The following demo shows how to setup the Duplicate Match Confidence percentage.

For further information about setting up Duplicate Management Match Confidence, please do not hesitate to contact us at hello@onemerge.co.uk.

Article last reviewed: 2026-02-17