Match log report

Administrators and data managers can run reports on the match logs that are created from source subscriptions. Match logs can contain many records, so using reports makes it easier to analyze the data to discover the effectiveness of your match rules and data groups. Network provides templates to help you begin your analysis.

Available match logs

New match logs are immediately available to report on but they are purged after three days. Logs that are older than three days can be retrieved for reporting again using the Analyze Match Log button on the source subscription Job Details page.

Loading the log might take up to ten minutes. When the log is loaded, users are automatically redirected to the Reports page.

Run a match log report

To run a report on match logs:

  1. On the Network menu bar, click REPORTS > SQL Query Editor.
  2. In the query window, click Load query from template.
  3. In the Load Query dialog, find the Match Log heading. Four templates are available:
    • Count of ACT, ASK and Unmatched
    • Count of Match Type (Act, ASK) by feature set
    • Count of record pairs per data group
    • Match log attribute comparison
  4. Select a template and click Load.

    The report loads into the query window.

  5. Click Run.

The report runs and the results display in the Results section.

Templates

Review the templates and example results to understand the information that you can view in the report results.

Count of ACT, ASK and Unmatched

Use this template to see a summary of the match jobs available.

Count of Match Type (ACT, ASK) by feature set

This template helps you to analyze your match data by feature set.

When you load the template, the job_id and entity_type parameters must be defined to see results; for example, job_id = '9' AND entity_type = 'HCP'.

Count of record pairs per data group

The helps you to analyze the data groups that you have defined in your match configuration.

When you load the template, the job_id and entity_type parameters must be defined to see results; for example, job_id = '9' AND entity_type = 'HCP'.

Match log attribute comparison

This report compares attributes from the match log.

When you load the template, the job_id, entity_type, and attribute_list parameters must be defined to see results.

In the example results below, the parameters are defined as job_id = '721', entity_type = 'HCO' and attribute_list ='addresses__v.address.line_1__v'. The report results compare addresses between the source and match value.

Analyzing match logs using SQL queries

You can also access data from the following match log tables if you have permissions to use the SQL query editor.

The available match log tables and corresponding attributes are as follows:

export_id
A key assigned to the export file. This key is the same for all rows.
entity_type
The type of entity; for example, HCP.
file_path
The name (including path) of the match log file.
file_size
The size of the match log file.
job_id
The ID of the job that produced the file.

export_id
A key assigned to the export file. This key is the same for all rows.
advice
The status of the match; for example, ACT.
child_object_type
The type of the sub-object; for example, address.
entity_type
The type of entity; for example, HCP.
match_vid__v
A unique ID assigned to each match.
pair_id
A unique ID assigned to each match pair.
rule_name
The rule that produced the match; for example, field match.
entity_id__v
The Network entity ID.
source_id
The ID corresponding to a source field.

export_id
A key assigned to the export file. This key is the same for all rows.
attribute_list
The fields in a match log; for example, address_line_1__v.
match_vid__v
A unique ID assigned to each match.
match_value
The matched value for a field.
pair_id
A unique ID assigned to each match pair.
source_id
The ID corresponding to a source field.
source_value
The source value for a matched field; for example, 123 Main St.

export_id
A key assigned to the export file. This key is the same for all rows.
group_name
The name of the group that produced the match.
match_vid__v
A unique ID assigned to each match.
pair_id
A unique ID assigned to each match pair.
source_id
The ID corresponding to a source field.
status
Indicates whether a data group contributed to the match.

export_id
A key assigned to the export file. This key is the same for all rows.
advice
The status of the match; for example, ACT.
features
The match features used in a pairing.
instance
The Network instance in which the match was found.
match_country
The country for the matched pair.
match_vid__v
A unique ID assigned to each match.
mode
The origin of the match; for example, source deduplication.
pair_id
A unique ID assigned to each match pair.
rule_name
The rule that produced the match; for example, field match.
source_archive_id
The ID of the archived source.
source_country
The country used for the source data.
source_id
The ID corresponding to a source field.
source_type
The type of source data; for example, customer.