LogoLogo
  • Delpha Documentation
    • Welcome to Delpha Documentation
    • Delpha Setup
      • Install Delpha
        • Install Delpha package from the Salesforce App Exchange
        • Assign a Delpha Permission Set Group
        • Assign a Delpha licence to the users
        • Connect the org to Delpha
      • Import Conversations
      • Extra Tasks
        • Check my org settings
        • Install Delpha Connector for LinkedIn Enrichment
    • Delpha Upgrade
    • Delpha Apps
      • Delpha Setup
        • Delpha configuration
          • First Steps
          • Token Usage
          • Data Quality - Account
          • Data Quality - Contact
          • Duplicates
          • Job Tracker
          • Default Values
        • Conversations
        • Conversation Builder
          • High-level overview of the conversation builder
      • Delpha Data Quality
        • Data Quality Steward view
        • Duplicate Data Steward view
      • Delpha Score Meter
    • Use Cases Setup
      • Duplicate
        • Setup
          • Initialize the default settings
          • Activate Auto Merge
        • Duplicate detection
          • Properties section
          • Fields section
        • Run your first duplicate detection
        • Duplicate Merge
          • Merge Object Rules section
            • Master Record Selection
            • Custom rule for Master Record selection
            • Default rules for field selection
          • Merge Field Rules section
      • Data Quality
  • Delpha Campaigns
    • Create a Delpha Campaign
    • Configure a Delpha Campaign
      • Select the Campaign Type
        • Lead Generation
        • Job Tracking
        • Account Generation
      • Review and update the Settings
      • Add Campaign Members
  • HOW TO - FAQ
    • Quick Start Guide
    • Delpha Integration
      • How to add Delpha components in my standard layout
      • How can I add Delpha fields in my standard layout
      • How to manage conversation priority
      • How to manage the conversation auto opening
    • Delpha Job Tracking
      • How to display the Job History
      • How does job tracking works
    • Delpha LinkedIn Connector
      • How can I connect my LinkedIn Account to Delpha
      • I am not allowed to install Delpha Connector on my browser
      • How many records can be enriched with LinkedIn in a day per user?
      • How can I check if a LinkedIn cookie is properly set or valid
      • How is used my LinkedIn Cookie
      • How can I automate my lead generation
    • Delpha Duplicate
      • What is a Filtering Rule and how to use it
      • What is the Expression and how to use it
      • How to exclude records from the analysis
      • How to make Duplicate Records exclusion dynamic
      • How to Fix Duplicates in Salesforce with Delpha – Automatic, Bulk & Manual Options
      • How to modify the detection threshold
      • How to modify the auto process threshold
      • What algorithms are used by Delpha
      • How does the Duplicate scoring work
      • How to define a Golden Record for Duplicate
      • How do you differentiate Do Not Compare & Is Golden Record
      • How to sync Salesforce & Hubspot to deduplicate records
      • Duplicate detection - When does it happen?
      • How to set the frequency of the Auto Merge
      • How to create a Master selection custom rule
      • How to create a Master selection custom rule - Advanced
      • What are the duplicate status?
      • How to Merge 2 leads with different currencies
      • What is a Duplicate credit?
      • Do I consume a credit when merging a pair?
      • What is field grouping?
      • How can I hide a field from the Delpha Bot conversation?
      • How can I keep both values of a field after the merge
      • Some duplicate are not detected, what can I do?
      • Can I ignore some field values when detecting duplicates?
      • What data is available for Duplicate?
      • How can I create custom reports on Duplicate
    • Delpha Data quality
      • What are the 6 data quality dimensions
      • How to exclude records from the analysis
      • How to fix my data quality
      • What is a Token?
      • Do I consume a token when applying a Delpha recommendation?
      • What are the Data Quality dimensions for Contact Name
      • How Contact Name Normalization works?
      • What are Data Quality Dimensions for Contact Email
      • What are the Data Quality fields for Contact Email
      • What are the Data Quality dimensions for Address
  • Delpha Campaigns
    • How to add records to a campaign from reports?
  • TROUBLESHOOT
    • Grant access for Delpha Support
    • Error when connecting to Delpha
