Can we restrict the lookup to name and Address attributes, instead of the order of precedence mentioned in the D&B document (As DS don't trust the DUNS number populating from the Sources)?

Question

We are using the D&B Data blocks connector in Reltio to enrich the data from D&B. Within this process, we informed that the matching of Reltio data with D&B data follows the logic and precedence mentioned the document :

https://directplus.documentation.dnb.com/html/guides/Identify/IdentityResolution.html#precedence-used-for-transactional-and-batch-requests

If we check the document, we will find that the matching is happening based on multiple attributes following a certain precedence order. At first, the connector checks the D&B data based on the DUNS number provided in the Reltio data.

If it finds a match based on DUNS, it enriches the Reltio profile with the information from D&B; otherwise, it checks for matches with the other attribute set mentioned as per the precedence table in the said document. 

The Data stewards have concerns about the DUNS number we are getting from various sources and loading in Reltio. Hence, they want to match only by Name and address. 

Can the D&B data blocks connector be re-configured to implement this match criteria only, as per Data Stewards' recommendation?

Answer

There are two options in this case.

• Not loading the source DUNS numbers with the source data
• Modifying the outbound recipes so they do not transmit the DUNS numbers will impact subsequent attempts to re-enrich the record if D&B monitoring is not used.

 
We recommend option one over option two above. The customer should work with DNB on this request, as it will affect the match rate/confidence levels.