Trigger: Wait for Event

This trigger is a make our own trigger. We can trigger a dialog activity when a specific event occurs that the existing triggers in the Marketing tool do not support. For example, we can trigger a dialog activity when a customer clicks a custom link on a store page or adds an item to a wish list. The existing triggers do not support these events, so we can set up the Wait for Event trigger to detect these events or others. Store developers must provide you with technical information to set up this trigger, and some customization might be required.


Example

You might want to trigger a dialog activity when a customer clicks a custom link on the storefront.

When a customer clicks the Send me emails about furniture specials marketing content, add the customer to the Subscription List for Furniture customer segment.

We can use the Wait for Event trigger with any other dialog activity actions, such as the Send Message or Issue Coupon actions.


Additional examples of events that the Wait for Event trigger can detect

Use the Wait for Event trigger to detect storefront events, such as the following events:

The Wait for Event trigger can also detect certain events that occur on systems external to WebSphere Commerce. An example of an external event is when a customer calls a call center associated with the store.


Technical information that you need from store developers

When you decide on the event to trigger your dialog activity, meet with store developers to discuss your goals. Store developers must determine how to detect the event within the WebSphere Commerce software. Depending on the scenario, some customization might be required. Store developers must provide you with the following technical information:


Prerequisite for using this trigger

Make sure that the site is configured to support the Management Center marketing features.


Guidelines for using this trigger

When you set up this trigger, we must use the technical information from store developers to specify the event name, one or two parameter names, and optionally, the parameter values to match. In addition, we can specify the number of times the event must occur for a customer and the time frame for the occurrences.

Note: Be aware of the following if you use this trigger with the following actions:

These actions do not work for generic users. Customers who are generic users cannot receive a coupon or a message (email or text message) because generic users share a common ID. In addition, for the Send Message action, customers must opt in to receive email or mobile marketing messages, which typically happens during the registration process.


Related concepts
Activity building blocks: triggers, targets, and actions
Triggers in dialog activities


Related tasks
Creating a dialog activity