Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Install the Delpha Connector browser extension to link your LinkedIn account with Delpha and unlock powerful enrichment features. Compatible with Chrome and Edge for seamless integration.
To enable advanced LinkedIn enrichment features in Delpha:
Install the Delpha Connector browser extension from the Chrome Web Store
The extension is compatible with both Google Chrome and Microsoft Edge
Once installed, it seamlessly connects your LinkedIn account to Delpha, allowing for smoother and more accurate data enrichment
This integration helps automate and enhance LinkedIn data collection within your Delpha workflows.
Apply the package
If you are upgrading from a version below 3.58, you must run the migration script
Migration steps are not cumulative. Depending on your initial version, you will have to apply all upgrade tasks listed on the main Build Item (eg: Build 3.58.x), all the way from your current version up to the version you are upgrading to.
No migration step when upgrading from 3.58x.
Apply the package
Explore Delpha’s documentation for setup, integration, deduplication, and LinkedIn enrichment. Includes FAQs, job tracking, and support options.
This Help Center is organized into structured categories to help you quickly find the guidance you need, whether you're setting up Delpha for the first time or fine-tuning deduplication rules.
Start here to understand how Delpha works and how to get set up.
Welcome to Delpha: Introduction and overview
Delpha Setup:
Delpha Upgrade:
Delpha Apps:
Use Cases Setup:
Delpha Campaigns:
Common tasks, step-by-step guides, and practical how-to articles.
Delpha Integration:
Delpha Job Tracking:
Delpha LinkedIn Connector:
Delpha Duplicate:
For when you need assistance or something isn’t working as expected.
Grant Access for Delpha Support:
.
Assign the right Delpha permissions by selecting a persona-based permission set group—Admin, Data Steward, or User—for each Salesforce user. Simplify access control and role-based setup.
To assign the correct permissions in Delpha, follow these steps:
Determine the User’s Persona: Choose the appropriate role — Admin, Data Steward, or User — based on their responsibilities.
Assign the Permission Set Group:
Go to Users in the Salesforce Setup.
Find the user and assign one of the following groups:
Delpha Admin – Full access including Setup and Data Quality tools
Save your changes to apply the permissions.
This ensures each user has the appropriate access to Delpha features based on their role.
Do not forget to assign the Delpha Admin permission set group to you
From this version, the Duplicate Settings have been moved from SObejcts into a unique JSON.
This reduces the complexity of Duplicate settings spanned over many objects (mainly DDQ Duplicate Objects, DDQ Duplicate fields...). This change requires a migration step that is made simpler by using a dedicated migration package provided by Delpha.
After the main Delpha package is installed, add the DelphaUpgrade258 package (unmanaged) to your org. It will facilitate the migration process.
Package Id: 04tRl000001EAVBIA4
Package URL : /packaging/installPackage.apexp?p0=04tRl000001EAVBIA4
Once the upgrade package is installed, open a developer console and run the script below.
Connect your Salesforce org to Delpha by using the Delpha Setup app and configuration tab. Fast integration in just a few clicks to enable full platform functionality.
Apply the package
If you are upgrading from a version below 3.58, you must run the
Apply the package.
If you are upgrading from a version below 3.58, you must run the
Check your Salesforce org settings to optimize the use of Delpha to and install the LinkedIn Enrichment connector for enhanced data insights.
Assign Delpha licenses in Salesforce easily via Installed Packages or directly from user profiles. Ensure your users have access to Delpha features with quick license management.
Import conversations into Delpha to enable advanced data quality and deduplication use cases. Select recommended components for full feature coverage and smarter data management.
Apply the package
If you are upgrading from a version below 3.58, you must run the
Delpha Data Steward – Access to Data Quality App, Score Meter, and Bot
Delpha User – Access to Score Meter and Bot only
Go to the Delpha Configuration tab
In the First Steps section, click Connect
A new window will open—follow the prompts to authorize and complete the connection
Once connected, Delpha can begin syncing data and enabling core features.
The profile and permissions of the user that performed the connection are going to be used by Delpha. Make sure the user has an administrator profile and will keep the Delpha Licence and Delpha Admin permissions.
We recommend using a dedicated 'technical' user with Admin rights for that step.
This user should not be reused when connecting Sandboxes to Delpha. Using the same user to connect sandboxes will overwrite the current settings. In other words, you will disconnect from Delpha the org (prod or sandbox) where this user has done the initial connection.
Delpha Technical Setup is done!
On the Delpha listing page, click “Get It Now” to begin.
Choose your environment (Production or Sandbox) based on where you want to install the package.
Log in again if prompted to confirm your identity.
Accept the terms and conditions by checking the agreement box.
Set the security level, selecting who should have access to Delpha (Admins only, All users, or specific profiles), then click Next.
Click “Install” to start the installation process.
Once complete, Salesforce will send you a confirmation email indicating that Delpha was successfully installed.
During the setup, you are asked to Approve Third-Party Access
api.hubapi.com: HubSpot endpoint used by Delpha to synchronize HubSpot and Salesforce records after Delpha merges Salesforce records during the Duplicate process.
This integration is disabled by default and can be enabled only by a Delpha Administrator in the Duplicate Settings.
mail.delpha.services: Delpha endpoint used by the Email Insight feature to extract business information from incoming emails.
This feature is off by default and is activated at the Delpha license level (FMA).
Go to Setup in Salesforce
In the Quick Find box, search for and select Installed Packages
Find Delpha in the list and click Manage Licenses
Click Add Users, select the desired users, and click Add
Go to Setup > Users via the Quick Find box
Click the name of the user you want to license
In the Managed Packages section, find Delpha and click Assign
Click Save to confirm
Both methods will properly activate Delpha access for selected users.
Do not forget to assign a Delpha license to you
This step is useless when installing Delpha on a Sandbox org
To import conversations for use in Delpha’s data quality workflows:
Open the Delpha Setup app in Salesforce
Navigate to the Import Conversations tab
Select the components you wish to import
Click Import Data to begin the process
For full functionality, it’s recommended to include the following components:
Version 3.56 and onward: the conversation package Data Quality is no longer needed. All the Data Quality topics being handled in the score meter.
Versions 3.60 and onward: most of the data quality and duplicate conversations are managed from the Score meter.
DuplicateLeadWD
DuplicatePersonAccount
LeadVsContact
LinkedInEnrichmentAdvanced
LinkedInEnrichment
Additional information on Delpha Conversations
By importing these components you add the Delpha standard conversations to the org. They are all listed in the app Delpha Setup below the Conversation Builder tab.
Delpha Data Quality: Improve and maintain data health with dimensions and recommendations
Delpha Campaigns: Configure, run, and optimize campaign pipelines
This process ensures Delpha is fully installed, configured, and ready to use for your team.
Install Delpha Connector for LinkedIn Enrichment: Set up the connector to enable LinkedIn-based data enrichment
These tasks help ensure optimal performance and unlock advanced enrichment features.
Use this section to complete your initial setup and manage Delpha features within your org.
delpha.DDQ_DuplicateSettingsMigration.quickMigration();To upgrade Delpha to a newer version:
Open the Release Notes (external document)
Select the version you want to install and copy the Delpha Package ID
Apply the upgrade using the virtual URL method:
Replace MyOrgName with your Salesforce org domain and DelphaPackageId with the ID from the document.
https://MyOrgName.lightning.force.com/packagingSetupUI/ipLanding.app?apvId=DelphaPackageIdReconnect your Org to Delpha: App Delpha Setup / Section: Delpha Integration / Click the Connect button
Update conversations: App Delpha Setup / Section: Import Conversation
Remove Data: Select All conversation package and click on 'Remove Data
Import Data: Based on the use cases you are implementing, select your packages : DuplicateAccountsWD, Duplicate ContactWD, DuplicateLeadWD, DuplicatePersonAccount, LeadVsContact, LinkedInEnrichment, LinkedInEnrichmentAdvanced.
Do not select the package Data Quality as the corresponding .
pairs following these steps
delete current scheduled tasks involving the Apex class: DDQ_DuplicateRecordAutoMerge
from the app Delpha Setup > Duplicate > Initialization, section Auto Merge Scheduler, select the hours to run the auto merge.
Apply a migration script.
This script updates the existing Duplicate Expressions and Filtering rules and ensure their proper display with the .
Open the developer console and apply the following script.
Access Delpha’s release notes to upgrade versions using a package ID and virtual install URL. Quickly apply updates in Salesforce by selecting your desired version from the official documentation.
If some scripts must be applied for compatibility topics between versions of Delpha, a side release package and a 'how to' will be provided in the release notes of the target build.
Open the Delpha Setup app and select the tab Delpha Configuration
In the section First Steps, consider the Review Configuration block You will find here all the items that needs a manual update with enough information for a quick application.
Once the updates are done, refresh your page. The section should only display green ticks.
What to do when you upgrade to a 3.58.x build
Apply the package
After the main Delpha package is installed, add the DelphaUpgrade258 package (unmanaged) to your org. It will facilitate the migration process.
Package Id: 04tRl000001LuppIAC
Package URL : /packaging/installPackage.apexp?p0=04tRl000001LuppIAC
Once the upgrade package is installed, open a developer console and run the script below.
The Score Meter has been redesigned to simplify your workflow and make issue resolution faster and more intuitive:
Before: You had to switch between the Score Meter and the Bot to review and apply corrections.
Now: Everything happens directly in the Score Meter — review, select, and apply corrections all in one place.
New interface: Cleaner, clearer, and optimized for batch actions. You can now apply changes to 1 / some / or all suggestions with just a few clicks.
No more back and forth. Just smarter data review in a single streamlined experience.
Try it out now and speed up your remediation process!
Add missing permission set for duplicate merge editor.
We’ve redesigned the Data Quality Steward View and the Duplicate Steward View interface to align with Salesforce’s native List View experience:
Familiar Navigation: Use the standard cog and filter icons to create, filter, and manage your views—just like any Salesforce list.
View Sharing: Create custom views and share them with your team for easier collaboration.
Field Flexibility: Choose any fields to display—making data analysis faster and more intuitive.
This update simplifies navigation, improves usability, and gives you more control over your quality review workflows.
Fix some display issued on Cross Merge Field Rules.
2 new Legal Ids types are supported by Delpha : Australia and New Zealand
If you remove the D LinkedIn URL from your record (Account or Contact), all related information is deleted from Delpha fields, now including the logo / picture profile.
Validation rules can act as a blocker for Data Quality.
When a record is updated by Delpha in the Data Quality process (assessment or recommendation phases) it must follow the validation rules or the update will be blocked.
When it happens in a mass assessment process (Automation, Campaign, Data Steward mass update...) the record is detected and blacklisted in the Delpha Setup > Tab: Locked Records until a Delpha Admin deletes the entry (and takes proper actions to avoid the validation breach again).
When it happens in a single enrichment phase, using the Score Meter, a warning message is displayed to the user so he knows that his record cannot be updated and why.
Score Meter
Fix tooltips not displaying for bullets
Yellow bullet for Status = Unknown is now a triangle
Display LinkedIn title instead of LinkedIn name
This build introduces some enhancement in the display of the Duplicate Data Steward pairs. Loading time is divided by 2.
Negative view for tiles
Add "Last Modified Date" column to the steward
Implement filtering for data steward views (Data Quality and Duplicate)
Delpha’s updated Data Steward View offers a fully customizable, Salesforce-native experience. Easily filter records, choose the fields you want to see, and create or share your own views.
Apply the package
Explore all the latest updates to the Delpha Setup app here.
Explore all the latest updates to the Delpha Duplicate use case here.
delpha.DDQ_DuplicateSettingsMigration.quickMigration();List<delpha__DDQ_DuplicateObject__c> dupObjs = [SELECT Id, Name, delpha__Expression__c FROM delpha__DDQ_DuplicateObject__c];
for(delpha__DDQ_DuplicateObject__c dupObj : dupObjs) {
String expRuleStr = dupObj.delpha__Expression__c;
System.debug('Current Rule: ' + expRuleStr);
if(String.isBlank(expRuleStr) || !(expRuleStr.startsWith('[[') && expRuleStr.endsWith(']]'))) { //check here if expRule is in old format (field is not filterable in query)
continue; //skip if already in new format
}
List<Object> expRuleList = (List<Object>) JSON.deserializeUntyped(expRuleStr);
List<Map<String, Object>> newExpRules = new List<Map<String, Object>>();
Integer i = 1;
for(Object rule : expRuleList) {
Map<String,Object> newRule = new Map<String, Object> {
'name' => 'Rule ' + i,
'rules' => rule
};
newExpRules.add(newRule);
i++;
}
System.debug('New Rule: ' + JSON.serialize(newExpRules));
dupObj.delpha__Expression__c = JSON.serialize(newExpRules);
}
Database.update(dupObjs);Follow these steps to activate Delpha licenses purchased through the Heroku Marketplace and set them up on your Heroku account.
If you purchased Delpha through the Heroku Marketplace, follow these steps to activate your licenses. If you’re a direct customer, you can skip this section.
You have access to an Enterprise Account, directly setup with the Heroku Team.
This Enterprise Account is set at Heroku contract signature. The Tenant Owner receives an email from Heroku to activate the account. If you think that you did not receive this email, liaise with your Heroku account manager.
If you are activating Delpha Licenses on a Personal Account, the process is the same. Make sure that billing information is set up (required for paid add-on).
Go to and sign in.
Switch to your Enterprise Account If the top-left account switcher, displays Personal, click on it and select a Team within your Enterprise Account
If it is the first time you log in your Heroku Enterprise Account, you may have no team created under your Enterprise Account. You should create one for easier access management to the Delpha resources on Heroku.
Go to the tab Apps and click Create new app.
App name: use something meaningful, e.g. your-companyname-delpha-heroku-licence (must be globally unique).
App Owner: select your Team.
Case 1: you are on a Custom Plan
Using Heroku CLI, copy paste the command from your Custom Plan email. It will add Delpha Data Quality add-on to the app you just created and associate it with the Custom Plan.
If Delpha has created a Custom plan for your company, you received an email titled Heroku - You have been invited to install delpha-data-quality:NameOfTheCustomPlan sent by [email protected] with this command line.
If you did not receive this email or if you do not know what to do with it... add Delpha Support with email address [email protected] to your Heroku Team so we can manage the Custom plan activation for you.
To add a Team Member on Heroku, just follow these steps: in your Heroku account: Select your Team / go to the Access tab / click 'Invite User'.
Case 2: you are on the Standard plans
Open your new app and go to the Resources tab.
In Add-on Services section, search Delpha Data Quality and select it.
Plan Name: choose Pro.
You should now see the Service Delpha Data Quality under Add-on Services section with a Plan selected.
Licences are now active for this Heroku app. You can start using Delpha.
Based on the users feedback, we improved the Data Steward view by having the most common filters back on the main data steward screen area.
You can directly select the Object and the field from the main screen. To access the extra filtering capabilities, click on the filter logo.
You can select the Object and the processing state (True or False). To access the extra filtering capabilities, click on the filter logo.
Use Delpha’s Use Cases Setup to configure data quality and duplicate detection rules in Salesforce. Tailor each use case to meet your business needs and maintain clean, reliable CRM data.
The Use Cases Setup menu allows administrators to configure key operational workflows in Delpha:
Data Quality – .
These options ensure your Salesforce org is equipped to handle both duplicate management and ongoing data health monitoring.
Use Delpha’s Data Quality and Duplicate Steward views in Salesforce to monitor record quality, apply intelligent recommendations, and resolve duplicates efficiently.
The Delpha Data Quality section provides dedicated views for data stewards to monitor and improve the quality of records in Salesforce:
Data Quality Steward View – Review, validate, and apply field-level recommendations across Accounts and Contacts
Duplicate Data Steward View –
These views help ensure data accuracy, unicity, and consistency across your CRM.
Use Delpha’s Duplicate Remediation settings to automate and control duplicate merges. Configure object-level rules and field-level logic to ensure clean, reliable data consolidation.
The Duplicate Merge section helps define how merges are executed after duplicate records are detected. It includes:
Merge Object Rules Section – Configure global merge logic and thresholds for specific objects (e.g., Account, Contact).
Merge Field Rules Section – , such as which value to keep (e.g., master, most recent, highest score).
These settings allow you to control both which records get merged and how field values are resolved post-merge.
Email-to-Case Duplicate Management keeps Salesforce clean by detecting and merging duplicate cases from emails.
Email-to-Case Duplicate Management helps avoid clutter when multiple emails create duplicate cases for the same issue. It detects and merges duplicates, consolidates information, and keeps case handling efficient and consistent.
Run the initial assessment – .
Initialize default duplicate settings in Delpha to enable record deduplication in Salesforce. Quick setup with customizable rules for accurate and scalable duplicate detection.
To prepare Delpha for duplicate detection, follow these steps:
Open the Delpha Setup App in Salesforce
Go to the Delpha Configuration tab
Scroll down to the Duplicates section
Click the Initialize button to load default settings
Once initialized, you can review and customize these settings from the within the Delpha Setup menu.
Ensure your Salesforce org settings are properly set to get the best of Delpha
This section helps users quickly access the latest improvements across the platform.
The "What's New" section is organized by key feature areas, making it easy to browse recent updates and improvements. Each item links to a dedicated page summarizing the latest changes and enhancements for that component:
Delpha Setup – .
Duplicate – .
Data Quality
Customize Delpha for Salesforce with configuration tools for data quality, deduplication, normalization, and default values—accessible via the Delpha Setup app.
Monitor Delpha token and duplicate credit usage in real time. Track consumption, reset dates, and usage limits to optimize your subscription and avoid overages.
Delpha’s Duplicate Detection Properties section lets you configure AI thresholds, filtering rules, screening fields, and auto-merge logic for accurate deduplication.
Check
Configure Delpha’s Job Tracker to monitor job changes and manage contact movements. Match accounts by ID or name, auto-create missing accounts and automate contact updates when job shifts are detected
Set default field values in Delpha for Account, Contact, and Lead creation. Ensure required fields are always filled to prevent Salesforce validation errors and streamline automated record creation.
Delpha’s Master Record Rule helps you define which duplicate to keep during merges. Choose from built-in rules -oldest, latest, or most-filled...- to ensure accurate and complete Salesforce data.
Start your first Salesforce duplicate detection in Delpha by clicking "Evaluate." Review results in the Duplicate Steward View to manage and clean duplicate records efficiently.
Form now on, Delpha performs an analysis on your targeted duplicate population and proposes you to discard in one click all values that may trigger too much pairs. Thsi information is displayed in the app Delpha Setup > Duplicate > Object Settings, in the Properties section of each object.
You can
Set up Delpha’s duplicate management by initializing default settings and activating auto merge. Automate the detection and resolution of duplicate Salesforce records with confidence-based logic.
Configure duplicate detection in Delpha by adjusting properties and field-level match logic. Ensure smart, accurate duplicate identification using customizable rules.
Access key Delpha apps in Salesforce, including Setup, Data Quality, and Score Meter, to streamline configuration, monitor data health, and optimize data-driven decisions.
To run your first check for existing duplicate cases, simply click the Launch Assessment button at the top of the Email-to-Case settings.
If the button is not visible, it means the initial assessment has already been executed.
Previously, Delpha asynchronous operations were executed either:
on behalf of the user who connected the org to Delpha, or
via the Salesforce Automated Process user, which introduced several limitations:
No clear audit trail for changes made by Delpha
Inability to assign Permission Set Groups to the Automated Process user
Reduced visibility and control for admins
✅ Now, a dedicated named user is explicitly selected during the setup. All actions performed by Delpha will consistently appear under that user’s name, providing:
Clear traceability of changes
Full permission customization and access control
Alignment with Salesforce best practices for automated systems
When upgrading to version 3.53.x or later from 3.50.x or earlier, you will need to reconnect Delpha as part of the setup process.
No email activation required: You no longer need to Activate Delpha sending an email to activate core features, simplifying the onboarding process.
Conversations are now automatically imported once Delpha is connected, eliminating the need for manual setup steps.
Salesforce Validation Rules set on a record can fire an error and prevent Delpha from updating it. When this happens in a batched process, the whole batch is rejected. The system now more reliably handles these situations to minimize disruption in workflows by catching the error and logging the record ans the error message in the Locked Records table so you can take care of it later. This allows the other members of the batch to be properly updated.
Usage Reset Date
Shows the next reset date for your token and credit usage (e.g., 2025-02-15), marking the start of a new billing or allocation cycle.
Tokens
Progress Bar: Visual indicator of how many tokens have been used
Current Usage: Displays used vs. total tokens (e.g., 22,030 / 1,000, or 2,203% usage)
Duplicate Credits
Progress Bar: Visual progress on duplicate credit consumption
Current Usage: Shows used vs. available credits (e.g., 4,528 / 10,000, or 45% usage)
This page helps you stay in control of your consumption and avoid overages.
Key Takeaways for Users:
Regularly monitor this screen to avoid exceeding your plan’s limits.
If your token or credit usage is consistently high, consider upgrading your plan using the "Change Plan" button.
Keep track of the usage reset date to plan resource-intensive tasks effectively.
Account Default Values
Action: Use Add New Field to define defaults (e.g., Industry, Account Type, Region)
Purpose: Prevent errors during Account creation due to missing required fields
Contact Default Values
Action: Add defaults for fields like Email, Phone, or Job Title
Purpose: Ensure Contact records are created with all mandatory info
Lead Default Values
Action: Set fields such as Lead Source, Status, or Company Name
Purpose: Avoid issues during Lead creation where validation rules apply
These settings are critical for the Job History use case as you can be proposed to create a new account or a new contact.
Open the Delpha Setup App and go to the Duplicate Settings tab.
By default, Delpha selects the oldest record as the master and fills any empty fields with values from the duplicate. This ensures completeness and consistency in the final, merged record.
Rule
Description
Oldest created date
Selects the record with the earliest creation date
Latest created date
Selects the most recently created record
Oldest modified date
Selects the record with the earliest last update
Latest modified date
Selects the record with the most recent update
Most Filled
Selects the record that has the most populated fields
These rules help you tailor your merge logic to preserve the most reliable or relevant data.
Once the analysis is complete, you can view the identified potential duplicates in the Delpha Data Quality App, under the Duplicate Steward View tab.
This view lets you review, validate, and take action on the suggested duplicate records.
Delpha’s Connected App (DelphaAssistantV2) is not installed with the Delpha Assistant package. That makes it an uninstalled application. New users attempting to connect LinkedIn through Delpha will fail until the app is installed (or the user has a bypass permission). (Salesforce)
In Setup, open Connected Apps OAuth Usage (Quick Find → “Connected Apps OAuth Usage”). (Salesforce)
Locate DelphaAssistantV2.
In Actions, click Install (you’ll typically also see Block beside it).
Confirm installation. After this, end users can authorize via Delpha normally.
Tip: In this list, an app showing “Install” is not yet installed; one showing “Uninstall” is already installed.
If you are using a Delpha version below 3.62, you will have to apply the same remediation to the connected app DelphaApp
Create a temporary Permission Set that grants the system permission: Approve Uninstalled Connected Apps. (Salesforce Admins)
Assign this Permission Set to the user who will perform the install.
Have that user repeat Case 1 to click Install on DelphaAssistantV2.
Remove the temporary Permission Set after installation.
If you are using a Delpha version below 3.62, you will have to apply the same remediation to the connected app DelphaApp
Existing users who previously authorized an uninstalled app may continue working in some cases, but new authorizations are blocked unless the app is installed or the user has the new permission.
If “Install” isn’t visible, you may already have the app installed (you’ll see “Uninstall” instead), or you’re not viewing from an account with rights to install.
To double-check, open Connected Apps OAuth Usage, select the app, and review Manage App Policies. (Salesforce)
To activate the Lightning Web Security feature in Salesforce:
Access Setup: Click on the gear icon and select "Setup."
Locate Session Settings: Enter "Session Settings" in the Quick Find box.
Enable Lightning Web Security: Scroll to find the "Enable Lightning Web Security" option and check the box.
Save Your Configuration: Click "Save" to ensure the settings are applied.
In newly created Salesforce orgs, the LWS feature is activated by default.
If you do not activate it, the display of the all the LWC components in the org will be too slow to allow a good user experience.
Delpha's data steward views are LWC components.
To deactivate the Adopt updated CSP Directives setting in Salesforce:
Access Setup: Click on the gear icon and select "Setup."
Locate Session Settings: Enter "Session Settings" in the Quick Find box.
Adopt updated CSP directives: Scroll to find the "Adopt updated CSP directives" option and uncheck the box.
Save Your Configuration: Click "Save" to ensure the settings are applied.
If this option remain selected, some links provided by Delpha (such as Company logo) will not display properly and will appear as broken links.
Delpha relies on OAuth for secure authentication that's why, to use Delpha features, the users must be able to access the User External Credentials Object.
To activate this access:
Option 1: For a permission set, under Apps, click Object Settings, and then click User External Credentials.
Option 2: For a profile, scroll to Standard Object Permissions and then select User External Credentials.
Access Setup: Click on the gear icon and select "Setup."
Locate Accounts As Campaign Members: Enter "Accounts As Campaign Members" in the Quick Find box.
Enable Accounts As Campaign Members: Select the option "Enable"
Save Your Configuration: Click "Save" to ensure the settings are applied.
This setting is mandatory if you want to deal with Account Enrichment through Delpha Campaigns.
To activate the feature allowing users to relate a contact to multiple accounts in Salesforce:
Navigate to Setup: Click the gear icon and select "Setup."
Search for Account Settings: Use the Quick Find box to locate "Account Settings."
Enable the Feature: Find the "Contacts to Multiple Accounts" option and check the box to enable it.
Save Changes: Click "Save" to apply the changes.
This setting is recommended when dealing with contacts belonging to different accounts.
Token Usage – Track API token consumption
Duplicates – Manage deduplication logic and thresholds
Job Tracker – Define rules to apply when a job change is detected
Default Values – Set fallback values when a record is created by Delpha
ignore the recommendation
Activate Auto Merge – Enables automatic merging of duplicate records based on confidence scores and predefined rules
These initial steps are essential for enabling Delpha’s smart deduplication workflows in Salesforce.
These settings give you precise control over the logic used for deduplication, enabling more accurate and tailored detection strategies.
Delpha Data Quality – Monitor and resolve data issues like duplicates, missing fields, or invalid values
Delpha Score Meter – View and track data quality scores across your org for better decision-making
These apps work together to ensure powerful data governance and enrichment within Salesforce.





