Table Name | Table Description | Primary Key | JOIN Relationships |
|---|---|---|---|
Individual master-customer records after Customer Data Platform (CDP)’s de-duping of raw child-customers. | mastercustomerid |
| |
Transaction records at the line-level across all sales channels. | id |
| |
List of products. | id |
| |
List of product categories. | id |
| |
Cross-reference between products and product categories. | id |
| |
Cross-reference between master-customers and their first transaction product categories. | id |
| |
Cross-reference between master-customers and their last transaction product categories. | id |
| |
List of sales organizations and stores. | id |
| |
List of events such as emailOpens, web productBrowsed or custom events for your tenant. | id |
| |
Cross-reference between child-customer and master-customer records. Multiple child-customer records could roll up to one master-customer record | id or customerid |
| |
List of online/offline marketing touches or promotions that influenced transactions. | id |
| |
Fiscal calendar mapping for each calendar date. | id (calendar day in YYYYMMDD format) | Any datetime attribute can be joined into the timesummary table to find the corresponding fiscal calendar date. Here are a few examples of how this can be achieved:
| |
customer (optional) | Individual child-customer records before CDP’s de-duping. | id |
|
address (optional) | List of address records for child-customers. | id |
|
customeraddressxref (optional) | Cross-reference between child-customers and their addresses. | id |
|
audiencehistory (optional) | Cross-reference between cohorts and master-customers used to perform Cohort Analysis. | ID |
|
any client-specific entities (optional) | Any client-specific tables configured for your account. | - | - |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Table Name | Table Description | Primary Key | JOIN Relationships |
|---|---|---|---|
Individual master-customer records after Customer Data Platform (CDP)’s de-duping of raw child-customers. | mastercustomerid |
| |
Transaction records at the line-level across all sales channels. | id |
| |
List of products. | id |
| |
List of product categories. | id |
| |
Cross-reference between products and product categories. | id |
| |
Cross-reference between master-customers and their first transaction product categories. | id |
| |
Cross-reference between master-customers and their last transaction product categories. | id |
| |
List of sales organizations and stores. | id |
| |
List of events such as emailOpens, web productBrowsed or custom events for your tenant. | id |
| |
Cross-reference between child-customer and master-customer records. Multiple child-customer records could roll up to one master-customer record | id or customerid |
| |
List of online/offline marketing touches or promotions that influenced transactions. | id |
| |
Fiscal calendar mapping for each calendar date. | id (calendar day in YYYYMMDD format) | Any datetime attribute can be joined into the timesummary table to find the corresponding fiscal calendar date. Here are a few examples of how this can be achieved:
| |
customer (optional) | Individual child-customer records before CDP’s de-duping. | id |
|
address (optional) | List of address records for child-customers. | id |
|
customeraddressxref (optional) | Cross-reference between child-customers and their addresses. | id |
|
audiencehistory (optional) | Cross-reference between cohorts and master-customers used to perform Cohort Analysis. | ID |
|
any client-specific entities (optional) | Any client-specific tables configured for your account. | - | - |
If this content did not answer your questions, try searching or contacting our support team for further assistance.