Unified Scores table

The Unified Scores table records all pairwise comparison scores and match categories for all groups of records. For each group of records, records all pairwise scores that are present between records within that group.

The Unified Scores table is added to databases in the Customer 360 page when:

  1. The Stitch QA database is added using the “Stitch QA” database template.

  2. A customer 360 database is added using the “Customer 360” database template.

  3. A table is added to a custom database using the Unified Scores table as a passthrough table.

Use with Stitch QA

The Unified Scores table is the foundation for the Detailed Examples table in the Stitch QA database, which is the starting point for any quality review of Stitch output and is an important part of the Stitch QA workflow.

Use with Customer 360

The Unified Scores table enables using the Amperity ID to discover information about how groups of records were scored and to verify those scores against other data points.

Important

The Unified Scores table should not be used outside of the Customer 360 page. It should not be used to build queries or segments or be configured to send data to downstream workflows.

Column reference

The Unified Scores table contains the following columns:

Column Name

Data type

PII

Description

Amperity ID

String

The unique identifier assigned to clusters of customer profiles that all represent the same individual. The Amperity ID does not replace primary, foreign, or other unique customer keys, but exists alongside them within unified profiles.

Note

The Amperity ID is a universally unique identifier (UUID) that is 36 characters spread across five groups separated by hyphens: 8-4-4-4-12.

For example:

123e4567-e89b-12d3-a456-426614174000

Source1

String

Source2

String

PK1

String

PK2

String

Score

Float

A score has a value from “0.0” to “5.0” that represents the combined score assigned to the record pair by Stitch. A score has two parts: the score is on the left side and the score’s strength is on the right.

The record pair score correlates to the match category, which is a classifier applied by Amperity to individual record pairs. The record pair score corresponds to the classification:

  • 5 for exact matches

  • 4 for excellent matches

  • 3 for high matches

  • 2 for moderate matches

  • 1 for weak matches

  • 0 for no matches

The record pair strength represents the strength of the record pair score. It is a two digit number. For example: .31 is a lower strength and .93 is a higher strength.

Note

Scores are shown for records that end up in the same cluster, including any scores that are below threshold. Scores are not shown for records that do not end up in the same cluster.

Also in: Detailed Examples

Match Category

String

A match category is a classifier that applies to an individual record-pair within a cluster of record-pairs. The match category is the result of this classification.

Match Category

Description

Exact

Amperity has the highest confidence that these records represent the same person because all profile data exactly matches.

Excellent

Amperity has near perfect confidence that these records belong to the same person, despite select types of profile data not matching.

High

Using deductive reasoning, Amperity has high confidence that these records match, despite some profile data not matching.

Moderate

Amperity has moderate confidence that these records match, due to weak or fuzzy matches between unique customer attributes, such as email, phone, or address.

Weak

Amperity lacks confidence, but if asked to guess, Amperity would assert these records do belong to the same individual, because they match on non-unique customer attributes, such as name, state, zip code.

Non-match

Amperity has high confidence that these records do NOT match, because core profile data is in conflict.

Also in: Detailed Examples

Match Type

String

The score. Possible values: “scored”, “scored_transitive”, and “trivial_duplicate”. Records assigned a “scored” value are directly connected. Records assigned a “scored_transitive” value are transitively connected.

A match is assigned “scored_transitive” when that match was not identified during blocking. For example: three records (A, B, and C). If records A and B and records B and C were identified as matching during blocking, all three records will end up in the same group of records for pairwise comparison. Records A and C have a transitive connection.