Matching
Graph Connections
Graph Connections is entity and graph matching: customer records on one side, the FactGraph on the other. It is the general form of the comparison Obituary Match uses for deaths.
What it does
Record to entity
You provide the fields needed for a comparison, such as name, date of birth, and location. Cloudswift looks for corresponding entities in the FactGraph.
Ordinary variation
Matching has to tolerate nicknames, missing middle names, and uneven addresses. That is part of the work. It is not a published accuracy percentage.
Paths the graph can show
Where the FactGraph has a relationship, we can show how a candidate connects to public data. If the graph does not contain a path, we will not invent one.
Review stays with you
A match is a candidate. Ambiguous names are expected. Your team decides whether a candidate is the person on your file.
Where it is used
Alongside Obituary Match
Death matching is the lead case. The same machinery can compare a record with other public entities in the graph when that is in the agreement.
A file, not a one-off search box
This website does not offer a public search of people. Matching is a commercial workflow on a file you provide.
Then alerts, if included
After an initial match, connection alerts can watch for a new public-data link. Alerts are described on their own page and are not automatic.
Described plainly
- We do not publish an accuracy rate, a latency target, or a maximum path length.
- Name collisions are normal. Treat every result as a candidate.
- Which entity types are in scope is part of the conversation, not a fixed catalog on this site.
Talk with us about Graph Connections
Tell us about the file you want to match. We will say whether it fits and what the agreement needs to cover.