Reports¶
Overview¶
Matchbook Reports offer a comprehensive view of the data processing pipeline, including the input, processing, and output stages. The reports aim to provide a transparent representation of how data moves through the system, highlighting key metrics like unprocessed inputs, low-confidence candidates, unmatched records, and final matched output. These reports enable effective monitoring and management of data stewardship and enrichment activities, as well as tracking API usage.
Reports let users a comprehensive understanding of the data processing queues, data stewardship statistics and API Usage.
Reports navigation¶
There are three primary categories of configurations that need to be reviewed.
Base Report
Investigation Report
Metrics Dashboard
Reports section has been discussed in detail in further section of the document.
Base Report¶
The Base Reports section provides an essential snapshot of data activity within Matchbook. This dashboard offers real-time insight into various stages of the data processing workflow, such as the number of records in the input queue, processed results, and enrichment activities. The Base Reports section allow users to view the metrics and statistical information for three main components:
Data Queue Dashboard
Data Stewardship Statistics
API Usage
The Data Queue Dashboard presents all this information in a clear, chart-based format, providing a visual representation of the different stages in the data processing workflow. This section effectively manages and displays diverse profiles, facilitating easier tracking and monitoring of data status as it progresses through the system. This report encompasses metrics and statistical information across various queues, detailing unprocessed data, data currently being processed, and processed data.
Reports-Data Queue Dashboard¶
Field |
Description |
|---|---|
Unprocessed Input |
This indicates the total number of records that have entered the system but have not yet undergone any processing. |
Queue |
Represents the number of records currently awaiting action in the processing queue (15 in this instance). |
Low Confidence Candidates |
This figure shows the records identified as low confidence, indicating a need for further review and validation (7 records). |
Unmatched Records |
Displays the total number of records that could not be matched with existing profiles, highlighting potential data issues (7 records). |
Number of Records |
Summarizes the overall counts of various data categories, showcasing the flow of records through the system. |
Data Stewardship - Low Confidence Candidates |
Highlights the focus on records flagged for manual review due to their low confidence status, essential for maintaining data quality. |
Data Stewardship - Unmatched Records |
Emphasizes the attention given to unmatched records to identify and resolve discrepancies in the dataset. |
Match Output |
Reinforces the importance of matched records as a key performance indicator of the data processing efficiency. |
Data Enrichment Queue |
Indicates the queue of records that are awaiting data enrichment to enhance the existing profile information. |
Enrichment Output - Company Profile |
Represents the enriched company profiles generated because of the data enrichment process, adding valuable context. |
Enrichment Output - Corporate Linkage |
Displays the enriched corporate linkages established through the data enrichment process, which aids in better understanding relationships. |
Monitoring Registration Queue |
Tracks the records in the registration queue that are pending monitoring, ensuring no data is overlooked. |
Monitoring Notification Output |
Provides insights into notifications generated from monitoring activities, alerting stakeholders to key updates or issues. |
Data Stewardship Statistics provides valuable insights into the efficiency of data matching and user activity. It tracks key metrics such as the number of rows matched by users and user groups, confidence levels in data matches, and auto-acceptance rates. This report helps evaluate the accuracy and performance of data stewardship processes, offering a detailed overview of top matched rows based on user and confidence codes. Additionally, the dashboard highlights total matched rows and user activity, ensuring a clear understanding of the overall data processing workflow.
Reports-Data Stewardship Statistics¶
The API Usage report tracks the number of third-party API calls made to D&B for data enrichment and entity resolution. It tracks the number of API calls by type, detailing both the current month and year counts. The report highlights two key API services: Corporate Identity: On-Demand Single Entity Resolution and Company Profile, Executives with Linkage (CMPELK) V2, showcasing their usage frequency and distribution. This data helps monitor the effectiveness of API integrations, with clear metrics on the total number of calls made monthly and annually, ensuring optimized data enrichment processes across the system.
This report includes metrics and statistical information for:
Current Month Count: Current month count by API type.
Current Year Count: Current year count by DnB API Name.
Total Count: Total count overall.
Reports-API Usage¶
Investigation Report¶
The Investigation Report is a D&B product that allows end users to investigate company data, specifically DUNS numbers, when a business name has changed.
Note
The Investigation Report is only accessible to users with a valid license. To activate it, navigate to the Settings section and go to the D&B. Under the License tab go to Default Keys For UI sub-section, select the appropriate license key from the drop-down menu options under Investigations.
A user can investigate a record through two methods:
Prospecting – Search Data
Low Confidence – No Match
Reports-Investigation Report¶
Field |
Description |
|---|---|
Customer Transaction ID |
A unique identifier assigned to each customer transaction for tracking purposes. |
Source Record ID |
The identifier associated with the original record being investigated. |
Primary Name |
The main name of the business or entity under investigation. |
Primary Address |
The primary location associated with the business or entity being examined. |
DUNS Number |
The unique DUNS identifier assigned to the business for identification in the D&B database. Note: This will only be visible for Targeted investigation. |
Request Type |
The category of investigation being requested, such as Mini or Target Investigation. |
Date |
The date on which the investigation request was made. |
Resolved DUNS |
The DUNS number obtained as a result of the investigation. |
Case Resolution |
The outcome or findings of the investigation process. |
Resolution Date |
The date on which the investigation was completed, and the resolution was provided. |
Status |
The status of the investigation, indicating whether it is Open, Resolved, or Closed |
Details |
Additional information or notes related to the investigation case. |
There are two types of investigations, which can be viewed under the Request type tab.
Mini Investigation
Target Investigation
A Mini Investigation is conducted when the records display the business’s address and name but lack a DUN’S number. In the Data Stewardship section under Low Confidence, click the “+” sign to view the details of any search ID. Select Investigate Record, which opens a new dialog box. After filling in the necessary information, the resolution will provide the DUNS number. The user can also attach documents related to the company for further investigation by D&B to identify the correct entity. The requester will receive an email notification confirming that a Mini Investigation has been processed, along with all case details sent to the provided email address.
Reports-Mini-Investigation¶
Note
Mini Investigations can also be performed from the Data Stewardship section under Low Confidence and No Match Queue.
Bulk investigations can be conducted for multiple records through the Additional Actions drop-down menu. Users can upload a file for the records they wish to investigate, which will then be sent to D&B for processing and investigation.
The tabs related to investigations are accessible from the main Dashboard page by clicking on the Import Process queue icon, where all queue counts will be visible.
A Target Investigation is conducted when the DUNS number is known, enabling users to verify if the business name has changed.
Reports-Target Investigation¶
A Targeted Investigation is conducted when the records display the DUN’S number. In the Data Stewardship section under Low Confidence, click the “+” sign to view the details of any search ID. Select Investigate Record, which opens a new dialog box. Research Sub type allows users to search in a deeper depth basis. Select the Research Sub type from the options available in the drop-down menu. After filling in the necessary information, the resolution click Submit. The user can also attach documents related to the company for further investigation by D&B to identify the correct entity. The requester will receive an email notification confirming that a Mini Investigation has been processed, along with all case details sent to the provided email address.
Note
Target Investigations can also be performed from the Data Stewardship section under No Match Queue. Additionally, investigations can be conducted for multiple records via the Additional Actions drop-down menu.
The tabs related to investigations are accessible from the main Dashboard page by clicking on the Import Process queue icon, where all queue counts will be visible.
A user can investigate a record through two methods:
Prospecting – Search Data
Low Confidence – No Match
Metrics Dashboard¶
The Steward Metrics Dashboard, embedded in Power BI, provides a detailed overview of data stewardship activities, specifically tracking how many reports are accepted, rejected, or categorized under other actions. The Steward Act section displays the record count and total actions performed by stewards, helping to assess data management efficiency. Key metrics include:
Accepted Reports: Total number of records accepted by stewards.
Rejected Reports: Number of records rejected during the review process.
Other Actions: Additional actions taken on records that don’t fall under acceptance or rejection.
The dashboard also tracks these actions by date and provides a breakdown of stewardship activities across different time periods, helping to monitor performance and decision trends over time.
Reports-Metrics Dashboard¶
Stewards Metrics¶
The Steward Metrics report tracks the performance and actions taken by data stewards in managing data quality and governance. It provides an overview of the decisions made during data processing, categorized by action type and time frame.
Reports-Metrics Dashboard¶
Key components include:
Steward Actions: This section lists the actions taken by stewards, such as Rejected records or other decisions regarding data integrity.
Summarized Decision: A consolidated view of decisions made by stewards across different categories, giving insight into the outcomes of data processing efforts.
Total Actions by Steward: The total number of actions taken by each steward is captured, helping to measure individual contribution to the process.
Steward Action Totals by Date: Actions are also grouped by date, providing a time-based view of stewardship activities, helping track progress over specific periods.
Filters: There are 7 filters available, allowing for detailed analysis using parameters like Relative Dates, covering periods such as Last Years (e.g., 10/18/2022 - 10/17/2024).
Tags & File Name: This section allows tracking specific data files based on their name and associated tags for more granular reporting.
The Steward Metrics report is essential for understanding how stewards manage data and the overall effectiveness of data quality processes.
Import File Metrics¶
The Import File Metrics report provides a detailed overview of the data records processed during file imports, including matching results and the status of each record. This system evaluates each record based on its unique Source Record ID, such as DUNS Number or other identifiers, and processes them into relevant output queues.
Reports-Import File Metrics¶
Key metrics include:
Source Record ID: A unique identifier like DUNS Number (e.g., 1257674t) representing the origin of the record.
Match Output Queue: Records that successfully matched with the existing data are assigned to the Match Output Queue. For example, DUNS 001257674 has a corresponding match in this queue.
No Match Queue: Records that did not find a match, indicating potential data discrepancies or the need for further investigation.
Low Confidence Queue: Records with a low-confidence match are stored here, requiring validation for accuracy.
The report also includes the Total Record Count by Queues and the Imported File Record Count, offering a summary of data processed and categorized by match status.
Identity Resolution Metrics¶
The Identity Resolution Metrics report provides insights into the accuracy and efficiency of data matching processes managed by stewards. It focuses on how effectively stewards resolve identity records by examining confidence codes, match grades, and total actions.
Reports-Identity Resolution Metrics¶
Key components include:
Average Accepted Confidence Code by Steward: This metric tracks the average confidence level of records accepted by each steward, reflecting the accuracy of their decisions. For example, a steward like Aruna Varlagadda may have an average accepted confidence code of 9.63.
Total Actions by Steward: This section summarizes the total number of actions, such as matches or rejections, taken by individual stewards during the identity resolution process.
Confidence Code Total Matched: Displays the total number of records successfully matched by each steward based on confidence codes.
Total Match Grade Strings of Matched Records: Provides a breakdown of the match grade strings assigned to records. For instance, AAAAA/REA indicates a high-quality match for certain records.
Total Confidence Codes: A count of the different confidence codes applied across all resolved records, giving insight into the overall data quality.
The Identity Resolution Metrics report helps evaluate the effectiveness of stewards in resolving identities, improving data accuracy, and ensuring that high-confidence matches are achieved.