This section describes the default Event elements you can insert into a scenario segment (see Creating a Scenario: Basic Steps).

If your application developers have added any custom events, these appear as additional options in the Events element in the Scenarios task area. For more information, see Adding Custom Events, Actions, and Conditions to Scenarios in the Personalization Programming Guide. If your product suite uses Commerce, additional Commerce-related events will appear (for example, Uses Promotion). For more information on these events, refer to the Commerce documentation.

If you use ATG products in a multisite environment (one in which your installation supports several customer-facing Web sites that share data such as user profiles or shopping carts), you can specify the sites that each event applies to. By default, events apply to all the sites in your system. For example, a Registers event is triggered when a user registers on any Web site unless you configure the event to apply to specific sites only. See the Multisite Administration Guide for information on how to set up a multisite environment.

Note for developers: Scenario Event elements are triggered when the ScenarioManager component receives events sent as Dynamo Message System messages. The optional parameters that appear in the scenario editor for a specific Event element correspond to the properties of the message bean that represents that event, including properties inherited from any parent classes. For example, the parameters you can select to further define the Logs In event are the properties associated with the DPSMessageSource component. For technical information on each Event element, refer to Using Scenario Events in the Personalization Programming Guide.