Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Extending the customer profile using Customer Profile Designer

In Pega Customer Decision Hub™, you can enable data sources, define summaries on streamable data, create data jobs to ingest data, and extend the customer entity by associating these data sources by using Customer Profile Designer. Learn how to associate a new entity with the Customer Profile Designer.



This demo shows you how to enable a data source and associate it with the customer profile in a few simple steps. You can then use the data source to build engagement policies and as predictors in adaptive models.

The business users of U+ Bank want to use the new Offline Scores data source that the IT department introduced to the system. The bank wants to enrich the profile of its customers with this data to create new engagement policies that confirm whether the customer is suitable for a product. Customers who are below a specific propensity value are not suitable to receive the offer because they are not likely to be interested.

The use case definition


This portal is the Pega Customer Decision Hub portal. To view existing data sources, navigate to the Profile Data Sources landing page. Data sources that are currently enabled in the application are displayed in the corresponding tabs. The system automatically imports existing entities and associations from the Context Dictionary into Customer Profile Designer. In this example, the Customer, Account, and Interaction History data sets are included from the import.

Data sets allow listed in the application


When you add a data source as a Profile Data Source, it becomes available to associate with an entity in Profile Designer.
The U+ Bank system architects already defined the underlying structure and components that are necessary to access the offline scores of the customer. The structure has the following elements:

A database table to store the score data,

The database table


a concrete class for OfflineScores,

The concrete class


The CustomerID, CardScore, ChurnScore, InsuranceScore, and MortgageScore data model properties,

The data model


and a data set to access the offline score data.

Data set to fetch customer data


Now, add the Offline Scores data set to the allow list to construct the association with the customer. The type of the selected data source is automatically displayed in the view.

The data set selection


Notice that the data source is now enabled as a Profile Data Source but not associated with a context yet.

Offline scores is now allow listed


To construct the association between the offline scores and the customer context, navigate to Profile Designer. Here, you can see the entities with definitions in the Context Dictionary and existing associations.

The profile designer


By clicking a data source, it is possible to see the data model, existing records, and data jobs for that data source. These details are the primary entity, Customer.

List of customer fields


Now, add a new associated data source. Enabled data sources in Profile Data Sources are available for selection here. In this case, only one data set is available, so select Offline Scores from the Data set menu.

Adding the new association


When adding new associations, you define how the new data source must map to the primary context. Select CustomerID as the Data Source key to map to the primary context key. This mapping creates the association rule and corresponding page or page-list property in the primary entity.

Making the association to customer


Save the changes to complete the configuration and regenerate the data flows with the newly added data source.

Completed adding the data source


Now, you can see the details of the Offline Score data set and what properties you can access from this data source, existing records, and data jobs.

Fields for the Offline Scores


The system automatically marks the new data structure and its properties as relevant, and now available for use in engagement policies. You can add a new suitability condition to the Credit Cards group, which uses the properties from the newly added entity (in this case, the CardScore).

Adding a new suitability condition


In the new condition, enter CardScore. Notice that the newly-added association is available for selection.

Cards score is available in eligibility


Complete building the condition so that the customer does not see a product on the website if their score is less than 0.2. When finished, save the configuration.

You have reached the end of this video. What did it show you?

  • How to add a data source to the allow list.
  • How to associate the data source with a context.
  • How to use the new data source to build engagement policies.



Tip: To practice what you have learned in this topic, consider taking the Creating a new entity challenge.

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice