Testing the Next-Best-Action strategy framework
You can verify that your Next-Best-Action Designer configuration is giving the desired results by defining a data transform that represents a test customer persona, and running a test for this persona directly from the strategy canvas.
The strategy framework consists of the following components:
- Import actions, to import the actions using Proposition Data shapes
- Engagement policies, which filter out actions based on eligibility, applicability and suitability criteria using Proposition Filters
- NBA strategy framework, which applies constraints, calculates the action and treatment propensity using AI, performs arbitration, and finally applies channel-specific rules to select the top actions based on the channel requirements.
These parts of the strategy framework are tested in slightly different ways. These approaches will be discussed in detail in the sections that follow.
- Testing trigger strategies
Trigger strategies are referenced by the dataflow which is invoked by the channel services. To test a trigger strategy, use the data transform (persona) that was automatically generated for you based on your Context Dictionary and run the trigger strategy to identify where the actions are dropping out or where the strategy results are unexpected.
- Using the trigger strategy to test an engagement policy
If you see that strategy results are getting dropped from one of more of the engagement policies in the trigger strategy, this is often expected behavior since the policy conditions may be legitimately excluding actions that do not meet the criteria. However, if the results are not as expected, the next step is to test the engagement policy strategy to find the issues and groups where the results are unexpectedly dropping out.
- Using the trigger strategy to test the NBAStrategyFramework component
If you see unexpected strategy results from the NBA Strategy Framework component in the trigger strategy, the next step is to test the NBA Strategy Framework strategy to find the high level component where the results are dropping out or are unexpected.
- Testing the lower strategies
Once you identify the point in the framework where you are seeing unexpected results, you may want to test that sub-strategy and perhaps some related strategies.