Review customer 360¶
The Customer 360 tab allows databases to be created from any combination of stitched output, passed-through domain tables, and custom domain tables. At least one database must be designated as your “Customer 360” database, but there is no limit to the number of databases you may configure for use with any downstream workflow. For example:
Use a passthrough database to separate raw source data from stitched customer data.
Use a QA database to build tables for use with validating Stitch quality and for ensuring that interactions records (for orders and items) are being measured correctly.
Use a custom database for experimentation.
About table types¶
Tables are organized into the following categories:
Standard tables¶
A standard database table forms the foundation of your databases. Standard tables are output by Stitch and provide unified data structures for all data sources to which semantic tags were applied.
Standard tables include:
Campaign_Recipients
Customer_360
Customer_Attributes
Email_Engagement_Attributes
Email_Engagement_Summary
Lifecycle_Events
Merged_Customers
Transaction_Attributes
Transaction_Attributes_Extended
Unified_Customer
Unified_Coalesced
Unified_Email_Events
Unified_Itemized_Transactions
Unified_Product_Catalog
Unified_Scores
Unified_Transactions
along with tables that are associated with predictive modeling and AmpIQ, such as Predicted_CLV_Attributes.
Source and custom tables¶
Source and custom tables make raw source data and custom domain tables available to your customer 360 database as a series of passthrough tables. Source and custom tables will vary from tenant to tenant, but typically represent data that can provide useful context to your customer profile data and to support a variety of upstream and downstream workflows, such as:
Behavioral data
Clickstream data
Marketing campaign response data
Display advertising performance data
Passthrough tables that contain original customer data
And so on …
Any domain table or custom domain table can be configured as a passthrough table for any database.
QA tables¶
A QA database table is output by Stitch for use with the Stitch QA process.
QA tables include:
Detailed_Examples
Stitch_Blocking_Keys
Stitch_Scores
Unified_Changes_Clusters
Unified_Changes_PKS
Unified_Coalesced
Unified_Preprocessed_Raw
Unified_Scores
Review customer profile¶
Customer profile details are pulled from the Customer_360 table, which represents all of your unified customer profiles, including:
Names (first names, last names), email addresses, physical addresses, phone numbers
Transaction details (first purchases, last purchases, total purchases, etc)
Other custom profile values that are unique to your company
You can choose to summarize these customer profile details directly on the Customer 360 tab.

Customer profile details are displayed in the following order:
Fields with an associated icon
Fields marked as a favorite
Fields without an associated icon or not marked as a favorite
Note
Profile details that appear in the Customer Profile section are selected during the Configure and Save step when configuring the Customer_360 table.