What is it?

The Dun & Bradstreet (D&B) Corporation is an American company that provides commercial data, analytics, and insights for businesses.

The Reltio Enrichment with D&B Data Blocks is a prebuilt integration delivered through the Reltio Integration Hub (RIH). It consists of an RIH package that you can deploy (import) into a tenant using RIH Recipe Lifecycle Management. The imported package includes:

• Recipes
• Connections
• Environment properties
• Lookup tables
• API endpoints
• API collections
• Connector SDKs
• Templates

Why would I use it?

The integration allows you to enrich organization profiles with D&B Data Blocks and is designed to deliver automation, governance, and performance for data enrichment.

Data enrichment with D&B Data Blocks eliminates duplicates, unifies customer, vendor or partner records. It supports business goals by reducing risk, cutting costs enhancing segmentation and accelerating compliance.

When would I use it?

Key benefits

Accelerate time to value with a prebuilt integration for data enrichment with D&B

Leverage the prebuilt integration in Reltio Integration Hub (RIH) to realize several benefits including:

• Built using Reltio and D&B integration best practices
• Built-in error handling
• Access to logs, job statistics, and email notifications for transparency and troubleshooting
• Configurable parameters, including confidence code thresholds for auto-merge vs. suspect match
• Support for “Potential Match only” mode via configuration
• Enrich multiple Reltio profiles that match the same DUNS number
• Unified functionality across all modes of operation: real-time, batch, on-demand, and monitoring
• Ability to add and configure D&B Data Blocks to suit your requirements
• Optimized recipe design and consolidated SDKs for improved performance and maintainability
• Recertification workflows to ensure enriched data stays accurate and current

Bridge gaps in your data with D&B curated “Data Blocks”

The Reltio D&B Data Blocks integration unfolds the latest D&B enrichment technologies in a structured, extensible format.

Enrich profiles across four modes of operation

Use the D&B Data Blocks connector to get trusted, accurate, and current organization data from D&B’s database. Records are matched against D&B using basic firmographic information.

Note:

Profiles are matched using the following Organization input attributes: Name, Address, Email, Phone, Website URL, and Tax ID. The availability and quality of these attributes determine how D&B performs the Identity Resolution.

Supported modes:

1. Real-time (continuous enrichment triggered by ENTITY_CREATED and ENTITY_CHANGED events)
2. Batch (scheduled or invoked manually via API)
3. On-demand (user-initiated via UI buttons)
4. Monitoring (based on change events for registered DUNS numbers)

Create organization hierarchies and contact relationships

Further enrich your organization data using D&B company hierarchies. Build corporate structures and relationships using the Get Company Hierarchy and Contacts button.

Note:

Refresh your screen after clicking the Get Company Hierarchy and Contacts button to see the updated data.

The following image shows the Get Match, Get Latest Company Info, and Get Company Hierarchy and Contacts buttons in the Organization Profile view:

Get match scores to control merge decisions

D&B returns a match score (the Confidence Code) that reflects the quality of the match. This value controls whether a record is auto-merged, flagged for review, or skipped. The confidence thresholds are configurable between 0 and 10.

Automated and ad-hoc monitoring registration

Support both automated monitoring registration using rule-based filters and manual ad-hoc registration by uploading DUNS lists. Registration is tracked through delta logic and enforced by license limits.

Custom merge behavior based on crosswalk format

Use the Merge records by DUNS crosswalks property to control whether records with the same DUNS number are merged. When set to Yes, the legacy behavior is preserved and records with identical DUNS numbers will merge. When set to No, URI:DUNS is used to preserve separate profiles.

Note:

Don’t change this setting without reviewing merge policies. Incorrect values may cause improper merges.