Unified_Customer table¶

The Unified_Customer table contains every row of every stitched table with all semantics coalesced into a single column, with two exceptions that are removed from the table: values from a bad-values blocklist and values associated with supersized clusters. A unique Amperity ID may appear in more than one row.

Add table¶

The Unified_Customer table is a required table for the customer 360 database and is always built as a passthrough table from Stitch output.

Important

This table is added automatically when the “Customer 360” template is used to add the customer 360 database. Using a template is the recommended way to add the Unified_Customer table. This section documents how to manually add this table, should it be necessary.

To add the Unified_Customer table

From the Customer 360 page, under All Databases, select the menu for the customer 360 database, and then click Edit.
From the Database Editor, click Add Table.
Name the table “Unified_Customer”.
Set the build mode to Passthrough.
From the Source Table drop-down, select the Unified_Customer table.
Click Next.
Add a table description. This enables a tooltip that is visible from other areas in Amperity.
Verify that semantic tags–given_name, surname, email, phone, address, city, state, postal, birthdate, gender, etc.–were applied to all PII fields correctly.

Tip

You can clear incorrectly tagged semantics individually or for the entire table. To clear semantic tags for the entire table, under Semantic Suggestions click Clear semantics.
From the Table Semantics drop-down, select Unified_Customer.
Click Save.

Column reference¶

The Unified_Customer table contains the following columns:

Column Name	Data type	Description
amperity_id	String	The unique identifier that is assigned to clusters of customer records that all represent the same individual. The Amperity ID does not replace primary and foreign keys, but exists alongside them within unified profiles. Note The Amperity ID is a universally unique identifier (UUID) that is represented by 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 that is associated with the location of an individual customer record. For example: 123 Main Street. Values in this column depend on fields that are tagged with the address semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
address2	String	Additional address information, such as an apartment number or a post office box, that is associated with the location of an individual customer record. For example: Apt #9. Values in this column depend on fields that are tagged with the address2 semantic. Also in: Merged_Customers, Unified_Coalesced
birthdate	Date	The date of birth that is associated with an individual customer record. Values in this column depend on fields that are tagged with the birthdate semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
city	String	The city that is associated with the location of an individual customer record. Values in this column depend on fields that are tagged with the city semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
ck	String	The ck semantic tag may be applied to a column that contains pre-existing, tenant-specific customer IDs. When customer keys are applied, Amperity compares them to the Amperity ID as part of the deduplication process. Also in: Unified_Coalesced
country	String	The country that is associated with the location of an individual customer record. Values in this column depend on fields that are tagged with the country semantic. Also in: Merged_Customers, Unified_Coalesced
create_dt	String	Apply the create-dt semantic tag to columns in customer records that identify when the data was created. The field to which this semantic is applied must be a datetime field type. Also in: Merged_Customers, Unified_Coalesced
datasource	String	The name of the data source from which this customer record originated.
email	String	The email address that is associated with an individual customer record. A customer record may be associated with multiple email addresses. Values in this column depend on fields that are tagged with the email semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
fk_[name]	String	The fk-[namespace] semantic tag identifies a field as a foreign key. A foreign key semantic tag must be namespaced. 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 tab. 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_Coalesced, Unified_Preprocessed_Raw
full_name	String	A combination of given name (first name) and surname (last name) that is associated with an individual customer record and is stored as a combined value in a single field within customer data. A full name may include a middle name or initial. Values in this column depend on fields that are tagged with the full-name semantic. Also in: Merged_Customers, Unified_Coalesced
gender	String	The gender that is associated with an individual customer record. Values in this column depend on fields that are tagged with the gender semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
generational_suffix	String	The suffix that identifies to which family generation a customer record belongs. For example: Jr., Sr. II, and III. Also in: Merged_Customers, Unified_Coalesced
given_name	String	The first name that is associated with an individual customer record. Values in this column depend on fields that are tagged with the given-name semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
loyalty_id	String	The identifier for a loyalty program that is associated with an individual customer record.
phone	String	The phone number that is associated with an individual customer record. A customer record may be associated with multiple phone numbers. Values in this column depend on fields that are tagged with the phone semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, 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.
postal	String	The zip code or postal code that is associated with the location of an individual customer record. Values in this column depend on fields that are tagged with the postal semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
state	String	The state or province that is associated with the location of an individual customer record. Values in this column depend on fields that are tagged with the state semantic. Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
surname	String	The last name that is associated with an individual customer record. Values in this column depend on fields that are tagged with the surname semantic. Also in: Customer_360, Merged_Customers, Unified_Coalesced, Unified_Preprocessed_Raw
title	String	The title that precedes a full name that is associated with an individual customer record. For example: Mr., Mrs, and Dr. Also in: Merged_Customers, Unified_Coalesced
update_dt	String	Apply the update-dt semantic tag to columns in customer records that identify when the data was last updated. The field to which this semantic is applied must be a datetime field type. At least one customer record must have this semantic tag applied to ensure that the update_dt column is created in the Unified_Coalesced table and to ensure that the Merged_Customers table behaves correctly. Also in: Merged_Customers, Unified_Coalesced