Capturing Interaction History

Transcription

1 Capturing Interaction History Pega Marketing for Financial Services 7.4 April 2018 Introduction This document contains information about how Pega Marketing for Financial Services 7.4 captures Interaction History. This is an extension of the Pega Marketing 7.4 Interaction History features. Refer to the Pega Marketing 7.4 User Guide on the Pega Marketing product page for details. Customers and sales representatives are recommended to use this as a reference for implementing their own functionality around Interaction History. While the back-end rules that support the Interaction History functionality is included in the PegaMarketingFS application, the rules listed in this document are in the sample application (PegaMarketingFS_CRMSample). Contents Interaction History Capturing Interaction History Headless integration (Real-time containers) Microsites - Non-bundled offers microsite - Bundled offers microsite (fixed bundles) - Bundled offers microsite (flexible bundles) s Interaction history Interaction History is a storage location for the actions and choices made by a customer so that so that real time decisioning and predictive analytics can be utilized to present the best offer or take the next best action for a specific customer. For more details about Interaction History, see the articles on decision management (covers ADM, Interaction History, and VBD) available on PDN. The information from Interaction History is used in a variety of places within the application. Some key functionality include in adaptive models and strategy rules. Adaptive model learning is based on the outcome dimension in the Interaction History. Capturing Interaction History 1

2 Next-best-action strategies refer to the Interaction History to determine how many times a proposition has been offered to a customer, and how many times it has been rejected or accepted, and use that information the make decisions. Interaction History is also captured and used in the below functional areas in Pega Marketing for Financial Services: Microsites Offer flows Real-time containers Capturing interaction history The following table represents the fields captured for Interaction History and their relative use. Property name Fact ID Description An automatically generated unique fact record ID. Initially generated IDs start at a Capturing Interaction History 2

3 Property name Subject ID Outcome time Business issue Group Proposition Outcome Propensity Direction Channel Interaction Strategy Operator Description random value, and then the value is incremented by 1 for every new ID. The subject ID that was used when setting the results of the strategy. It represents the identity (the customer) with whom the integration was handled. A time stamp when the record was stored in the Interaction History tables. The issue to which the proposition belongs. It is the ultimate purpose of the proposition (for example: Sales, Retention, Service). Together with pygroup and pyname, it uniquely identifies the proposition. The group to which the proposition belongs (for example: Phones, Discounts, Tariffs). Together with pyissue and pyname, it uniquely identifies the proposition. The name of the proposition. Together with pyissue and pygroup, it uniquely identifies the proposition. Contains the result of the interaction (for example: accepted, rejected). Calculated propensity for the action. It is the likelihood that a customer will accept a particular proposition. The value for propensity is within the range of 0 to 1. The direction that is used in the interaction (for example: inbound, outbound). The channel that is used in the interaction (for example: web, call center). The Interaction rule instance. The Strategy rule instance. The person who handled the interaction. The default is the Operator ID. Pega Marketing for Financial Services captures this information as part of the Pega-provided microsites (autoloan, nonbundles, and bundled), s, and as a headless integration through real-time containers. This includes capturing clicks on links or images, capturing navigation across different microsite pages, and through services to other applications. Headless integration (real-time containers) Real-time containers support presenting offers or next-best-actions through a headless REST service. Pega Marketing for Financial Services provides NextBestAction and TopOffers containers Capturing Interaction History 3

4 to support the application as a centralized decision hub for other Pega applications such as Pega Collections, and Pega Customer Service for Financial Services. Within Real-time container rules, configure the Container Details tab to enable Interaction History capture. Captured on retrieval Select this option to have the Container processing API (ExecuteWebContainer) automatically capture an impression before rendering the Container. CaptureResponse is a REST service that is used by Pega Customer Service for Financial Services to respond to Offers triggered via TopOffers container. MicrositesAutoloan Microsite The AutoLoanCreditOffers data flow rule stores the results coming from the AutoLoanCredit decision strategy in Interaction History whenever someone submits an application for preapproval. Capturing Interaction History 4

5 Offers with Approved Outcome gets presented to customers in Autoloan microsite. Capturing Interaction History 5

6 The SaveOfferResponse interaction rule updates the Interaction History for the offer response after the user clicks Accept. The interaction rule is called in the activity GetOfferDetailsWrapper. For more details on Autoloan microsite, see Pre-qualify Credit Offers via Mobile Devices. Non-bundled offers microsite Pega Marketing for Financial Services includes the NonBundledOffers microsite which demos displaying single offers. The below table includes rules which support Interaction History table update in for this demo scenario. Scenario Interaction History outcome Referenced rule Interaction History interaction Open microsite from a banner ad/csfs Portal Clicked Service HTTP: CaptureWebClickThrough [PegaMKT-Engine] Capturing Interaction History 6

7 Scenario Interaction History outcome Referenced rule Interaction History interaction Clicking on Impression UpdateIH (Flow:UpdateIH) SaveOfferResponse banner ad Request more Pending GetOfferDetails (Activity) SaveOfferResponse info Open account - Microsite Accepted CaptureMicrositeInteaction (Activity) MicrositeInteraction Open account No response within 30 minutes Accepted NoResponse Update Status shape in (Offer flows) WaitExpired - update status shape in (Offer flows) The Update Status shape is used in offer flow to capture offer responses from the channel. This shape in offer flows is designed to update the Interaction History. Bundled microsite (fixed bundle) Capturing Interaction History 7

8 Pega Marketing for Financial Services includes the BundledOffers microsite which demos displaying bundled offers. This example demonstrates fixed bundles where the customer must select the bundle in its entirety (all members). The below table includes rules which support Interaction History table update in for this demo scenario. Scenario Interaction History outcome Referenced rule Interaction History interaction Open microsite from a banner ad/csfs Portal Clicked Service HTTP: CaptureWebClickThroug h [PegaMKT-Engine] Clicking on banner ad Request more info Open account - Microsite Open account No response within 30 minutes Impression Pending Accepted Accepted NoResponse UpdateIH (Flow:UpdateIH) UpdateBundleIH (Activity) CaptureMicrositeInteacti on (Activity) Update Status shape in (Offer flows) and AcceptBundleMembersO ffers strategy WaitExpired - update status shape in (Offer flows) SaveOfferResponse SaveOfferResponse MicrositeInteraction Bundled microsite (flexible bundle) Pega Marketing for Financial Services includes the BundledOffers microsite which demos displaying bundled offers. This example demonstrates flexible bundles where the customer is presented a series of questions and answers from which a bundle is presented based on the captured response. Capturing Interaction History 8

9 The interaction history functionality works similarly to fixed bundles. There are some additional values set for the interaction history in the property set shape of the strategy FlexibleBundles. This helps capture the impression on loading the bundle offers in the microsite. The actual update of Interaction History is still done in the offer flows. See the highlighted shapes in the below example FirstMortgageFiveOneARM where Interaction History is updated for the bundle parent and bundle (child) member offers. Capturing Interaction History 9

10 s Treatment rules automatically update the Interaction History when s are sent. If the Track Open Rate checkbox is enabled, then, Interaction History will also capture the open impression. Capturing Interaction History 10

11 Interaction History can also capture when a customer clicks on a link, button, or image within an . See the Pega-provided treatment rules for how this is accomplished. For example, the Open Account button in OfferDetails sends offer response as Accepted to an Offer flow where update status shape takes the offer response and updates Interaction History Pegasystems Inc. All rights reserved. All trademarks are the property of their respective owners. The information contained in this document is subject to change without notice. Pega will not be liable for technical or editorial errors or omissions contained in this document.