> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-for-salesforce/use-cases-setup/duplicate/duplicate-detection/matching-fields.md).

# Matching Fields

Configure Delpha Matching Fields, Field Weights, and Mandatory settings. Learn how Mandatory fields impact duplicate scores when values are missing (null).

### Overview

The Matching Fields section allows you to define exactly which data points Delpha compares to determine if two records are duplicates. Unlike simple exact-matching tools, Delpha assigns a "weight" to each field and a specific comparison model, allowing you to build a sophisticated scoring model.

### How to Configure Matching Fields

1. Access the Section: In the Detection Settings, click to expand the Matching Fields section.
2. Add a New Field: Click the New button.
3. Select the Field: Click Select Field and choose the Salesforce field to compare (e.g., `BillingCity`, `Name`, or `Website`).
4. Choose the Match Type: [Select the logic Delpha should use](/delpha-for-salesforce/how-to-faq/delpha-duplicate/what-algorithms-are-used-by-delpha.md):
   * String: Fuzzy matching (handles typos/nicknames).
   * Exact Match (boolean): Values must be identical.
   * Email / Phone / URL / Address/ Timestamp / Coordinate: Specialized logic for contact data.
5. Assign a Weight: Enter a numerical value (e.g., `100`) for the field's importance.

### Understanding "Mandatory" vs. "Optional"

[The Mandatory setting controls how strictly Delpha treats missing data.](/delpha-for-salesforce/how-to-faq/delpha-duplicate/how-does-the-duplicate-scoring-work.md#mandatory-checkbox)

* **Optional**: The field contributes to the score if a match is found. If the field is empty on one record, it simply yields 0 points for that specific field, but the records might still match based on other fields.
* **Mandatory**: The field is treated as a "Dealbreaker."
  * Impact on Empty Values: If a field is set to Mandatory and no value is present (the field is blank/null) on one of the records, it will negatively impact the total score.
  * Why use this? This prevents false positives. For example, if you set `Email` to Mandatory, Delpha ensures it does not incorrectly merge two people just because they share a name (e.g., "John Smith") if one of them is missing an email address entirely and if no other parameter is counterbalancing enough the negative impact related to the missing Email. 

### Understanding the Configuration Table

* Weight: The points contributed by this field. The Total active weight (e.g., `900`) is the maximum possible score.
* Active: Edit the rule to temporarily disable a field without deleting the configuration.

{% hint style="info" %}

* [**How the Score is Calculated**](/delpha-for-salesforce/how-to-faq/delpha-duplicate/how-does-the-duplicate-scoring-work.md)

  The score is determined using a proprietary algorithm that evaluates multiple factors. Each component is weighted differently to reflect its importance in the overall calculation. The final score is a comprehensive assessment of these elements, providing a robust measure of success.
  {% endhint %}

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-for-salesforce/use-cases-setup/duplicate/duplicate-detection/matching-fields.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.