Develop > Presentation layer > Customize marketing > Marketing customization: Management Center > Customizing triggers, targets, and actions
Define the event and parameters for the Wait for Event trigger
Marketing managers require technical information from store developers to set up the Wait for Event trigger in a Dialog activity. This information includes the event name and the parameters that the marketing services will use to detect that the event has occurred. To gather this information, determine the type of event to match and then complete some steps to define the event and its parameters. Depending on the type of event, you might need to implement a service call with a custom URL or using Java code.
Before you begin
To understand how marketing managers can use the Wait for Event trigger for Dialog activites, read Trigger: Wait for Event.The Wait for Event trigger can support three types of events. The following table lists the three types in the left column.
To use the Wait for Event trigger, the event to detect must be one of these three types.
Note that the Wait for Event trigger does not support events that occur when a controller command exits. An example is when the LogonCmd controller command successfully exits, indicating that a customer has logged on.
Procedure
Decide on the type of event that will start or continue a Dialog activity containing the Wait for Event trigger; then follow the relevant procedure in the right column of the table.
Type of event Example Procedure for defining event and parameters the Wait for Event trigger 1. An event that occurs on the storefront – the event is triggered by an existing WebSphere Commerce URL command Examples:
- A customer adds an item to a wish list. The existing WebSphere Commerce URL command is InterestItemAdd.
- A customer removes an item from the shopping cart. The existing WebSphere Commerce URL command is OrderItemDelete.
- A customer views a category display page. The existing WebSphere Commerce URL command is CategoryDisplay.
Both Ajax and non-Ajax URL commands are supported. For examples of existing WebSphere Commerce URL commands used in the Madisons starter store, see the relevant store page topic within the section Site flow and interactions in the Madisons starter store. For example, for the Product Details page, the URL commands are listed under "Links and buttons," for example, OrderChangeServiceItemAdd, InterestItemAdd.
Define the event and parameters for a storefront event: existing WebSphere Commerce URL command 2. An event that occurs on the storefront – the event is triggered by a custom URL you create Examples:
- A customer clicks a link on a store page to subscribe to promotional offers for a category.
- A customer clicks a button on a store page to start a live chat session with customer service.
Define the event and parameters for a storefront event: custom URL 3. An event that occurs on a system external to WebSphere Commerce, such as a point-of-sale system or a call center Example:
- An external credit card fraud detection system detects that fraud has occurred for a certain customer's credit card.
Define the event and parameters: external event
Related concepts
Triggers in marketing activities
Related tasks