Found, Enriched, Connections and Match Accuracy

After you run a search, the results screen carries three header counters that describe the results in three different ways: Found, Enriched and Connections. This page explains what each counter counts, how the same three ideas reappear as per-row flags in the results table, and what Match Accuracy means. These are distinct quantities, so keep the words distinct: never use one in place of another.

Results screen, Search 3000+ sites Module, three counters and results table

The three counters

Every populated results header carries the same trio of counters, in this order: Found, Enriched, Connections. They count three different things. The counter trio stays in the header across module types, even though the results table columns below change from one Module to another.

The counters are colour coded: Found renders green, Enriched orange, Connections white.

Counter	What it counts
Found	Accounts located on a site (a matching profile exists there)
Enriched	Found accounts on which UserSearch holds extra metadata
Connections	Links drawn between entities across results

Found

Found means the identifier was located on a site — a matching profile for the value you searched exists on that site or data source (per Lee, 2026-07-08).

Two observed examples show how the count is presented per Module:

• Search 3000+ sites Module: the header read Found 207, with a sub-header “207 found / 161 not found”. This Module reports both halves; the Found counter reflects only the found subset, and the complementary 161 are checked sites with no match.
• OneScan Module: the header read Found 546, with the status line “Success. Found 546 results”. This Module surfaces no separate not-found count.

Enriched

Enriched means UserSearch holds further metadata on a found account — for example possible names, linked emails, and similar profile-level data attached to that account (per Lee, 2026-07-08). Because only a found account can be enriched, Enriched is always a subset of Found.

• Search 3000+ sites Module: Enriched 18 of 207 found.
• OneScan Module: Enriched 545 of 546 found.

Enrichment coverage depends on the Module and data source. In the observed runs nearly every OneScan hit was enriched (545 of 546), against only 18 of 207 for the single-site sweep.

Note

What enrichment delivers in practice is the populated INFORMATION detail block for a found account — profile-level metadata such as account creation date, follower and photo counts, an avatar link, and a canonical user id. That this block is the concrete face of enrichment is inferred from the observed data rather than stated by the product.

Connections

Connections counts relationships surfaced between entities — clusters of linked accounts rather than raw site hits. These are intended to populate the Graph tab in the Details panel.

• Search 3000+ sites Module: Connections 15.
• OneScan Module: Connections 0 — the connections count can be zero even on a large result set (546 found).

Caution

A populated Connections graph has not yet been captured, so its rendered appearance is not confirmed. In both observed result states the connections detail area read “No connections found” — including one case where the counter showed 15 but the detail section was empty. Treat the Connections counter as a count only; do not assume a populated graph until it is verified.

Tip

Memorise the distinction. Found = how many accounts you located. Enriched = how many of those you hold extra metadata on. Connections = how many links were drawn between entities. Different quantities — never substitute one word for another.

The same ideas as per-row flags

Below the counters, the results table repeats Enriched and Connection as per-row flags, so you can see which specific results carry them. The columns adapt to the Module that produced the results.

Results screen, OneScan Module, all rows enriched

In the Search 3000+ sites Module the table showed BOOKMARK · SITE · ENRICHED · CONNECTION · PROFILE URL. The ENRICHED and CONNECTION cells are per-row boolean flags — a check when positive, a red X when negative — and they are independent of each other. In the observed rows some sites showed a check in both, one showed an ENRICHED check but a CONNECTION X, and others showed X in both.

In the OneScan Module the table showed BOOKMARK · ENRICHED · FOUND ON · DATA SOURCE, with no CONNECTION column. Every visible ENRICHED cell was a check, consistent with the Enriched 545 / Found 546 counters. The DATA SOURCE column names the third-party data source behind each hit — observed values were “OSINT Industries” and “Predicta Search”.

Note

The per-row ENRICHED flag and the Enriched counter describe the same idea at different scales: the counter totals the rows whose flag is a check.

Match Accuracy

Match Accuracy appears as a column in the CONNECTIONS detail table, alongside INFORMATION IN COMMON and SITES.

Match Accuracy is set by the third-party data source, not computed by UserSearch (per Lee, 2026-07-08).

Caution

No populated Match Accuracy value has been captured. In every observed state the CONNECTIONS table read “No connections found”, so how the value is displayed — as a percentage, a band, or a label — is not yet confirmed. This page describes the concept, not the display format.

Where these appear in the Details panel

When you select a result, the Details panel below shows structured detail for it, including connection-oriented sections that use the same vocabulary:

• ALL CONNECTIONS — grouped by the matched value, listing the SITES that share it. In one observed result the values fred and Fred formed separate clusters, showing that grouping is case-sensitive (inferred from the observed rows).
• CONNECTIONS — the table that adds the MATCH ACCURACY column described above.
• INFORMATION and INFORMATION (CONTINUED) — the enrichment metadata for a found account (for example platform, username, user id, creation date, follower and photo counts).

Note

The CONNECTIONS section and the Connections header counter can disagree in a captured state — the counter showed 15 while the section read “No connections found”. Why is not yet explained, so rely on the section contents you can see rather than the counter alone.

Verified against UserSearch v2.0.20