Pegasystems PEGAPCDC87V1 Exam Questions

The best way to organize customer actions applicable to various business issues in Pega Customer Decision Hub is into a three-level hierarchy: Business issue > Group > Actions. This structure allows for clear categorization and management of actions based on their business purpose and relevance. The 'Business issue' represents the high-level goal (e.g., Retention, Acquisition), 'Group' categorizes the actions under each issue (e.g., Credit Cards, Mortgages), and 'Actions' are the specific offers or recommendations.

Requirement for Total Revenue Calculation:

MyCo needs to calculate the total revenue of three new actions over a specified period.

The goal is to aggregate the revenue generated by these actions.

Use of Group By Component:

The Group By component is used to aggregate data based on specified properties.

In this scenario, it can be configured to sum the revenue of the three new actions.

Configuration Steps:

Configure a single Group By component to group the actions by their identifiers.

Use the aggregation function within the Group By component to calculate the sum of the revenue for the grouped actions.

Efficiency and Simplicity:

Using a single Group By component simplifies the strategy by avoiding redundancy.

It ensures that all actions are considered in a single aggregation process, providing an accurate total revenue calculation.

Verification from Pega Documentation:

According to Pega's guidelines, a single Group By component can efficiently compute total values such as revenue by grouping and aggregating data.

Email treatments in Pega Customer Decision Hub allow for personalization, including customizing the email subject to address the customer by name or other personalized data.

Definition and Purpose:

Email treatments are used to define the content and presentation of email communications sent to customers as part of outbound campaigns.

Personalization enhances the relevance and engagement of these emails by including customer-specific information.

Capabilities of Email Treatments:

Personalization Tags: Pega supports the inclusion of dynamic tags in the email subject and body, allowing for personalized greetings, offers, and other content. For example, 'Dear <customer name>' where '<customer name>' is dynamically replaced with the actual name of the customer.

HTML Content: Design rich email content using HTML, which can include images, links, and other multimedia elements.

Steps to Personalize Email Subjects:

Step 1: Create or edit an email treatment in Pega.

Step 2: In the subject line field, use the syntax for personalization tags. For example, 'Dear <customer name>, check out our new offers!'.

Step 3: Map the personalization tags to the appropriate customer data fields to ensure the correct information is inserted when the email is sent.

Testing Personalization:

Use seed lists to test personalized emails. Seed lists are groups of test email addresses used to preview how the email will look when sent to actual customers.

Ensure that personalization attributes appear correctly in the received test emails.

Best Practices:

Always test personalized emails thoroughly before launching a campaign to ensure that the tags are working correctly and the content renders as expected.

Use personalization to enhance customer engagement by making emails feel more relevant and tailored to individual recipients.

Pega-Customer-Decision-Hub-User-Guide-85.pdf: 'Configuring email treatments' section.

Pega documentation on 'Defining an action for outbound'.

Ethical Bias Policy Configuration:

To allow minimal bias on age while ensuring eligibility (Age >= 18), an appropriate Gini coefficient threshold needs to be set.

The Gini coefficient measures statistical inequality, with 0 representing perfect equality and higher values indicating more bias.

Choosing the Gini Threshold:

A 0.1 Gini coefficient is a low threshold that allows minimal bias.

It ensures that the actions are distributed fairly among customers while still respecting the eligibility condition.

Detailed Explanation:

Setting a 0.1 Gini coefficient allows for slight variations in distribution, which is sufficient to accommodate the Age >= 18 requirement without introducing significant bias.

Verification from Pega Documentation:

The Pega Customer Decision Hub User Guide explains the use of Gini coefficients for measuring and setting thresholds to control bias in decisioning strategies.

Proposition Data Components - These components in a decision strategy are used to import and reference actions or propositions.

Requirement - The strategy designer wants to import all actions from one group and a subset from another.

Minimum Number Calculation:

One component for importing all 10 actions from the Sales/Credit Cards group.

Another component for importing the 2 specific actions from the Sales/Mortgages group.

Pega Customer Decision Hub User Guide 8.6, Section on configuring and using Proposition Data components in strategies .