Strategies are balanced to determine the most important issue when interacting with a customer. The first step in applying this pattern is adding prioritization components to filter the possible alternatives (for example, determining the most interesting proposition for a given customer). The second step is to balance company objectives by defining the conditions when one strategy should take precedence over another. This optimization can be accomplished by a champion challenger or a switch component that selects the decision path.
Champion Challenger components randomly allocate customers between two or more alternative components, thus allowing for testing the effectiveness of various alternatives. For example, you can specify that 70% of customers are offered product X and 30% are offered product Y.
Champion challenger components express component selection through the Champion Challenger tab. Add as many rows as alternative paths for the decision and define the percentage of cases for each decision path. All alternative decision paths need to add up to 100%.
Exclusion components conditionally stop the propagation of results by restricting the selection to results that do not meet the exclusion criteria. These components are typically used to build traditional segmentation trees in strategies. Exclusion components express the selection of results through the Exclusion tab.
Use the Type drop-down to select the type of data: Pages or Component.
In the Name field, select the page or component.
The Class field displays the class context.
The criteria to exclude results is defined as one or more conditions in the Exclude when all conditions below are met section. This is a value pair between properties in the exclude component and, depending on what you selected in the Type field, properties in the page or strategy component. If you do not define any condition, this component stops the propagation of the results of its source components.
Switch components apply conditions to select between components. These components are typically used to select different issues (such as, interest or risk) or they select a component based on customer characteristics or the current situation.
Switch components express component selection through the Switch tab. Add as many rows as alternative paths for the decision, use the Select drop-down to select the component and enter the expression that defines the selection criteria in the If field. The component selected through the Otherwise drop-down is always selected when conditions are not met.
- Strategy rule form - Completing the Strategy tab
A strategy is defined by the relationships of the components that are used in the interaction that delivers the decision. The Strategy tab provides the facilities to design the logic delivered by the strategy (the strategy canvas) and to test the strategy (the Test runs panel).
- About Strategy rules
Strategies define the decision that is delivered to an application. The decision is personalized and managed by the strategy to reflect the interest, risk, and eligibility of an individual customer in the context of the current business priorities and objectives. The result of a strategy is a page (clipboard or virtual list) that contains the results of the components that make up its output definition.
- Completing the Strategy rule form
Strategy rules - Completing the Create, Save As, or Specialization form
- Strategy rule form - Using the Strategy Properties tab
The Strategy Properties tab displays details of the strategy's applicability in the decision hierarchy and the properties available to the strategy:
- Declare Trigger form - Completing the Pages & Classes tab
Use this tab to list the clipboard pages referenced by name in the Triggers tab. See How to Complete a Pages & Classes tab for basic instructions.