Powered by GitBook
On this page
  • Completeness
  • Validity
  • Consistency
  • Address Normalization
  • Accuracy & Recommended address
  • Accuracy status

Was this helpful?

Export as PDF
  1. HOW TO - FAQ
  2. Delpha Data quality

What are the Data Quality dimensions for Address

PreviousWhat are the Data Quality fields for Contact EmailNextDelpha Campaigns

Last updated 10 hours ago

Was this helpful?

Address analysis applies on the standard fields:

  • Contact.MaillingAddress

  • Account.BillingAddress

  • Account.ShippingAddress

Completeness

All required fields—street, city, postal_code, country—must be present and non-empty. For certain countries (France, Japan, Germany, United Kingdom, United States), the state field is also required.

If any required field is missing or empty, completeness is 0; otherwise, 1.

Examples:

  • Input: street=1 rue du Louvre, city=Paris, postal_code=75001, country=France, state=Île-de-France → Completeness = 1

  • Input: street=123 Main St, city=New York, postal_code=10001, country=USA , state= (missing) → Completeness = 0

Validity

Validity determines if the matches a real-world address with high confidence and completeness.

How validity is computed:

  • If there is no normalized match from the geocoding analysis, validity is 0.

  • If a match exists:

    Check Validity: The following conditions must all be true for validity to be 1:

    • The normalized address and the geocoded match are not different

    • The geocoding match's score is above the threshold (0.75 by default).

    • The match is complete and mapped: all required fields (street_number, street, postal_code, country, city, and for some countries, state) are present in both the input and the match.

    If any of these conditions fail, validity is 0.

Consistency

Consistency checks if, for each required field (street, city, postal code, state, country), the original and normalized values are equal after strong normalization (removing accents, punctuation, and lowercasing). If any required field differs after strong normalization, consistency is 0; otherwise, 1.

Examples:

  • Original: paris fRance, Normalized: Paris France → Consistency = 1

  • Original: Paris, Normalized: Lyon → Consistency = 0

Address Normalization

The normalization cleans and standardizes the input fields.

Each address field is normalized using specialized logic:

  • Street:

    • Cleaned and standardized for casing and accents, with particles compressed to their preferred short form (e.g., 'avenue' → 'Av', 'boulevard' → 'Bd', 'de', 'du', 'la', etc. replaced with a standard, often shorter, form for consistency).

    • Examples:

      • Input: rue du Louvre → Normalized: Rue du Louvre

      • Input: Avenue de l'Opéra → Normalized: Av de l'Opera

      • Input: 43-45 boulevard Saint-Germain → Normalized: 43-45 Bd Saint-Germain

  • City/State:

    • Normalized for casing, accents, and removes unwanted punctuation (commas, parentheses).

    • Examples:

      • Input: paris → Normalized: Paris

      • Input: saint-denis (île-de-france) → Normalized: Saint-Denis Ile-De-France

  • Postal Code:

    • Uppercased and cleaned, keeps special characters.

    • Example:

      • Input: 75001 → Normalized: 75001

      • Input: sw1a 1aa → Normalized: SW1A 1AA

  • Country:

    • Normalized for casing, accents, and known aliases using a geo database. Title-cased for presentation.

    • Examples:

      • Input: france → Normalized: France

      • Input: deutschland → Normalized: Germany

  • Country Code:

    • Uppercased, removes special characters, converts non-ASCII.

    • Example:

      • Input: fr → Normalized: FR

      • Input: de → Normalized: DE

Accuracy & Recommended address

How recommendations are generated:

  • If there is no normalized match, no recommendations are returned and accuracy is set to -1.

  • If a match exists:

    1. The geocoded match is used as the recommendation.

    2. If the normalized input street (after strong normalization) contains the geocoded match's street, the match's street is replaced with the input's street (to preserve original formatting).

    3. The accuracy is computed as:

      • accuracy = geocoding_score * completeness_of_recommendation

    4. f the computed accuracy is greater than 0.5, the recommendation is returned; otherwise, no recommendation is returned and accuracy is set to 0.

Accuracy status

How the status is assigned:

  • If accuracy is -1 : label is "Unknown".

  • If accuracy is below the threshold (0.75 by default): label is "No".

  • If accuracy is greater than or equal to the threshold: label is "Ok".

normalized address