Tracking suspect matches

When suspect matches are processed, there are several ways for administrators and data managers to track the changes.


Suspect match details can be analyzed using reports. For more information, see Sample suspect match queries.

To analyze the match analysis log using reports, see Match log report.

Task audit history

Tasks that are generated after a suspect match resolution are automatically assigned to the same data steward that resolved the suspect match task. This makes the task process more efficient by automatically assigning it to the data steward who already has knowledge about the task.

The task assignment is logged in the Task Audit History with the Action Type called AssignTask.

Data lineage

Selecting individual fields to retain on the surviving merge record can change the data lineage for the surviving record.

When data stewards or data managers change the surviving record by picking field values from the suspect match record, a change request is applied to the surviving record. The values from the losing record display as a change_request in the data lineage. This ensures that the selected values are not reverted to the previous values of the surviving record when the surviving record is loaded through a source subscription. A change request is higher than a source system in the source rankings.

If no field values on the surviving record were changed, then no change request is applied.

Revision history

The Revision History for the surviving record will show two record versions if field values are picked from the suspect match record:

  • the update from the merge request
  • the update from the change request

    Field values that were selected from the suspect match record display in the Revision History.