Standard output

The following tables are standard output of Amperity when using guided setup. These tables and the attributes within them are always available to the Segment Editor:

All of the attributes that are available in standard output as a single topic. It is organized alphabetically by table, and then within each table attribues it is organized alphabetically by attribute name.

Customer Profiles

Customer Profiles attributes present a unified view of your customers across all points of engagement, including attributes that cross systems.

The following attributes are available from the Customer Profiles table.

Attributes

Description

Given Name

The first name connected with a customer.

Surname

The last name connected with a customer.

Email

The email address connected with a customer. A customer may have more than one email address.

Phone

The phone number connected with a customer. A customer may have more than one phone number.

Address

The address connected with the location of a customer, such as “123 Main Street”.

City

The city connected with the location of a customer.

State

The state or province connected with the location of a customer.

Postal

The zip code or postal code connected with the location of a customer.

Birthdate

The date of birth connected with a customer.

Gender

The gender connected with a customer.

Identity Graph

The Identity Graph table compiles rows in the Unified Coalesced table into a graph that maps each data source, along with the primary key for that data source and any customer keys, to the Amperity ID.

The Identity Graph table contains the following columns:

Column Name

Data type

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

Datasource

String

The name of the source data table.

Customer Key

String

The primary key and all customer keys from a data source coalesced into a single value.

Merged Customers

Merged customer attributes represent your unique customers across all of the data sources that you provided to Amperity. These attributes group customer profile data–names, email addresses, phone numbers, physical addresses–based on how it was discovered from across all of the data sources that were provided to your tenant.

The following attributes are available from the Merged Customers table.

Attributes

Description

Address

The address connected with the location of a customer, such as “123 Main Street”.

Address2

Address information, such as an apartment number or a post office box, connected with the location of a customer, such as “Apt #9”.

Birthdate

The date of birth connected with a customer.

City

The city connected with the location of a customer.

Company

The company, typically an employer or small business, connected with a customer.

Country

The country connected with the location of a customer.

Email

The email address connected with a customer. A customer may have more than one email address.

Full Name

A combination of given name and surname–or first name and last name–for a customer. May include a middle name or initial.

Gender

The gender connected with a customer.

Generational Suffix

The suffix that identifies to which family generation a customer profile belongs. For example: Jr., Sr. II, and III.

Given Name

The first name connected with a customer.

Loyalty ID

The identifier for a loyalty program connected with a customer.

Phone

The phone number connected with a customer. A customer may have more than one phone number.

Postal

The zip code or postal code connected with the location of a customer.

State

The state or province connected with the location of a customer.

Surname

The last name connected with a customer.

Title

The title that precedes a full name connected with a customer, such as “Mr”, “Mrs”, and “Dr”.

Unified Coalesced

The Unified Coalesced table has all PII data processed through Stitch. Each semantic tag is a column header. All data is coalesced into a single table. A unique Amperity ID may appear in more than one row.

The following attributes are available from the Unified Coalesced table.

Column name

Data type

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

Address

String

The address connected with the location of a customer, such as “123 Main Street”.

Values in this column depend on fields that are tagged with the Address semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

Address2

String

Address information, such as an apartment number or a post office box, connected with the location of a customer, such as “Apt #9”.

Values in this column depend on fields that are tagged with the Address2 semantic.

Also in: Merged Customers, Unified Customer

Birthdate

Date

The date of birth connected with a customer.

Values in this column depend on fields that are tagged with the birthdate semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

BLV Address

Boolean

When true, the address on this customer profile matches a blocklist value.

BLV Email

Boolean

When true, the email on this customer profile matches a blocklist value.

BLV Given Name

Boolean

When true, the given-name on this customer profile matches a blocklist value.

BLV Phone

Boolean

When true, the phone on this customer profile matches a blocklist value.

BLV Surname

Boolean

When true, the surname on this customer profile matches a blocklist value.

City

String

The city connected with the location of a customer.

Values in this column depend on fields that are tagged with the City semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

CK

String

The ck semantic tag identifies pre-existing, tenant-specific customer IDs. Amperity compares customer keys to the Amperity ID as part of the deduplication process.

Tip

What happens to customer keys in the Unified Coalesced table?

  • Records may have NULL customer keys.

  • There may be only one customer key per data source.

Also in: Unified Customer

Component ID

Integer

An identifier that represents a set of records that are transitively connected with a score above threshold as an outcome of blocking and initial scoring. Records that share a component ID, but have different Amperity IDs, are split during hierarchical comparison.

Tip

Records with different component_id values may show as having blocked together. This can occur after removing a connecting record pair that scored below the pairwise comparison threshold.

Also in: Unified Preprocessed Raw

