DUNS Match Insight

This insight is available for the following templates: Company Mastering with D&B and Supplier Mastering with D&B. Run your flow to populate metrics.

How has my DUNS Match improved overall?

In the following example, you can see:

• Before running the flow, <1% of source records had a DUNS match.
• 28% of source records were matched with high confidence to a DUNS number in the DUNS Match step.
• After clustering, 69% of companies were grouped into clusters with an identified DUNS match.

How about in the last run?

Shows you how many DUNS matches were added, and how many DUNS matches were updated in the last flow run. The Unique DUNS Added count is of the number of unique DUNS numbers that were added, while the DUNS matches updated is the number of mastered entities that had their DUNS match changed from one non-null DUNS number to another non-null DUNS number.

Why do I have companies without a DUNS Match?

There wasn’t enough information to enrich or find a DUNS match for some of your mastered entities. In the following example, you can see there are 399 mastered entities with no DUNS match.

What is the confidence of the DUNS Match in my source records?

See the distribution of records at certain confidence codes. On the left side, you see the number of records with low confidence codes. On the right side is the number of records with high confidence codes.

In the following example:

• 1.19K source records have no DUNS match.
• 2.13K source records have a low confidence code of 7.
• 657 source records and 44 mastered entities have a high confidence code of 8.
• 1.4K source records and 814 mastered entities have a high confidence code of 10.