Plauti Duplicate check

By default, Salesforce uses its own Duplicate Rules when CampaignSuite communicates with Converse or Findock. A simple example is, for example, that you can set the e-mail address of a Contact to be unique. Converse and Findock will then look for duplicates based on an email address.

If you have indicated in CampaignSuite that Plauti Duplicate Check should be used, CampaignSuite will in some cases first go through this App so that its Duplicate Rules are used.

You have the option of setting per form what the score for scenarios should be. More information about scores and scenarios can be found in Plauti’s documentation . To be able to use this function it is important that the scenario is applied to DATA API!

The threshold in the DC Setup of your Salesforce instance only indicates from which matching percentage a record is considered duplicate. With the Duplicate Score in CampaignSsuite you can indicate from which matching percentage you want to update an existing record.

Example:
You have the Duplicate Check Threshold set at 75% and Duplicate Score in CampaignSuite at 90. When you submit a record via CampaignSuite, the scenario is used to see if there is a duplicate. Suppose there is a duplicate record with a matching percentage of 80%, a new record is created (which is considered a duplicate) and placed in a DC Job.
If there was a matching percentage of 90% or higher, the existing record will be updated (because the Duplicate Score is at 90).