FAQ for Reltio Enrichment with D&B Data Blocks
Answers to common questions about configuration, enrichment modes, troubleshooting, and performance benchmarks for D&B Data Blocks integration.
Do I need a license to use D&B enrichment?
Yes. D&B Data Blocks enrichment requires a license. Contact your Reltio Customer Success Manager to confirm entitlements and activation steps.
Which enrichment modes are available?
The integration supports these modes:
- Batch: Scheduled or API-triggered jobs
- Monitoring: Triggered by DUNS change events
- Real-time: Triggered by profile changes or unmerge events
- On-demand: User-triggered via UI buttons
- Recertification: Removes stale enrichment and reprocesses profiles
What modes of enrichment should I use?
It is recommended to use Batch Mode at least one time during your Reltio implementation lifecycle. Typically this occurs after the initial data load and consolidation/mastering. The batch mode supports enrichment of profiles in bulk and has a configurable filter condition which allows you to enrich the superset or some subset of data.
After the initial Batch enrichment is complete, you may choose to adopt Monitoring and monitor the superset or subset of data. You’ll receive these ‘push’ updates from D&B with no further action required on your end.
Alternatively, you may choose to adopt Real-Time (continuous) enrichment instead. It is recommended to use a dedicated SQS streaming destination for this purpose. It is recommended to set Type filter and Object filter for these events to suit your business requirements and reduce the amount of processing and RIH tasks invoked.
For example, set Type filter to ENTITY_CREATED, ENTITY_CHANGED and Object filter to (equals(type,'configuration/entityTypes/Organization') and (not equals(sourceSystems,'DnB'))).
Why isn’t my record being enriched?
Enrichment can be skipped in the following scenarios:
- The record already contains a D&B crosswalk but does not meet confidence code thresholds.
- Monitoring skipped the record because the crosswalk is not marked as
ov=true. - The record was previously enriched using
doNotMerge=trueand is excluded by filters.
How can I re-enrich a record?
Use recertification mode to remove outdated crosswalks and trigger new enrichment. You can also manually remove D&B crosswalks and run enrichment again. See Use recertification mode on D&B Data Blocks.
Why are monitoring registrations being skipped?
Registrations are skipped when:
- The DUNS number is already registered in the master file.
- The number exceeds the Monitoring Registration Limit.
Why is hierarchy enrichment skipped for duplicates?
Only one record per DUNS is enriched with hierarchy and contacts. Duplicate profiles will only receive company info. The system logs why hierarchy is skipped in the Data Provider Verification Details field.
How do I start or stop enrichment modes?
Enable or disable the following trigger recipes in Integration Hub:
- Real-Time: D&B | TRG-SQS | Real Time Enrichment
- Batch: D&B | TRG | Scheduler for Batch Enrichment
- Monitoring: D&B | TRG | Monitoring Trigger Recipe
- Recertification: D&B | TRG | Scheduler for Recertification
Can I trigger enrichment externally?
Yes. You can use API tokens and REST API endpoints exposed through the API Platform. For examples, see Operate Reltio Enrichment with D&B Data Blocks.
Can I customize the enrichment logic?
Yes. You can add new Data Blocks or modify mapping logic. For instructions, see Customize or add new Data Blocks.
What modes of enrichment support re-enrichment of records?
Re-enrichment will work only for On-Demand Enrichment via Rest API and Monitoring (For Monitoring, doNotMerge flag won’t be considered).
For records already containing enrichment D&B crosswalks like URI:DUNS that need to be enriched, if the job ran with doNotMerge flag as true, the recipe will not process this record and an error message is thrown in the D&B Logs table. If the job ran with doNotMerge flag as false with the Confidence Code less than Auto Merge – Confidence Code, the recipe will not process this record and an error message is thrown in the D&B Logs table.
In this case, if we must force re-enrichment of records, then the Data Provider Verification Status value attribute should be deleted/removed for specific enriched records from Reltio. Then, if a Batch job is run and part of the filter criteria, it will re-enrich those records.
Why can’t I see the On-Demand buttons?
Ensure you have ROLE_DNB_CONNECTOR assigned to you and the On-Demand configuration was performed.
You’ll need a Reltio support ticket to create the RIH profile that is used by the UI configuration.
Where can I see D&B Integration recipe task counts?
You can view the recipes task count in the Dashboard menu in RIH. Specify filters to view relevant details, as shown in the screenshot below:
Where can I find job status and logs?
See topic Operate Reltio Enrichment with D&B Data Blocks for in depth information.
How do I configure a particular mode of enrichment?
See topic Mode-specific configuration for Reltio Enrichment with D&B Data Blocks for more information on how to configure each mode
Can I use an external application to trigger or schedule batch and/or on-demand enrichment for data in my Reltio tenant?
Yes. Enable Batch or Real-Time APIs and their corresponding triggers. Create an authorization token for these APIs and begin making requests to these endpoints.
For more details, see topic Configure Reltio Enrichment with D&B Data Blocks
Can I modify recipes?
Yes. If you are adding new Data Blocks, see topic Customize or add new Data Blocks.
Reltio cannot provide support for customizations.
Where are the rest of my logs?
RIH has limitations of 10,000 entries per Lookup table. If the D&B Job Execution Statistics or D&B Logs lookup table reaches 9,900 entries, the last 1,000 old entries will be deleted from these lookup tables (Step 19, Step 23). Other Lookup tables will be truncated while starting any new job. For more details, see topic Operate Reltio Enrichment with D&B Data Blocks
What happens to logs for Jobs that are terminated or stopped abruptly?
You cannot view logs and stats for a job that is either terminated or stopped abruptly.
Why aren't principal contacts being added?
To enrich a record with the Principal Contacts datablock, ensure one of the 3 datablocks, i.e. Company Info, Hierarchy connections, or Diversity Insights, is mandatory.
If the Principal contact and Hierarchy datablocks are available, and hierarchy is not available for the record from D&B, then the Hierarchy is unavailable for these records hence Principal contacts won't be created error message is logged. If all datablocks are present and the hierarchy is not available for the record, the principal contacts are populated for the record along with the company details.
Can I match multiple profiles to the same Organization (DUNS Number)?
Yes, you can but with some limitations on hierarchy and contacts.
Let us assume there are 2 duplicate records in Reltio. The first one is already enriched and contains crosswalks such as URI:DUNS, Standalone DUNS. The other record that must be enriched will also get same DUNS Number. To avoid merging 2 duplicate records based on Standalone DUNS crosswalks, only URI:DUNS crosswalk will be created for the duplicate record.
If Hierarchy and Principal Contacts is available, it will be skipped for the duplicate record. In other words, only the first enriched record will contain these details.
How can I enrich Shell Records (created for Hierarchy)?
The recipes won’t allow the enrichment of Parent records via Real-Time and Batch. These records will be ignored and captured under logs for Batch Process.
Shell Records can be enriched using On-Demand or when subscribed to Monitoring. Contact your D&B Representative for more information regarding monitoring.
How does Monitoring work?
The Monitoring feature provides the ability to receive updates and changes to specific registered DUNS Numbers via D&B notification service.
Reltio supports Monitoring via D&B FULL_PRODUCT notification type. This ensures that full data payloads for each DUNS Number are included in the monitoring files, enabling complete downstream enrichment.
To create a Monitoring registration, customers should work with their Dun & Bradstreet Representative to have registrations created or raise support ticket with https://support.dnb.com:
To begin using Monitoring, customers must first register for the service through their D&B Representative. For details, see Monitoring registration strategies in D&B Data Blocks.
Reltio processes the following DUNS status types:
- SEED: Updates Company Info and Diversity Insights (using URI:DUNS) and enriches Hierarchy and Principal Contacts (using DUNS crosswalk).
- TRANSFER: Soft-deletes old crosswalks, appends new D&B crosswalks based on the retained DUNS, and logs transfer details.
- DELETE: Soft-deletes all associated D&B crosswalks.
- UNDELETE: Removes deleteDate from previously soft-deleted D&B crosswalks.
Other DUNS status types are ignored and captured in the D&B Logs lookup table.
Monitoring only processes records if the appropriate crosswalks (URI:DUNS and/or DUNS) are present and marked as ov: true.
If a DUNS number appears in an EXCEPTION file, it will be logged in the D&B Logs lookup table with an error message.
How can I deploy the D&B Data Blocks integration into my tenant?
After obtaining the necessary entitlements, contact Reltio Support to have the deployment done for a given tenant. See topic Get help in Support Portal.
Why do we have different crosswalk formats?
Different crosswalk formats are used to address various data integration scenarios. The following table describes the crosswalk sources, values, and verification details:
| Object Type | Crosswalk Values | Record Type | Description | Verification Status/Details |
|---|---|---|---|---|
| Entity |
URI:DUNS DUNS | Auto Merged Record | If Merge records by DUNS crosswalks property is “No”, URI:DUNS - is used for populating Company info details. URI in the crosswalk ensures all records can be enriched to avoid unique DUNS dependency. Also solves the infamous/painful "URI miss match" issue of past connector.Standalone DUNS crosswalk- is used for creating Hierarchy and Contacts relationships. Standalone DUNS crosswalk will be populated only for one Auto merge record. If Merge records by DUNS crosswalks property is “Yes”, DUNS crosswalk is used for populating Company info details and creating Hierarchy and Contacts relationships. | Enriched by D&B |
| DnB/URI | Source Record | In case of No Match Found, Potential Match and any error from D&B, we will create this crosswalk in original record. Later, if the record is enriched successfully then this crosswalk will be soft deleted. | No Match Found by Dun & Bradstreet, Potential Match Found by Dun & Bradstreet, Error occurred in Dun & Bradstreet job | |
|
URI:DUNS DUNS | Potential Match Record | For Source records, this record will be created as a Potential Match record, if confidence code is between Auto Merge – Confidence Code and Potential Match – Confidence Code. | Enriched - Potential Match by D&B | |
| URI:DUNS | Duplicate Record | For duplicate records when we try to enrich, only Company info details will be populated from this crosswalk. Standalone DUNS crosswalks will not be created, and we will get the Verification Details message. | Data Provider Verification Details - Hierarchy and Principal Contact is unavailable for this duplicate entity. Resolve merge with Entity ID | |
| DUNS+MSP+GIVEN NAME | Principal Contacts | If a contact is created while enrichment, then we’ll create crosswalk in this pattern for that contact record.DUNS - Associated to Organization, MSP – Most Senior Principals abbreviation is used in crosswalk.GIVEN NAME – Associated to Principal Contacts | NA | |
| DUNS | Standalone DUNS Crosswalk/Parent | This crosswalk is used to create Hierarchy and Principal Contact Relationships. In case of Hierarchy enrichment, if the Parent DUNS is not already present in Reltio, then we will create shell records with that Parent DUNS as a crosswalk. This shell record contains Name, Address, DUNS Number in attribute level. |
Shell Organization - Created as Part of the Dun & Bradstreet Hierarchy Note: Only for Shell Records
| |
| Relation | DUNS:DUNS | Organization – Organization | Parent DUNS:Child DUNS | NA |
| DUNS:DUNS+MSP+GIVEN NAME | Organization – Individual | DUNS:Contact Crosswalk | NA | |
| AddressType:URI|DUNS | Organization – Location | Example - Shipping:URI|DUNS | NA |
Do you have any Performance Benchmarks
These benchmarks reflect test results from standard tenant runs. Results may vary depending on recipe customization, data volume, or external API latency.
| Mode | Merge records by DUNS Crosswalks | Record Count | Typical Duration |
|---|---|---|---|
| On-Demand: Get Match | Yes | 1 | 7 sec |
| On-Demand: Get Company Details | Yes | 1 | 5 sec |
| On-Demand: Get Company Hierarchy and Contacts | Yes | 1 | 5 sec |
| Real-Time | Yes | 1 | 5 sec |
| Batch | Yes | 100K | 32 min |
| Batch | Yes | 50K | 16 min |
| Batch | Yes | 10K | 3 min |
| On-Demand: Get Match | No | 1 | 7 sec |
| On-Demand: Get Company Details | No | 1 | 5 sec |
| On-Demand: Get Company Hierarchy and Contacts | No | 1 | 5 sec |
| Real-Time | No | 1 | 5 sec |
| Batch | No | 100K | 47 min |
| Batch | No | 50K | 23 min |
| Batch | No | 10K | 4 min |
| Monitoring Registration | No | 100K | 20 min |
If you customize the recipes, retry logic, or transformation steps, your actual job duration may vary.
Can I use Hierarchy & Connections Data Block without creating the organization profiles and relationships in Reltio?
This is not a supported use-case out-of-the-box, although recipes can be customized to modify the functionality.
Using Monitoring, what happens to the data in Reltio when an organization's DUNS number changes?
For monitoring, D&B sends a Transfer status instead of Seed. Based on the status, the integration will soft delete the old DUNS and append new DUNS crosswalks to the same profile.
To receive further updates, the new DUNS number will need to be added to the monitoring registration.