Skip to main content


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

Interpret the decision funnel with simulation tests (8.2)

Updated on May 3, 2021

Gain a better understanding of how strategy components influence decision outcomes by using decision funnel explanations. By running simulation tests with the new Decision funnel explanation purpose, you can now break down the results of a decision funnel into granular analyses to assess how certain components and expressions influence the overall outcome. For example, you can create a simulation test to investigate whether a new business logic affects the frequency with which propositions would be offered across a segment of customers.

You can create and run simulation tests on the Simulation Testing landing page. Selecting Decision funnel explanation as the purpose for a simulation test adds predefined reports that drill down to the details of proposition counts by Champion Challenger, Proposition Filter, Prioritization, and Switch components.

Thumbnail
Predefined decision funnel reports

If your environment includes Pega Marketing 8.2, you can also view the details of proposition counts by Geofence, Segment Filter, and Contact Policy.

Creating a decision funnel simulation test

Watch the below video to see how to create a decision funnel simulation test in Customer Decision Hub.

Creating a decision funnel simulation test

For more information and detailed steps, see Creating simulation tests in Customer Decision Hub.

  • Previous topic Improve prediction accuracy by monitoring predictive models (8.2)
  • Next topic Review the lifecycle events of data flow runs (8.2)

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us