Build smart, no-code conversational workflows with Delpha’s Conversation Builder in Salesforce. Guide users with interactive Q&A and automate business logic all within a visual decision-tree interface
All the conversations available in your org are listed here.
From here, you can edit existing conversation or create new conversations.
Fix some limitations related to the Auto Number fields when used in Expression or Filtering rules.
Delpha merges Salesforce duplicates via AI score, steward validation, or bot confirmation. Set up a daily Apex job to automate approved merges and streamline CRM cleanup.
Delpha offers three ways to merge duplicate record pairs automatically or manually:
Auto Merge via Score
If the pair score exceeds the Auto Merge Threshold, the status is set to Auto Yes and merged automatically.
Merge Confirmed by Data Steward
If a data steward validates the pair from the Duplicate Data Steward View, the status becomes Steward Yes, triggering an automatic merge.
Merge via Conversation Bot
When the duplicate is confirmed by the user through a Delpha conversation, the status changes to Bot Yes, and the merge is performed immediately after clicking the Merge button.
In the Duplicate Initialization section of the Delpha Setup app, select at what time you want the Auto Yes and Steward Yes pairs to be processed daily.
In the Auto Merge Scheduler:
You can select multiple times in the day
The time display in the picklist is your Salesforce Local Time.
Connect your Salesforce org to Delpha, review configuration health, and optimize batch size settings for the Ultimate Account use case. Ensure smooth setup and maximum performance.
Establish a secure connection between your Salesforce org and Delpha's backend. This may require authentication and enabling API access. If not connected, follow the prompts to complete the setup.
Check for any missing or incorrect settings. If issues are detected, Delpha provides step-by-step instructions for remediation to ensure proper functionality.
Defines how many accounts are processed per batch in the Ultimate Account use case. A green check indicates the correct setting. If not, follow the recommended adjustments to optimize batch processing.
Explore all the latest updates to the Delpha Data Quality use case here.
Data Steward Views – Changes in how data stewards can manage, filter, and act on data.
This structure helps users quickly find what’s relevant to their role or workflow.
Location: choose the closest (e.g., Europe or United States).
Leave “Pipeline” inactive.
Click Create app.
Package Id: 04tRl000001JK45IAG
Package URL : /packaging/installPackage.apexp?p0=04tRl000001JK45IAG
Once the upgrade package is installed, open a developer console and run the script below.
If you use a boolean field (e.g., Do Not Assess) to exclude certain records from duplicate detection, make sure to update your detection scope in App Delpha Setup > Duplicate > Detection Settings, under the Record Filter section.
If you skip this configuration, the duplicate analysis will run on all records, which may consume more credits than intended.
delpha.DDQ_MultiDuplicateSettingsMigration.executeMigration();heroku addons:create delpha-data-quality:CUSTOM_PLAN_NAME --app YOUR_APP_NAME_HEREBefore: Managing duplicate filtering and matching logic required editing complex JSON structures manually.
Now:
Filtering rules are applied from Top to Bottom. Once a rule is applied the filtering processing stops.
You can reorder the rules by drag / drop. We recommend packing the 'Keep' rules at the end of the list, after all the 'Discard' rules.
With the new visual rule builder, you can:
Define Filtering Rules and Matching Expressions using clear, editable blocks.
Instantly see and adjust logic with intuitive field comparisons (e.g., “if BillingCity is not the same…”).
Remove the risk of syntax errors—no more editing raw JSON!
Enjoy a more organized layout for thresholds, filters, and expressions.
Existing rules have been migrated automatically—just open the new interface to start using it right away.
Conversations – View and manage imported conversation components
Conversation Builder – Customize and create new conversation flows
This section is essential for Delpha Administrators managing Delpha integration and workflows.
AI Threshold Minimum confidence score for a pair to be flagged as a potential duplicate.
Auto Merge Threshold Score from which records will be automatically merged without user review.
Expression - Direct Match rules The initial condition to detect potential duplicates. Think of it as a formula requiring exact matches between specific fields (e.g., Name + Website).
Active Toggle Quickly enable or disable duplicate detection for the object.
Post-detection logic that allows you to add comments or discard certain pairs based on specific field-level differences. Example: Discard if cities differ.
Filtering rules are applied from Top to Bottom. Once a rule is applied the filtering processing stops.
You can reorder the rules by drag / drop. We recommend packing the 'Keep' rules at the end of the list, after all the 'Discard' rules.
Screening Fields These are the primary fields (e.g., Name) used to determine if a pair is even worth comparing. If values differ too much, Delpha skips the pair.
Discard Values
If any key field contains a listed value (e.g., "test", "dummy"), Delpha will ignore it during duplicate scoring.
Syntax: comma-separated list with no spaces or quotes — e.g., text1,text2,text3

