> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zwiron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Match overview

> Configure, run, and review Match projects to resolve duplicate records and produce golden records in Zwiron.

Match in Zwiron lets you configure, execute, and review entity-resolution work against a table on a connected source. A Match **project** defines how records are blocked and compared. A **run** executes that configuration and produces candidate **groups**. Stewards review those groups, approve or reject them, and—when ready—write **golden records** back to a destination.

<Note>
  Match projects are not the same as sync Jobs under **Data → Jobs**. Sync Jobs move data between connections. Match projects resolve duplicate entities on a table. Use the correct surface for each task.
</Note>

Match is designed to identify true matches while limiting false matches in incomplete or inconsistent data. Blocking keys keep the volume of comparisons practical. Compare fields and scoring decide which pairs within a block warrant steward attention. Thresholds and auto-approve settings influence how aggressively candidates are suggested—but review remains available so humans confirm outcomes before write-back.

The following articles help you use Match end to end:

* [Match projects](/match/projects) — create, edit, import, export, run, and delete projects
* [Match advanced settings](/match/advanced-settings) — blocking mode, scoring, overlap, lookup, write-back targets
* [Reviewing Match results](/match/review) — steward groups on the run results hub
* [Golden records and write-back](/match/write-back) — survivorship and **Write back approved**

***

## Where Match sits in Zwiron

| Area | Role relative to Match |
| - | - |
| **Connections** | Provide the table Match reads (and optionally the write-back destination) |
| **Catalog** | Optional asset link on a project enables lineage and Trust follow-up after write-back |
| **Data Quality / Trust** | Uniqueness or duplicate failures often motivate opening a Match project |
| **Agents** | When the project uses Agent execution, Match compute runs inside your network |

Typical sequence:

1. Connect and, where needed, profile the source so the table is known.
2. Create a Match project (**Match → Projects → New project**).
3. Run the project (**Run** / **Full run**, or **Delta** / **Run delta** when lookup is configured).
4. Review groups from **Match → Review** or the run results hub.
5. Click **Write back approved** when golden rows are ready.

***

## Core terms

| Term | Definition |
| - | - |
| **Project** | Named configuration: connection, table, blocking keys, compare fields, scoring, survivorship, optional overlap table, optional write-back destination |
| **Run** | One execution of a project. Status and counts (groups, pending, unmatched) appear on the project and on the run hub |
| **Group** | A cluster of candidate matching records produced by a run |
| **Member** | An individual source row inside a group, with field values and scores |
| **Blocking keys** | Columns used to partition records before pairwise compare |
| **Compare fields** | Columns scored within a block |
| **Golden record** | Survivorship result for an approved group |
| **Write-back** | Upsert of golden rows via **Write back approved**; may record Catalog lineage and trigger Trust re-detect when an asset is linked |

***

## Navigation

| Task | In the app |
| - | - |
| List and run projects | **Match → Projects** |
| Create a project | **Match → Projects → New project** |
| Cross-project review cards | **Match → Review** |
| Inspect one run | Open a project → open a run, or land on `/match/runs/…` after **Run** / **Delta** |

Sidebar labels under **Match** are **Projects** and **Review**.

***

## Related articles

* [Match projects](/match/projects)
* [Match advanced settings](/match/advanced-settings)
* [Reviewing Match results](/match/review)
* [Golden records and write-back](/match/write-back)
* [Connections](/concepts/connections)
* [Hosted vs Agent](/guides/hosted-vs-agent)
* [Data Quality](/platform/data-quality)
* [Trust overview](/trust/overview)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.