# Advanced Settings ### Overview The Advanced Settings section allows you to fine-tune how Delpha finds potential duplicates during the initial "screening" phase and how it handles low-quality "junk" data. These settings are optional but highly recommended for organizations with complex data (e.g., companies with very different names) or noisy data (e.g., placeholder values like "TBD"). ### 1. Screening Fields (Broadening the Search) By default, Delpha's detection engine often relies on the record's Name to identify initial candidates for comparison. However, if two duplicates have completely different names (e.g., *"International Business Machines"* vs. *"IBM"*), they might be missed during this first pass. Screening Fields act as a "backup plan" to ensure these records are still compared. * How it works: If you add fields here (like `Email`, `Phone`, or `Legal ID`), Delpha will use them to find candidates even if the Names do not match at all. * Recommendation: Add unique identifiers here (e.g., `Email` for Contacts, `Website` for Accounts) to catch hard-to-find duplicates. ### 2. Discard Placeholder Values (Reducing Noise) In many CRMs, users enter generic "filler" data when a field is required but unknown. If two records both have the phone number *"555-555-5555"* or the email *""*, Delpha might incorrectly flag them as duplicates because the data matches perfectly. This setting allows you to tell Delpha to ignore specific values. * How to Configure: 1. Type the value you want to ignore in the text box (e.g., `N/A`, `TBD`, `unknown`, `00000`). 2. Click Add. * Result: If a record contains one of these values, Delpha treats that field as "Empty" (Null) rather than a match. This prevents false positives caused by junk data. {% hint style="info" %} Delpha automatically runs an analysis of the scoped records and proposes all potential placeholders for you to select from a list. \ Generic filler limit is set to 50 occurrences. {% endhint %} --- # Agent Instructions: 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: ``` GET https://help.delpha.io/delpha-for-salesforce/use-cases-setup/duplicate/duplicate-detection/advanced-settings.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.