Direct Processing

Last published at: February 23rd, 2026
Delete

The Direct Processing feature is available in the Premium and PDM Editions.

Delete

Direct Processing finds, merges and converts duplicate records at entry point without any user interaction. If you do not want to manually handle the process of deduplicating records that came in via Web to Lead, Unique Import / API Bulk Insert, or API Single Insert, read on!

Prerequisites

  • For automatically merging records, make sure you have set up the Merge Rules‍ to define how the records should be merged.
  • For automatically converting records, Cross Object‍ should be enabled and configured.
  • To use AI Assist to determine the best values to keep when automatically merging records, AI Merge Recommendation‍ should be enabled (optional).

1. Configure Direct Processing

You can apply the direct convert and direct merge features to any of the automation channels. 

  1. In Plauti Deduplicate, go to Deduplicate Setup.
  2. At left, select Object Configuration, and click Configure  at the Object you want to enable Direct Processing for. This is the object where records come in via one of the automation channels.
  3. At the Object, click the Direct tab.
  4. Click Configure  in the 'Convert Settings' or 'Merge Settings' section.
  5. At Apply direct convert/merge on, select one or more channels where you want to use Direct Merge or Direct Convert.
    • API / Apex Insert
      For all duplicate records that are created via API.
    • API / Apex Update
      For all duplicate records that are updated via API.
    • Deduplicate Apex API
      For all duplicate records that are found via the Deduplicate API.
    • Flow
      For all duplicate records that are created or updated via Salesforce Flows.
    • Unique Import / API Bulk Insert
      For all duplicate records that are imported via any import tool.
    • Web-to-Lead
      For all duplicate records that are created via the Web-to-Lead process.
  6. For Direct Convert, select a status for the converted records at Direct convert with the Convert Status. 
  7. At Direct convert/merge if the score is equal or higher, determine from which matching score the duplicates should be processed by the Direct Process feature. As merging and converting cannot be undone, it is recommended to set a high threshold score of 99% or 100%. This way only those records that are most certainly duplicates will be processed.
  8. For Direct Merge, toggle AI Merge Recommendation (optional) to improve upon the Merge Rules for automatically deciding which field values to keep. 
Delete

Matching Score?

When Plauti Deduplicate compares records to find duplicates, records will get a 'matching score' based on the applied Scenario‍. Records with a low matching score are not very likely to be duplicates of each other, while records with a high matching score are very likely duplicates.

The Threshold as set in Scenarios is the minimum score for records to be considered duplicates. These duplicates will be shown as duplicate job results for example, to be processed manually. The threshold for the matching score set here for Direct Processing is most likely higher, as you only want to automatically process the subset of the found records that are very likely to be duplicates.

2. Apply a scenario to Direct Processing

Apply one or more Search Scenarios‍ to the channels where you want to use direct processing: Web-to-Lead, Unique Import / API Bulk Insert, API Single Insert / Update, Deduplicate Apex API, and/or Flow. 

  1. Still in Deduplicate Setup, on the Object where the records come in, go to tab Scenarios.
  2. Find the scenario you want to use, or create a new one.
  3. At Apply To, select the channels for direct processing.

After applying at least one scenario to a channel, Direct Processing is activated for that channel.

Delete

All actions resulting from the options described above, all duplicate records merged and converted, can be viewed on the Deduplicate Audit Logging page. Deduplicate Audit Logging is only available in our Premium and PDM editions.

Delete

Do not set the score too low. Merging false duplicate records cannot be undone.