After the decisioning data has been successfully stored in the Decision Data Store (DDS), it can be used for predictive and adaptive analytics as well as for decisioning logic.
Two data flows pull these records from the DDS and populate them onto the clipboard. They are CustomerData and SingleCustomerData.
CustomerData takes all you customers stored in the CustomerDecision DDS and merges it with all the other pertinent records stored in all other DDS tables that have been created. In Pega Customer Decision Hub for Financial Services, this is all of the accounts associated to the customer. It then takes that bulk set of data and pushes it into a clipboard through the use of an abstract shape. This data flow is used when marketing for a large subset of customers, for example for campaigns and for field marketing.
SingleCustomerData is designed to pull from the DDS for a single customer record. It does this by calling the CustomerData finding the intersection between the customer defined on your customer class at run time and the set of data generated by the CustomerData data flow. This occurs in the Merge shape in the data flow. This data flow is leveraged whenever information needs to be loaded for a single customer or decisioning is done on a single customer. For example, when pulling customer information in the Marketing Profile and providing offers for a specific customer through real-time containers.
When creating an implementation Pega Customer Decision Hub solution:
- To save both CustomerData and SingleCustomer data to the implementation customer class, click Save as.
- Update the shapes to refer to the new data flows and data sets in the
implementation customer class.
Note: Do not change or alter the MasterSegmentTable data set.
This is used as part of segmentation. However, segmentation and exclusion lists do not support the DDS.