Country

String

The country connected with the location of a customer.

Values in this column depend on fields that are tagged with the Country semantic.

Important

The country field is added to the Unified Coalesced table when fields are tagged with the country profile semantic.

Also in: Merged Customers, Unified Customer

Create DT

String

Apply the create-dt semantic tag to columns that identify the creation date or time. The field must be a datetime field type.

Also in: Merged Customers, Unified Customer

Datasource

String

The name of the data source from which this customer profile originated.

Tip

The combination of PK and Datasource uniquely identifies a row in the Unified Coalesced table, which correlates to a single row in a domain table.

Email

String

The email address connected with a customer. A customer may have more than one email address.

Values in this column depend on fields that are tagged with the Email semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

FK [Name]

String

The fk-[namespace] semantic tag identifies a field as a foreign key. A foreign key semantic tag must use a namespace. For example: fk-customer, fk-interaction, fk-audience, or fk-brand.

A column is added for each foreign key that is defined in the Sources page.

Tip

What happens to foreign keys in the Unified Coalesced table?

  • Records may have NULL foreign keys.

  • There may be multiple foreign keys in the data source, but there may not be duplicate foreign keys.

  • There may be multiple foreign keys per Amperity ID.

  • There should not be multiple Amperity IDs per foreign key.

Also in: Unified Customer, Unified Preprocessed Raw

Full Name

String

A combination of given name and surname–or first name and last name–for a customer. Amperity selects the first non-nil value:

  1. A value tagged with full-name.

  2. A concatenation of values tagged with given-name and surname if they both exist.

  3. A value tagged with given-name.

  4. A value tagged with surname.

Also in: Merged Customers, Unified Customer

Gender

String

The gender connected with a customer.

Values in this column depend on fields that are tagged with the Gender semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

Generational Suffix

String

The suffix that identifies to which family generation a customer profile belongs. For example: Jr., Sr. II, and III.

Also in: Merged Customers, Unified Customer

Given Name

String

The first name connected with a customer.

Values in this column depend on fields that are tagged with the Given Name semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

Has BLV

Boolean

The has_blv column indicates if blocklist values for address, email, phone, given-name, or surname are present in customer profiles.

Is Supersized

Boolean

Indicates when a rough heuristic applies to the first grouping of records–the rep_pk field–to partition supersized records into smaller parts. Supersized records occur when more than 500 groups associate with the first grouping of records.

Loyalty ID

String

The identifier for a loyalty program connected with a customer.

This column is added when the loyalty-id semantic tag is applied to customer profiles.

Also in: Merged Customers

Phone

String

The phone number connected with a customer. A customer may have more than one phone number.

Values in this column depend on fields that are tagged with the Phone semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

PK

String

The combination of data source and primary key allows Amperity to uniquely identify every row in every data table across the entirety of customer data input to Amperity.

Tip

The combination of PK and Datasource uniquely identifies a row in the Unified Coalesced table, which correlates to a single row in a domain table.

Postal

String

The zip code or postal code connected with the location of a customer.

Values in this column depend on fields that are tagged with the postal semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

Rep DS

Integer

The rep_ds column shows the data source connected with the rep_pk column.

Rep PK

Integer

The rep_pk column is an identifier that represents the first grouping of records done by Stitch. This grouping relies on semantic patterns.

Tip

The combination of Rep DS and Rep PK represent qualified trivial duplications, which are records with enough identical PII to score 3.0 (or greater) and were grouped together by Stitch early in the identity resolution process.

All qualified trivial duplicates are treated as a single record by downstream Stitch processes.

The Rep DS and Rep PK fields are included in the Unified Coalesced table to help with situations where it is necessary to understand why two records were not clustered together.

State

String

The state or province connected with the location of a customer.

Values in this column depend on fields that are tagged with the state semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

Supersized ID

Integer

An identifier represents supersized records partitioned into smaller parts.

Also in: Unified Preprocessed Raw

Surname

String

The last name connected with a customer.

Values in this column depend on fields that are tagged with the Surname semantic.

Also in: Customer 360, Merged Customers, Unified Customer, Unified Preprocessed Raw

Title

String

The title that precedes a full name connected with a customer, such as “Mr”, “Mrs”, and “Dr”.

Also in: Merged Customers, Unified Customer

Update DT

String

Apply the update-dt semantic tag to datetime fields in customer profiles that identify the most recent update in the source system. At least one customer profile must have this semantic tag applied to ensure that the update_dt column exists in the Unified Coalesced table.

Also in: Merged Customers, Unified Customer

Unified Scores

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 following attributes are available from the Unified Scores table.

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 assigned to matched records. 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.