A scenario is a choreographed series of interactions with your website or application that can triggered by specific events or profile attributes. A scenario specifies exactly what content will be displayed to whom and when it will be displayed. Scenarios should be created after, or in parallel with, your content, your renderers, and your slots. The content and the renderers work together to create the personalized offer. You create scenarios using references to the slots you have defined and the content you created.
Like slots, scenarios are created, edited, and managed using the ACC. A scenario definition contains actions and events that can control who will see what content and when. The scenario must specify content that has been saved to a repository. The scenario definition must also define which slot it will fill. This is why you must create your slots before (or in conjunction with) your scenarios.
Scenarios are completely customizable. ATG includes numerous scenario events and actions; some of these are generic and can be used with any ATG product, others are specific to the ATG Service applications. You may also create custom actions and events to meet your business needs. For details about scenarios, scenario elements, events, and actions see the ATG Personalization Programming Guide and the ATG Personalization Guide for Business Users.
