> 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/how-to-faq/delpha-duplicate/what-data-is-available-for-duplicate.md).

# What data is available for Duplicate?

## Understanding the DDQ Duplicate Record Object in Delpha

All information related to duplicate detection and resolution in Delpha is stored in a custom object called **DDQ Duplicate Record** (`delpha__DDQ_DuplicateRecord__c`).\
This object represents a potential or confirmed duplicate pair and includes critical information for scoring, processing, and merging.

***

#### 📋 Field Breakdown

| **Field Name**                | **API Name**                                        | **Description**                                                                                                             |
| ----------------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Duplicate Record Name**     | `Name`                                              | Identifies the type of object being deduplicated (Account, Contact, Lead, etc.).                                            |
| **Record Id**                 | `delpha__RecordId__c`                               | ID of the first member of the duplicate pair.                                                                               |
| **Matched Record Id**         | `delpha__MatchedRecordId__c`                        | ID of the second member of the duplicate pair.                                                                              |
| **Status**                    | `delpha__Status__c`                                 | Current status of the duplicate pair (e.g., Auto Yes, Potential, Steward No).                                               |
| **Score**                     | `delpha__Score__c`                                  | Confidence score calculated by Delpha's matching algorithm.                                                                 |
| **Processed**                 | `delpha__Processed__c`                              | Indicates whether the pair has already been processed (`true`) or not (`false`).                                            |
| **Comment**                   | `delpha__Comment__c`                                | Free-text comment often added by a **filtering rule** or by the merge process (including error messages for failed merges). |
| **Is Cross Record?**          | `delpha__IsCrossRecord__c`                          | Boolean field. `True` means this is a cross-object duplicate (e.g., Lead vs Contact).                                       |
| **Account / Matched Account** | `delpha__Account__c` / `delpha__Matched_Account__c` | Lookup fields to the Account objects involved.                                                                              |
| **Contact / Matched Contact** | `delpha__Contact__c` / `delpha__Matched_Contact__c` | Lookup fields to the Contact objects involved.                                                                              |
| **Lead / Matched Lead**       | `delpha__Lead__c` / `delpha__Matched_Lead__c`       | Lookup fields to the Lead objects involved.                                                                                 |
| **Case / Matched Case**       | `delpha__Case__c` / `delpha__Matched_Case__c`       | Lookup fields to the Case objects involved.                                                                                 |

## Where is This Object Used?

* During duplicate **detection**, scoring, and status assignment
* In the **Duplicate Steward View** to visualize potential duplicates
* To manage merge operations and track merge **history**
* For troubleshooting merge **failures** and applying **filtering logic**

## Tips

* Use the `Status` and `Processed` fields to monitor merge eligibility.
* Use the `Comment` field to debug failed merges or filtered exclusions.
* Reference `IsCrossRecord` if you're managing duplicates across different object types (e.g., Lead vs Contact).

{% hint style="warning" %}
Use the DDQ Duplicate Record to initiate a trigger after the merge operation  

* Processed = true + Staus = BotYes, StewardYes, AutoYes = Successfull merge !
  {% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-duplicate/what-data-is-available-for-duplicate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.