Match By
Description: Defines how Delpha matches accounts between Salesforce and LinkedIn
Options:
By ID then by Name (default)
By ID
By Name
Purpose: Ensures accurate enrichment by prioritizing LinkedIn ID with fallback to name matching
Create New Active Accounts
Description: Determines what to do if a contact’s job points to an account not in Salesforce
Options:
Do Nothing
Manage Contact Has Moved
Description: Handles how Delpha reacts when a contact has changed companies
Options:
Do Nothing
Use Match By to determine how Salesforce accounts should be matched with LinkedIn data. The recommended option is "By ID then by Name."
Configure Create New Active Accounts to define the level of automation for handling new accounts, from manual prompts to full automation.
Adjust Manage Contact Has Moved to decide how contact movements should be handled, with options ranging from no action to automatic updates or contact creation.
App Delpha Setup > Data Quality > Contact > LinkedIn
If Active, the system will proceed to replace the existing contact title with the new one from LinkedIn, based on the prioritization logic below.
None, do not update the title: The system fetches the data but does not push any update to the title field.
Only update with the latest Job Title: The system applies the most recent title from the contact's job history.
Only update with the Profile Title: The system applies the title listed on the main LinkedIn profile (often the headline).
Prioritize latest Job Title, else use Profile Title: The system attempts to apply the latest Job Title first. If it's missing or invalid, it defaults to the Profile Title.
Prioritize Profile Title, else use latest Job Title: The system attempts to apply the Profile Title first. If it's missing or invalid, it defaults to the latest Job Title.
App Delpha Setup > Data Quality > Duplicate Duplicate settings have been separated into two distinct categories: Detection Settings and Merge Settings.
App Delpha Setup > Data Quality > Duplicate > Detection Settings

