The term "wait for event" refers to a type of step that can be incorporated into your automation (a.k.a. drip campaign).
This step allows you to wait for a recipient to take a certain action before proceeding to the next step in the drip campaign. Using this step creates an interactive, or real time, experience for the recipient.
1. You can set a max wait time for a Wait for Event step. For instance, if after two weeks you don't want to wait for the contact action any more, you would choose two weeks as your max time.
2. Typically there is not reason to use a Pause + Flag Event and a Wait for Event in conjunction, but choose one method or the other.
3. Enterprise clients can start an automation using Wait for Event.
4. You can add more nuance to your Wait for Event clauses by using additional groups to add more clauses.
Drag the Wait for Event over to the desired section of your automation workflow. Click the pencil to edit your specifications. Your choices are the same as Flag Events and include:
Opened: This flag will evaluate if the contact opened a campaign you specify. The campaign MUST be included within the existing automation workflow (not another, unrelated campaign).
Clicked on Email link: This flag will evaluate if the contact clicked on one or multiple links in a specified campaign. The campaign MUST be included within the existing automation workflow (not another, unrelated campaign).
Clicked on SMS link: This flag evaluates if a contact clicked on a link in a previous SMS message from the same automation.
Purchased from clickstream / eCommerce Store: You may note that these options are locked if your account does not have Clickstream or a Commerce integration enabled. If enabled, these flags will evaluate a completed purchase.
Currently Subscribed to SMS: This flag may also be locked. This step evaluates we have a SMS keyword attached to the contact's email record.
Evaluate contact data: This flag allows you to evaluate one or more database fields associated to a contact, typically looking for a change. Functionally, this process uses clauses (equal to, contains, etc) so it is very similar to building segment clauses.
Evaluate category: This flag evaluates if a contact is a member of a category or not.
Enterprise customers have the option to START their automation with a "Wait for Event" action rather than a "Send Email" or "Send SMS" step.
Starting an automation with a "Wait for Event" step (commonly referred to as Event-Based Automation) allows you to wait indefinitely on a change to a subscriber's demographic field (all fields are available) or category to kick off your automation.
For B2B customers, we have several automation templates (with links to help guides) to help you get started: