Skip to main content

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

Adding predictors to existing adaptive models

Updated on September 15, 2022

For new implementations of Pega Customer Decision Hub, when you save the Context Dictionary configuration, the journey predictors are automatically added to the adaptive models. If you are upgrading your application from version 8.5 or earlier, the predictors are not added automatically, and you must add them manually.

For more information about Context Dictionary, check Defining customer contexts for multilevel decisioning in Pega Customer Decision Hub.

Pega Customer Decision Hub
You must add the predictors to the strategy models at two different levels: action and treatment.
  1. Log in as an operator with access to Dev Studio.
  2. In the navigation pane of Dev Studio, click RecordsDecisionStrategy
  3. Select the strategy to which you want to add predictors
    • To add predictors to an action-level strategy model, select ActionModelImpl. The ruleset of the model should be Artifacts.
    • To add predictors to a treatment strategy model, select the treatments strategy, for example, WebTreatmentModelImpl. Every channel has a different treatment model.
  4. Right-click on Adaptive model component and choose Open Adaptive model.
  5. On the Predictors tab, click Check outParametersAdd parameter.
  6. Add the following parameters:
    • Journey
    • JourneyStage
    • LastJourneyStage
    • DaysinCurrentStage
    • PriorStageInJourney
  7. Make sure that the Data type for all added parameters is Text, and that Predictor type is set to Symbolic, as in the following figure:
    Adding parameters on the Predictors tab
    Adding predictors to action-level strategy model
  8. Click Save, and go back to your strategy.
  9. Right-click the Adaptive model component on the strategy canvas, and then click Properties.
  10. In the Parametrized predictors section, map values to parameters:
    1. To the Journey parameter map .pyJourney value.
    2. To the JourneyStage parameter map .pyStage value.
    3. To the Last Journey Stage parameter map .LastStage value.
    4. To the DaysinCurrentStage parameter map .DaysInCurrentStage value.
    5. To the PriorStageInJourney parameter map .PriorStageInJourney value.
    See the following figure for reference:
    Mapping values to parameters
    Adding properties to an adaptive model
  • Previous topic Understanding how customer journeys influence Next-Best-Actions
  • Next topic Filtering out actions not associated with the current customer journey stage

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