Import conversation modules in Delpha to enable automated handling of duplicates, enrichment and data quality via Delpha Bot. Easily manage records and boost data health through guided conversations
To enable conversational features in Delpha, import the relevant modules via the Import Data section and click Import Data. These modules power Delpha Bot’s interactions for handling data quality, duplicates, and enrichment.
All imported conversations will appear in the Conversation Builder.
To Remove all conversations from a Conversation Module from your org, just select the module and hit Remove Data
Delpha’s Duplicate menu helps you set up, detect, and clean duplicate Salesforce records with configurable rules and step-by-step remediation workflows.
The Duplicate section under Use Cases Setup helps you manage the full lifecycle of duplicate detection and remediation:
Duplicate Detection – (e.g., Account, Contact)
Run Your First Duplicate Detection – in Salesforce
Duplicate Merge – Define , user actions, and review workflows
This menu guides you from setup to execution, ensuring a structured and scalable approach to duplicate management.
We assume that the technical setup of Duplicate has been already done during the
Configure Delpha to detect duplicates in Salesforce with scheduled assessments. Enable continuous scans and initialize the detection engine to maintain clean and duplicate-free records.
The Duplicates section allows you to set up and control how Delpha detects and manages duplicate records in Salesforce. This helps ensure cleaner, more consistent data across your org.
Initialize
Purpose: Sets up the duplicate detection engine with default settings
Action: Must be clicked to enable duplicate use case
Result: Import the standard detection and merge settings.
Configure Delpha’s master record selection rules and predefined values to automate duplicate merges. Ensure clean, consistent data with flexible merge object logic.
The Merge Object Rules Section lets you define how the master record is selected and how field values are handled when merging duplicates:
Master Record Selection – Set the default rule for picking the surviving record (e.g., most recently updated, highest score).
Custom Rule for Master Record Selection – using advanced conditions.
Default rules for field selection – , ensuring compliance with business rules.
These rules help automate and standardize merge behavior across all duplicate resolution workflows.
Delpha merge field rules ensure high-quality Salesforce data by selecting values based on creation/modification date or data completeness. Choose the best default rule for your duplicate resolution.
Once the master record is selected during a merge, Delpha needs to determine how to choose the final field values. By default, it uses the Master and Not Empty rule.
These rules help ensure Delpha always retains the most complete and relevant data in the merged
Customize duplicate merges with Delpha’s Custom Master Record Rule. Use formula-based scoring to prioritize records and define fall back to creation date for tie-breaking.
If your merge logic needs to follow more advanced or business-specific rules, Delpha allows you to define a Custom Master Record Rule. This approach lets you assign a score to each record in a duplicate pair based on a custom formula and select the one with the highest score as the master.
Define a Custom Scoring Field
Create a formula field (e.g., DC_MasterScoring__c) to assign points based on your business rules.
Example Use Case:
If Account Type = Customer → +10 points
This setup allows your master record selection process to reflect your business priorities precisely.
The Delpha messages can contain more than simple texts. By inserting special tags, you can display dynamic and formatted messages. Tags can be used to modify text style, add icons, add images, add hyperlinks, or insert a variable value. The tags can be used on any message displayed to the user such as:
In the builder, via the message/question/answer display text field.
Step-by-step guide to create a “Hello” conversation in Delpha: use Conversation Builder, set display rule, add welcome message, question/answers, and activate.
Delpha’s Fields section defines how specific fields are compared to detect Salesforce duplicates. Adjust weights, match types, and rules to improve AI-driven duplicate detection accuracy.
Email-to-Case Duplicate Detection maps email data to Salesforce fields, applies look-back limits and uses filters to target relevant records—ensuring faster, cleaner, and more accurate case management
Ask to Create a New Account (default)
Create Automatically New Active Accounts
Create Automatically and Link Contact to Account
Ask to Move (default)
Move Automatically When Possible
Move Automatically and Update Title
Ask to Create a New Contact
Create New Contact Automatically When Possible
Clean Settings
Purpose: delete all existing duplicate settings and revert
Continuous Assessment
Purpose: Automatically scans for duplicates every 12 hours
Frequency Setting: Adjustable (e.g., Twice a day, Never.) via dropdown
Configure Continuous Assessments for accounts, contacts, leads, or cross-object duplicates as needed.
Use the dropdown menus to adjust how often duplicate assessments run (e.g., daily, weekly, or never).
Regularly enabling these processes helps ensure Salesforce data remains accurate and free of duplicates.
If Account Type = Target → +1 point
Otherwise → 0 points
Set the Custom Rule Expression
Use:
DC_MasterScoring__c Desc, CreatedDate
This tells Delpha to:
First, select the record with the highest custom score
Then use the oldest created date as a fallback if scores are equal
Use Case Logic Covered:
Customer > Prospect > Target > Oldest

