Decision tables
Feature availability is part of a phased rollout. Your organization may not see this functionality yet. It will become available when your environment is included in the rollout.
In SitecoreAI, component personalization uses a decision table to determine which version of a component a visitor sees.
A decision table is a set of rules that maps matching visitor conditions to a specific component variant.
Think of a decision table as a set of if this, then show that rules used to match visitors to different component variants. For example:
| If this is true about the visitor | Then show this component |
|---|---|
| Visitor is a returning visitor | Personalized welcome banner |
| Visitor is using a mobile device | Mobile-optimized call to action (CTA) button |
| Visitor arrived from a marketing campaign | Campaign-specific promotional banner |
When you personalize a component, you configure its decision table using three elements:
- Input - the visitor data used for evaluation, such as country, device type, profile attributes, or custom values.
- Rules - the conditions that determine when a visitor matches a specific scenario.
- Output - the component variants and associated content shown when a rule is matched.
For example, when personalizing a hero banner component, you might configure the decision table to show localized mobile content to visitors in Denmark:
- Input - country and device type.
- Rule - If the visitor’s country is Denmark and they are using a mobile device.
- Output - show the hero banner variant with the Denmark Mobile Promotion content.
Decision tables are evaluated from top to bottom, and the first matching rule determines which component variant is shown.
You can create as many rules as needed to support different personalization scenarios, from highly targeted experiences to broader fallback content.