Direct Processing finds and merges duplicate records that came in via API insert without any user interaction.
Duplicate records that were found when records came in via API insert, i.e. via integrations such as web‑to‑lead forms, Power Automate flows, partner uploads, or bulk imports, can be merged automatically without any human intervention.
In the near future, converting duplicates found via a Cross-Entity search upon API insert will be possible as well.
Set a threshold for Direct Processing, and any duplicate records that came in via API insert and have a matching score on or above that threshold will be automatically merged as soon as they are detected.
The records will be merged according to the Merge Rules, so make sure you have set those up correctly.
Direct Processing, also known as Automatically Merging After API Insert, can be configured in the ‘Duplicate Detection for API Inserts’ setting.
Prerequisites
- You have set up the Master and Field Merge Rules, so that winner and loser records and field values can be determined without human intervention.
- You have set up one or more Scenarios that will determine which records are duplicates of each other, and what their matching score (matching percentage) is.
Configuring Direct Processing
To set up Direct Processing:
- In the Plauti Deduplicate app, go to Manage Entities > open (Manage) an Entity > tab Feature Activation & Setup.
- Fold open the Enable duplicate detection for API Inserts by logging to Duplicate Check job section.
- At Applied scenario(s) for duplicate detection, make sure one or more scenarios are selected.
- At Automatically merge records found after API Insert, toggle to ‘Yes’.
- At Minimum required matching percentage to trigger automated Merge, set a threshold percentage. Duplicates that have a matching score that is equal to or higher than this percentage will be merged automatically.
- Toggle the Enable duplicate detection for API Inserts by logging to Duplicate Check job section to ‘Activated’ if this wasn't the case yet.
- Click Save and Publish Now. If you are requested to update the Search Index, proceed to do so.
Read more about the different ‘Feature Activation & Setup’ settings in Duplicate Prevention.
Set a high threshold
Since Direct Processing is a fully automated process, it is recommended to set a high threshold, such as 98% or 99%, and leave lower-scoring duplicates for manual review. Merges cannot be undone. If by experience you find that the threshold can be lowered a bit you can always change it later on.
Using Direct Processing
After configuring Direct Processing, it works fully automatically.
Records that come in via API insert are first scanned for duplicates. If certain records are found to be duplicates, and have a duplicate matching score equal to or higher than the threshold you set for automated merge, they will be picked up and automatically merged according to the Merge Rules. The matching score is determined by the scenario you are using.
Each merge action will be logged in the Audit Log.
Other lower-scoring duplicates, as well as high-scoring duplicates that could not be automatically merged for some reason, will be left in the ‘Duplicates Detected Via API’ job for reviewing and further processing by you.
During the automatic merge process, high-scoring duplicates are temporarily placed in the ‘Duplicates Detected Via API’ job. It will rarely happen, but sometimes it might occur that you temporarily see a group of high-scoring duplicates while reviewing other duplicates in the duplicates detected job, that then disappear again because they were picked up by Direct Processing.