Duplicate Field Name
The API name of the field being used for comparison (e.g., Name, Website).
Weight Determines the importance of the field in the overall match score. Higher weight = greater influence on the duplicate score.
Type Specifies the type of matching used:
Exact Matching – Compares identical values
Fuzzy Matching – Allows for slight variations (e.g., typos, casing) Tip: Click the help link in-app to explore matching algorithm types.
Mandatory When checked, empty values reduce the confidence score for that field. Ensures stronger matches only when relevant data is present.
Active Toggle to include or exclude a field from the duplicate detection process.







Address general data quality issues
/
Module
Description
Comment
DuplicateAccount
DuplicateContact
DuplicateLead
DuplicatePersonAccount
LeadVsContact
Handle duplicates
WD: The only option is to merge with all related items Information: Merge not allowed with this conversation
Account Enrichment
Manage account pipeline enrichment
/
LinkedInEnrichment
Perform standard LinkedIn enrichment
/
LinkedInEnrichmentAdvanced
Advanced LinkedIn enrichment
/
Data Quality
Uses field from earliest update, but skips if value is empty
Latest modified date & not empty
Uses field from latest update, but skips if value is empty
Rule
Description
Oldest created date
Uses the field from the earliest created record
Latest created date
Uses the field from the most recently created record
Oldest modified date
Uses the field from the earliest updated record
Latest modified date
Uses the field from the most recently updated record
Oldest created date & not empty
Uses field from oldest record, but skips if value is empty
Latest created date & not empty
Uses field from latest record, but skips if value is empty
Oldest modified date & not empty
This version provides a fix on the mass process from the Duplicate Data Steward view: some duplicate records pairs could be deleted before or after being processed
This issue is only impacting the display of the duplicate pairs. No record is wrongly deleted because of it.
Dedicated UI: App Delpha Data Quality > Tab Delpha User Settings
This UI can only be used if the Delpha Connector Chrome extension is installed in your browser.
If the extension is not installed, or if you prefer to manually set a cookie for a user profile, go to Delpha Setup → User Settings. Then edit the user settings you want to update.
You can access this page directly, or simply click the alert shown in the Delpha Score component when a configuration issue is detected. Click the red-dot icon to open the Delpha User Settings page instantly.
When an address recommendation is available, it is displayed to the end user in the Score Meter. The user can accept or reject it directly from the Score Meter, based on the data quality analysis and the recommendation’s confidence score.
For any monitored field, if the unicity value is not equal to 1, you can click the message shown in the score meter to display all records involved in the unicity issue.
From that window, you can open and review each record.
Add message/indicator on score meter when record is locked
The comments now explain how the Ultimate Parent was determined and provide the justification for mapping it to an existing account.
If the Ultimate Parent does not already exist in your org, the resolution process will automatically create it (score meter or data steward view).
More info on Ultimate fields and Ultimate Parent analysis.
3 step process:
Click on the link and enter the Duplicate process.
Select the potential duplicate candidate or discard the candidates
Select the Master record, review and select the data you want to keep and merge
All the pre-selected values come from the rules set in the Duplicate Merge section of the Duplicate Setup.
In the apex code, while creating dynamic answers.
Default or custom variable defined in the builder can be displayed in the bot using the following tags: Tag: {!VariableName} Example: {!CurrentRecordId}
Tag: {!VariableName.FieldName} Example: {!CurrentRecordId.Email}
Tag: {!VariableName.RelatedObject.FieldName} Example : {!CurrentRecordId.Contact.Name}
The associated records can be accessed by chaining them as shown above, and you can go on like {!CurrentRecordId.Contact.Account.Name}.
Tag: [record Id= value]display text[/record] The value can either be hard-coded or a variable, as shown below: Example:[record id=0031D00000aIxZtQAK]Andy Young[/record] Example:[record id={!targetRecordId}]Andy Young[/record]
Tag: [b]Bold Text[/b] Example: Discover [b]California[/b]
Tag: [br/] Example: Discover [br/]London
Tag: [i]Italic Text[/i] Example: Discover [i]Prague[/i]
Tag: [u]Underlined Text[/u] Example: Discover [u]Paris[/u]
Tag: [color=value]Colored Text[/color] The value can either be color name or hexadecimal code as shown below: Example: [color=green]Hello World![/color] Example: [color=#FF0000]Hello World[/color]
Tag: [icon]IconType:IconName[/icon] Example: [icon]standard:announcement[/icon]
Tag: [img]Image Link[/img] Example: [img]https://delphaimage.png[/img]
Tag: [img]https://img.png[/img][img width=50] Note: Currently, Salesforce doesn't consider the image height attribute added in the tags. However, the image scaling is respected during rendering.
Tag: [url]external link[/url] Example: [url]https://delpha.io[/url]
Tag: [url=external link]display text[/url] Example: [url=https://delpha.io]AI for Productivity[/url]
Tag: [url=external link][img width=50]Image link[/img][/url] Example: [url=https://delpha.io][img width=50]https://img.png[/img][/url]
For security reasons and to avoid vulnerabilities such as XSS, we only support our tags.
Click New Conversation on the conversation builder page and enter a name. Append your organization’s name on the trial environment for reference.
To start your conversation, click on the grey ‘ + ’ button. Once you click on the first ‘+’ button, a new node for conversation initialization is created.
Click on Initialization, select previously created display rule (Hello on Home Page) under Display Rule and Save.
Create a Message, add “Hello” as the welcome message and Save.
Create a question, add “How are you doing?” as the display text and Save.
Create two Answers “Good” and “Okay” and Save.
The conversation at this point should look something like this.
Create New nodes under Good and Okay. Add relevant Message to each node
The completed conversation should look like this. Activate the conversation and test the Hello conversation on the Home Page.
You must activate the conversation to make it visible to the Delpha Users. Click on the Activate Button
The email address of the person who sent the email. This is used to identify the Contact or create a new one if needed.
Case CC List
D CC Address
All recipients in the CC of the email are stored here. They can be used to track stakeholders copied on the case. D CC Address is a Delpha custom field.
Case Subject
Subject
The email subject line becomes the case subject. This helps categorize and search cases quickly.
Case Body
Description
The email body (message content) is inserted into the case description so that agents see the original customer message.
These fields are used for duplicate detection.
When searching for potential duplicate cases, the system needs to compare each newly created case with past cases. Since both open and closed cases are considered, the number of possible matches is restricted by defining a maximum look-back period based on the case creation date.
Case Filters let you define conditions that limit which cases are considered during duplicate detection. You can select any case field or any field in a related object, choose an operator (equals / not equals), and combine multiple filters with AND logic to focus only on the cases that matter.
To only compare cases where Case Origin = Email and where Account.Billing Country = United States.
This ensures the assessment process runs only on the subset of cases created through the Email to Case process and associated to US Accounts.
Case Field (Salesforce)
Email Field (Source)
Explanation
Case Sender
Email Address
Customize how Delpha scores and enriches Salesforce Account data. Set automated rules, reassessment schedules, and quality thresholds. Maintain accurate and up-to-date Account records effortlessly.
The Data Quality – Account section lets you define how Delpha evaluates, scores, and improves your Salesforce Account records. It helps ensure data remains complete, consistent, and ready for decision-making.
Account Assessment Criteria Field
Use a Boolean field to filter which Accounts should be assessed. By default, Delpha uses the Account.D Do Not Assess field, but you can define your own formula-based field for dynamic control.
Account Assessment Enable this to assess all existing and new Accounts once.
Account Continuous Assessment Automatically reassess Accounts whenever a monitored field is updated.
These settings activate Data Quality automation that will consume tokens to ensure optimal data quality in your org.
If you want to control the token consumption we recommend you
to not activate:
Fields monitored for quality scoring:
Website
Billing Address
Shipping Address
Phone
For each field, you can:
Enable or disable its inclusion in the quality score
Set automatic recommendation rules (trigger + score threshold)
Trigger: When value is Incomplete
Score Threshold: 100
Trigger: Disabled
Score Threshold: (none set)
Evaluates and maintains relationships with ultimate accounts to clarify ownership hierarchies.
Calculates a global quality score across all Accounts daily, giving you a snapshot of overall data health.
The Delpha Score Meter provides a clear 0–100 quality score based on six dimensions, helping you assess, prioritize, and improve Salesforce data accuracy and reliability at a glance.
The Score Meter is your all-in-one command center for data quality. It helps you understand, review, and apply improvements — all in a single, intuitive interface.
See your overall quality score for the selected object (e.g. Accounts, Contacts).
The score is visually represented with a color-coded gauge for quick assessment.
The number of available recommendations is clearly listed.
View AI-generated recommendations directly from the Score Meter.
Each recommendation includes:
A confidence score based on the data quality dimensions
Extra information to help the decision
Choose how to apply recommendations:
One by one
Bulk select multiple items
Accept all suggestions in one click
The score is based on six key data quality dimensions, evaluated field by field:
Each field within the record is evaluated and color-coded:
Red – Poor
Orange – Warning
Green – Good
Grey – Not applicable / no data
How to automatically handles duplicates with configurable thresholds, merge or parent options, child status rules, and attachment cleanup—keeping Salesforce cases clean and efficient.
Define the score threshold above which duplicate cases are automatically processed.
Defines how duplicate cases are automatically handled once they reach the configured Auto Remediation threshold score. You can choose between several modes:
None – No automatic action is taken. Duplicates are only flagged.
Auto – The system decides the most appropriate action (merge or assign parent) based on your configuration.
Merge – Duplicates are automatically merged.
Delpha applies the merge behavior defined on Salesforce Setup.
Service Setup > Process Automation > Case Merge
Assign Parent – The duplicate is automatically linked to an existing parent case.
The Master case is always the oldest case, which may be either Open (still in progress) or Closed.
If the Master case is Open, you can choose to either merge the two cases or assign the Master as the parent of the new case.
Child Case Status lets you define what status the duplicate (child) case should take after a merge or parent assignment.
Possible values include New, Working, Escalate, or Closed.
This ensures that all child cases follow a consistent lifecycle once they are processed, avoiding conflicting or outdated statuses.
In short: it standardizes the post-processing state of duplicate cases, keeping your case management clean and predictable.
Assign Parent / Merge Options let you control which fields are copied from the Master case to the Child case after a merge or parent assignment.
You can select up to 5 fields.
This ensures important information (e.g., OwnerId, priority, category) is consistently inherited by the Child case.
It helps maintain data quality and consistency across merged or linked cases.
In short: this option defines which Master case details should overwrite or update the Child case after remediation.
This option automatically removes duplicate attachments when using the email-to-case functionality. It prevents the same file from being stored multiple times across redundant cases, reducing clutter and saving storage space while keeping case records clean.
In short: it ensures only unique attachments are retained in cases created from emails.
The analysis is based on both the attachment’s name and its size, and only exact matches are considered duplicates.
Use Delpha’s Duplicate Data Steward View to detect and merge Salesforce duplicates at scale. Compare fields side by side, trust AI-powered scores, and clean your data with precision and confidence.
The Duplicate Data Steward View is designed to help you efficiently identify and merge duplicate records in Salesforce. Using side-by-side comparisons, smart scores, and visual cues, you can quickly take action with confidence.
The navigation in the Duplicate Steward view is aligned with Salesforce’s native List View experience:
Cog icon: Use the standard cog to manage your views (create, clone, rename, share, select fields to display, delete)
Filter Icon: Create custom views filtering on a Campaign, an Object, a Field and the score.
Pinned and Favorite Lists: Find the best view when you need it
At the top of the screen, a summary dashboard provides a snapshot of duplicate detection:
Total Potential: Total duplicate groups detected (e.g., 806)
Match Categories:
Exact Match, Likely Match, Possible Match, Unlikely Match
Each row shows:
Account name variations
Field-level identifiers (e.g., Website, LinkedIn)
Match Status (e.g., Potential, Auto Yes)
Score (0–100 confidence)
When you select a row, Delpha displays a detailed comparison view:
Fields from both records are shown side by side
Green dots = selected master value
Red highlights = mismatched fields This layout helps you quickly decide what data should be kept post-merge.
When rows are selected, the following actions appear at the top:
Accept
Merge using recommended values
Finalize the merge and mark as processed
Reject
Filter by object (e.g., Account)
Review suggested matches
Click to open detailed comparisons
Select records
Merge operation is not applied instantly. Duplicate that are validated by the Data Steward are processed by batch following a .
The Delpha Data Steward Quality View offers an intuitive interface to monitor, clean, and optimize Salesforce data. Filter by field and object, apply smart recommendations to meet high data quality
Build smart, no-code conversational workflows with Delpha’s Conversation Builder in Salesforce. Guide users with interactive Q&A and automate business logic all within a visual decision-tree interface
The article provides a high-level description of the processes and components involved in building a conversation using the Delpha conversation builder. The Delpha Author can be defined as the user of Salesforce who has access to the Delpha conversation builder.
The author playground mainly comprises:
Delpha Conversation Builder
The conversation builder is a no-code interface used to build new conversations and review existing templates, whereas, the configuration is used to install and uninstall templates.
Salesforce flow module
Configure how Delpha assesses, cleans, and enriches Salesforce Contact data. Set automatic rules for fields update and track global quality scores to maintain clean, reliable contact records.
Use Delpha’s Merge Field Rules to control which values are kept during Salesforce merges. Apply control specific automated logic,different from the default one.
The Merge Field Rules screen lets you override the default behavior set in the . This powerful interface allows you to define exactly which value should be kept for each field during a merge—ensuring consistent, automated decisions that align with your data governance policies.
Never, Once a Month, Once per Quarter, Twice a Year, Once a Year.Account Continuous Assessment: if you do a mass update impacting a monitored field, the records are supposed to be reassessed.
Account Reassessment: if a record has not been assessed for more than x months, it will be automatically reassessed, according the setting.
Legal ID
When value is inconsistent
Use Account Assessment and Account Continuous Assessment to ensure all accounts are reviewed and updated whenever changes occur.
Configure Account Reassessment to address potential data decay by selecting a reassessment schedule.
Select the fields involved in Quality Score definition by toggling them on or off.
Define the automation rules for automatic data quality remediation
For hierarchical relationships, activate Ultimate Account Assessment when needed.
Enable Global Scoring for a daily, holistic view of account quality.


You can expand or collapse details for quick scanning or deep inspection.
Track data quality improvements over time
Completeness
Is the value present or missing?
Validity
Does the data follow the correct format or rules?
Uniqueness
Is this value duplicated elsewhere in the system?
Consistency
Is the data coherent across fields or systems?
Accuracy
Is the value correct (factually or logically)?
Timeliness
Is the information still relevant and up-to-date?



Total to Be Merged: Duplicates awaiting confirmation
Processed status (True/False)
Dismiss the suggestion
Keeps records unchanged
Delete
Permanently remove selected records (⚠️ use with caution)

When Auto is selected, Delpha automatically merges the new case if the Master is Open, and re-parents it when the Master is Closed.












The navigation in the Data Steward view is aligned with Salesforce’s native List View experience:
Cog icon: Use the standard cog to manage your views (create, clone, rename, share, select fields to display, delete)
Filter Icon: Create custom views filtering on a Campaign, an Object, a Field and the score.
Pinned and Favorite Lists: Find the best view when you need it
Total records reviewed
Average data quality score
Breakdown of quality indicators: Complete, Valid, Consistent, Accurate
Click once: Filter for records that pass a dimension (tile turns green)
Click again: Show records that need fixing
Click Recommended: Show only records Delpha has suggested improvements for
Each record shows:
Current values
Field-level quality indicators
Recommended corrections
Score & status:
Auto Yes – Your value already matches the recommendation
Potential – A new recommended value is available
Not Found – No suggestion available
Failed – Error in analysis
Choose the object: Contact or Account
Select the field: Email, Phone, LinkedIn, etc.
Completeness, Validity, Uniqueness, Consistency, Accuracy, Timeliness
Color indicators:
Green = Good
Yellow = Warning
Red = Issue
Gray = Not Applicable
Each field is analyzed based on 6 data quality dimensions:
Completeness
Is the field filled in?
Validity
Does it follow the expected format or rules?
Uniqueness
Is it duplicated across the dataset?
Consistency
Is it aligned across systems or related records?
Accuracy
Is it factually correct?
Timeliness
Is it up-to-date?
Apply: Accept Delpha’s recommendation
Reject: Ignore and keep the current value
Delete: Remove the selected record(s) entirely (use with caution)
The conversation is used to describe a use case. It facilitates interactive communication with Delpha assistant & end-user. Every conversation relies on 3 fundamental steps :
Recommendation These are based on contextual rules. The author can define when and where a particular conversation (use case) is proposed.
Engagement Guide the end-user through predefined & Interactive questions & answers.
Execution Take necessary actions to deal with the corresponding use case efficiently.
The Builder consists of 3 main components:
Toolbox: The toolbox appears on the extreme left and comprises all the author's text and variables while building a conversation. The messages, questions, and answers are filled automatically while variables used in the conversation need to be defined by the author.
Tree Canvas: The canvas appears in the center. It is the working area and gives a high-level description of the conversation or the use case defined in a decision tree. The author can initialize and create nodes here.
Properties: The Properties tab appears on the extreme right and allows the author to define properties, including messages, questions, and answers associated with each component of the decision tree.
In the Initialization window, you can define:
Display Rule: Defines the page(s) on which the author wants the recommendation from the assistant.
Conditions: Define rule-based evaluation criteria on string fields to display the recommendation.
Action Type: Defines evaluation criteria for contextual rules which cannot be defined using conditions. This can be achieved using a Flow, an Apex.
Once the initialization criteria are valid, you can start the conversation The conversation is made up of nodes that are organized as a decision tree.
A conversation is made up of nodes. It is the key part of the decision tree and can act either as a redistribution point or endpoint of the conversation. Node consists of:
Unique node name
Message(s)
A question and answer(s) to engage the user and take action.
Answer
The Answer is the key component of the node which lets the author define the type of answer and the action to be taken upon the selection of an answer.
The answer can be Static or Dynamic
Static answers display fixed answers.
Dynamic answers display a list of dynamic values to select. The values are passed and stored using variables (discussed later).
The Answer can be Single select or Multi-select
The Selection view enables checkboxes, whereas, comparison view enables radio buttons.
The Answer can lead to an action or not lead to an action
The toggle switch can activate new action. The new action can be flow, quick action, apex, conversation, or open in a new tab
Variables
Variables are placeholders. They are used for storing and retrieving values in the conversation flow (actions or messages).
Variables can be created on the toolbox and can have multiple formats such as string, number, list, object, Id. The action type requires a set of input and output variables. Example: Input variables such as account Id passed to Flow, which processes the information and provides an output(s) used in the conversation. Variables can be classified into two types:
Global variables Read-only built-in variables to reference common information throughout the conversation. Currently, there are 2 global variables CurrentPage and CurrentRecordId
Conversation variables User-created variables. They are used to transfer information/data from an action (Flow, Apex) to a conversation or between 2 conversations.
Contact Assessment Criteria Field
Filter which Contacts should be assessed using a Boolean field (default: Contact.D Do Not Assess). You can use a formula field for more dynamic control.
Contact Assessment Enable this to assess all existing and newly created Contacts once.
Contact Continuous Assessment Automatically reassess Contact records when a monitored fields change.
Contact Reassessment
Schedule regular reviews even if the record hasn't changed.
Options: Never, Once a Month, Once per Quarter, Twice a Year, Once a Year.
These settings activate Data Quality automation that will consume tokens to ensure optimal data quality in your org.
If you want to control the token consumption we recommend you
to not activate:
Contact Continuous Assessment: if you do a mass update impacting a monitored field, the records are supposed to be reassessed.
Contact Reassessment: if a record has not been assessed for more than x months, it will be automatically reassessed, according the setting.
Configure how Delpha standardizes and corrects first and last names:
Apply Recommendation Automatically Set conditions (e.g., inconsistent value) and minimum score threshold for auto-correction.
First/Last Name Rules Control letter case, allowed characters, spacing, and removal of unwanted text blocks.
Letter case
Controls capitalization. typical: Capitalize All or ALL UPPERCASE
Characters
Specifies accepted alphabets.
Spacing
Handles white spaces.
Text Blocks
Handles titles or text in parentheses.
Monitored Contact fields:
Name
Phone
Mobile Phone
Mailing Address
For each field, you can:
Include/exclude it from quality scoring
Define when recommendations are applied
Set a score threshold (default: none)
Trigger: When value is Incomplete
Score Threshold: 100
→ Only perfect recommendations are applied automatically
Phone
Trigger: When value is Inconsistent
Normalization enabled (no score threshold needed)
Automatically computes a daily quality score for all Contact records—giving you a clear view of your data health at a glance.
Key Takeaways for Users:
Adjust the Criteria Field to include or exclude specific contacts from assessments based on your organizational needs.
Enable Contact Assessment and Continuous Assessment to ensure all contacts are reviewed and updated whenever changes occur.
Configure Contact Reassessment to prevent data decay by setting a reassessment schedule.
Select the fields involved in Quality Score definition by toggling them on or off.
Define the automation rules for automatic data quality remediation
Use Global Scoring to monitor the overall quality of contacts daily.
Rule Name
The label for your merge rule (can be customized).
Action
Indicates whether the field is grouped or individually customized.
Field
The API name or label of the field the rule applies to.
Override Rule
Specifies what value to keep: e.g., Master and Not Empty, Highest Value, or Empty.
Operation
Special logic applied (e.g., ConcatenateUnicity to merge unique values).
Visible
Whether this field is shown in the bot deduplication conversation.
Active
Whether the rule is currently being used during merge operations.
Each row in the panel defines a rule for a specific field, guiding how the final merged value is selected.
Master and Not Empty: Keep the master record’s value—unless it’s empty.
Highest Value: Ideal for dates or numeric fields (e.g., latest activity).
Empty: Clears the field value post-merge.
ConcatenateUnicity: Combines unique values (perfect for multi-entry fields like tags or IDs).
These rules are applied when you Accept a merge from the Duplicate Steward View. As a result:
The best value is selected automatically
Manual review is minimized
Merges stay clean, reliable, and aligned with business rules
Click New (top right) to define a custom merge behavior for any additional field.
Some practical applications:




Duplicate Settings now support multiple configurations. You can define a dedicated scope for each configuration using advanced rules in the Record Filter section.
Each configuration runs its own full duplicate assessment, and the results appear separately in the Duplicate Data Steward View.
To create a new Duplicate Setting, click Add New, choose the target object, and decide whether to start from the Delpha default template for detection and merge settings. You can also duplicate an existing configuration using the Clone option.
The goal of the Record Filter is to limit the scope of the duplicate scan, ensuring the system only checks records that meet specific criteria you define.
Filter Logic: This area allows you to combine multiple individual conditions using boolean operators (AND, OR, NOT) to create complex filtering rules.
e.g., 1 AND (2 OR 3): This example illustrates how the logic works. It means:
Condition 1 must be true, AND
Search Input Field: You use this to find and select a field name from your database (e.g., Status, Creation Date, Region).
Add Condition Button: Once you select a field, you click this button to add a new condition row.
Condition Rows (implied below the image): Each row will typically let you:
Example Use Case:
You might set up a filter to only check records where:
Status Equals Customer
AND Last Modified Date Is Greater Than 90 days ago
This filter ensures the duplicate detection process only runs on active customer records that have been modified recently, saving processing time.
If you use a boolean field (e.g., Do Not Assess) to exclude certain records from duplicate detection, make sure to update your detection scope in App Delpha Setup > Duplicate > Detection Settings, under the Record Filter section. If you skip this configuration, the duplicate analysis will run on all records, which may consume more credits than intended.
You will have to set up a filter to only check records where:
The purpose is to apply specific rules before potential duplicates are reviewed and merged.
The rules are divided into different Rule Types that trigger specific actions:
The Matching Fields configuration, is the core mechanism used by the application to calculate the numerical Duplicate Score for any pair of records. This section defines what fields matter and how much they matter when determining if two records are duplicates.
This screen shows the Advanced Settings for duplicate detection. This section provides granular control over how the system initially screens for duplicates, cleans data for scoring, and manages duplicate creation in real-time.
Purpose is to quickly filter the large pool of records down to a smaller, more relevant subset before the full, weighted matching score calculation (from the "Matching Fields" section) is performed. This significantly improves performance. The system performs a fast initial match (relying on Name). If the name match is inconclusive, it uses these Screening Fields (e.g., ZIP Code, First Letter of Company Name) to narrow down which records should proceed to the full scoring calculation.
Purpose is to prevent "dummy" or default values in your records from artificially inflating or skewing the duplicate match score.
You can enter common placeholders that should be ignored into the input field or directly select them from the proposed values.
Define the system's immediate response when a user attempts to create a new record that matches an existing record. This is a crucial real-time defense against data decay.
You choose an option from the dropdown menu to determine what action the system takes:
Either Condition 2 OR Condition 3 must be true.
The numbers (1, 2, 3) refer to the individual conditions defined below.
Select a Field (e.g., Record Status).
Select an Operator (e.g., Equals, Is Not Null, Is Greater Than).
Enter a Value (e.g., Active).
Do Not Assess Equals FalseSetting
Status/Value
Explanation
Activate Duplicate Detection
Active (Toggle On)
This is the master switch. Duplicate detection is currently enabled and running based on the configured rules.
Run Evaluation
Evaluate (Button)
This is the action button used to manually trigger the duplicate detection process. When clicked, the system scans the records and flags potential duplicates according to the rules and threshold.
Detection Threshold
50
This sets the minimum match score for a pair of records to be flagged as potential duplicates. Pairs must have a score $\ge 50$ (on a likely 0-100 scale) to be surfaced for review. A lower number flags more potential duplicates.
Rule Type
General Purpose
Action Taken
EXACT MATCH
Used to automatically flag a pair as a certain duplicate if they have an exact match on high-certainty identifiers.
If the specified conditions are met, the system automatically considers them as perfect duplicates. The score is set to the maximum (100), the Status is set to Auto Yes and a specified comment is added. This can prepare them for automatic or priority merging.
DISCARD
Used to prevent a pair of records from being considered duplicates if they match a specific rule.
If the values in the specified field(s) match, the system discards the pair. The Status is set to Auto No. The pair is not proposed to the Delpha User and can only be processed (accepted or rejected) by the Data Steward.
KEEP
Used to automatically flag a a pair by adding a comment if they match a specific rule.
When a pair of records meets the criteria of a KEEP rule, the system retains the pair in the set of potential duplicates and add a specific comment.
Option
System Action
Outcome
Allow (Async Detection)
(Default/Least Restrictive) The record is created immediately.
The duplicate check runs after creation, and the record is flagged for later review.
Block (Prevent Creation)
(Most Restrictive) The system performs a real-time check. If an exact match is found, it stops the creation process and forces the user to resolve the conflict (e.g., update the existing record).
Creation is prevented, ensuring no new duplicates enter the system.
