Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Loading your data to the customer analytics data store

Updated on August 27, 2020

Populate your customer data into the marketing repository by using the batch ETL process, file dump, or file injection.

Pega provides data flows that demonstrate how to import data from a relational database record into the Decision Data Store (DDS). These data flows are provided only to pull data from other Pega tables.

Start by identifying the data objects that are required by your use cases. At a minimum, the Customer data object must be loaded. Extend the data flows listed below that corresponds to the data object required for your decisioning. Create your own where necessary.


Load your data to the customer analytics data store only when using the Pega Customer Decision Hub for Financial Services application. For more information, see "Implementing your solution with Pega Customer Decision Hub for Financial Services application" in Implementation approaches for Pega Customer Decision Hub for Financial Services.

To load data from other Pega financial services applications, for example, Pega Customer Service for Financial Services, use only the data flows listed in the following table.

Data flowData objectUsage
DF_GetCustomerDataCustomerCopies and saves customer information into the Customer Decision Data Store.
DF_GetCreditCardAccountsDataCredit Card AccountsCopies and saves credit card account information into the CreditCardAccountsDecision Data Store.
DF_GetDepositAccountsDataDeposit AccountsCopies and saves deposit account information into the DepositAccountsDecision Data Store.
DF_GetInvestmentAccountsDataInvestment AccountsCopies and saves investment account information into the InvestmentAccountsDecision Data Store.
DF_GetLoanAccountsDataLoan AccountsCopies and saves loan account information into the LoanAccountsDecision Data Store.
DF_GetAccountDetailsAccountCalls DF_GetCreditCardAccountsData, DF_GetDepositAccountsData, DF_GetInvestmentAccountsData, and DF_GetLoanAccountsData and merges and flattens all the account details into one table.
DF_GetSAFSC2ORelationshipsOrganizationCopies and saves the Sales Automation contact to organization details into the table CRMFS_CUSTOMER.
DF_GetSAFSO2CRelationshipsOrganizationCopies and saves the Sales Automation Opportunity details into the table CRMFS_CUSTOMER.
DF_GetSalesOpportunityDataOpportunityCopies and saves the Sales Automation Opportunity details into the table PMFS_OPPORTUNITY_REPOSITORY. This is meant to be used for segmentation only.
DF_GetSalesLeadDataLeadCopies and saves the Sales Automation Opportunity details into the table PMFS_LEAD_REPOSITORY. This is meant to be used for segmentation only.

In order to pull the records from the source tables, class definition rules need to be created and mapped to each relevant database table. A report definition is then needed to pull the records. For example, in DF_GetCustomerData, the Pega Foundation for Financial Services database tables FSF_SAMPLE_CUST, FSF_SAMPLE_CUST_ADDRESS and FSF_SAMPLE_CUST_COMMS are mapped to through the respective class definitions and pulled from the referenced report definitions. The records of these three tables are merged in the compose shape based on a common key.

Create a class for each of their source database table and define properties that map to the columns in those tables relevant to their intended decisioning logic. Create a report definition to pull those properties and then create or update the existing data flows to do the actual storing.

Note: Different data set rules will create different tables in the DDS. Pega handles the structure of these tables based on the definition of the class defined on the data set rule. A database administrator is not needed to define a table structure when using the DDS.

Use an agent to run these data flows to load the values into the DDS. This way, it can be scheduled as a reoccurring process. Pega Customer Decision Hub for Financial Services provides the agent PegaCDHFS that runs the activity StoreCustomerRecordsinDDS as a reference. By default, this functionality is disabled.

To enable the functionality:

  1. Open the agent rule PegaCDHFS and select the Enable check box.
  2. Restart your system.
  3. Check that the agent schedule rule for PegaCDHFS has been updated to include an enabled StoreCustomerRecordsinDDS.

You can also trigger the activity StoreCustomerRecordsInDDS to refresh the data in your xCAR. Customers should keep in mind that they should update and extend this activity to suit their implementation data model.

A similar agent-run activity exists for the CRM-specific data with the activity StoreContactsInDDS.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us