Account: Customer and loyalty sample use case data sets
Overview
This page outlines some account based use cases and provides samples of the data required to load these use cases to the CDP.
Account use cases
Customer account only
Loyalty account only
Customer account with loyalty account data
Loyalty account with customer account data
Multiple members for one customer account
Account use case data sets
To load the use cases for this data, you need to load the party profile data before the account data in order to link the member to the account via source party profile.
Sample party profile data
There are both customer accounts and loyalty accounts that are loaded as a part of the account use case data. As mentioned above, we need the associated party profile data in order to load the account data. Below are two separate party profile files: one for linking customer accounts to, and the other for linking loyalty accounts to.
This is random sample data, as a single file could have been used for party profiles along with just a few generic party profiles:
Customer account party profile data: Party_Profile_For_Customer_Account_Gen_20241003.csv
Loyalty account party profile data: Party_Profile_For_Loyalty_Account_Gen_20241003.csv
Sample customer and loyalty account data
This file has both customer and loyalty account data that aligns to the use cases above.
This account data has both loyalty and customer data associated to it: Accounts_Customer_And_Loyalty_20241003_V2.csv.
Account use cases results
This section explains the results of loading account data related to the use cases in additional detail.
Customer account with party profile
This use case is related to an e-com customer account. Data from the account record is loaded to the following base tables:
CUSTOMER_ACCOUNTCUSTOMER_MEMBERSHIP
In addition, the following summary table is also populated from the base tables:
CUSTOMER_ACCOUNT_BU_SUMMARY
Loyalty account with party profile
This use case is related to a loyalty account. Data from the account record is loaded to the following base tables:
CUSTOMER_ACCOUNTCUSTOMER_MEMBERSHIPLOYALTY_ACCOUNT_DETAIL
In addition, the following summary table is also populated from the base tables:
LOYALTY_ACCOUNT_BU_SUMMARY
Customer account with loyalty account data
This use case is related to an e-com customer account that also contains loyalty account data. Data from the account record is loaded to the following base tables:
CUSTOMER_ACCOUNTCUSTOMER_MEMBERSHIPLOYALTY_ACCOUNT_DETAIL
In addition, the following summary table is also populated from the base tables:
CUSTOMER_ACCOUNT_BU_SUMMARY
If you create an account record with an account type that is not loyalty, and you include loyalty data, it will not create a summary data for the loyalty data. Currently, you must add an account record with an account type of loyalty to generate a loyalty account BU summary record. This may require that you provide two account records with different Source Account IDs to get data in both summary tables.
Loyalty account with customer account data
This use case is related to a loyalty account type with associated customer account data. Data from the account record is loaded to the following base tables:
CUSTOMER_ACCOUNTCUSTOMER_MEMBERSHIPLOYALTY_ACCOUNT_DETAIL
In addition, the following summary table is also populated from the base tables:
LOYALTY_ACCOUNT_BU_SUMMARY
Multiple members for one customer account
This use case is related to an e-com customer account that contains two members. Data from the account record is loaded to the following base tables:
CUSTOMER_ACCOUNTCUSTOMER_MEMBERSHIPLOYALTY_ACCOUNT_DETAIL
In addition, the following summary table is also populated from the base tables:
CUSTOMER_ACCOUNT_BU_SUMMARY