Skip to main content
Event-based triggers enroll contacts into a workflow each time a specific event happens. For example, a form submission, email open, or field change. Unlike criteria-based triggers, which continuously evaluate whether a contact matches a set of conditions, event-based triggers fire in response to a discrete occurrence.

​
Available triggers

​
Web interactions

Fires when a contact submits a form tracked in Conversion.
Fires when a contact visits a tracked page on your website.Each field supports string comparison operators (equals, contains, etc.). All fields are optional — expand only the ones you need.

​
Email events

All email triggers let you optionally select one or more specific emails to scope the trigger, or leave it blank to trigger on any email. Contacts flagged as bots are automatically filtered out and will not trigger email events.
Fires when an email is sent to the contact.
Fires when an email is successfully delivered to the contact.
Fires when the contact opens an email.
Fires when an email to the contact bounces.
Fires when the contact clicks a link in an email.

​
Database actions

Fires when a field value changes on the contact or company record.Both old value and new value support comparison operators (equals, does not equal, contains, etc.). You can use these to trigger only on specific transitions — for example, when a lead status changes from “Open” to “Qualified.”
Fires when a contact is added to an audience.
Fires when a contact is removed from an audience.
Fires when a contact is added to a campaign.
Fires when a contact is removed from a campaign.
Fires when a new contact is created in Conversion. This trigger has no additional configuration fields.

​
Custom events

Fires when a custom event is tracked for a contact via the Events API.Since custom event data is schema-less, all data comparisons use string-based operators: equals, does not equal, contains, does not contain, contains any of, does not contain any of, is any of, is not any of.
Custom events are sent through the API and are always associated with a specific contact. When the trigger fires, that contact is the one enrolled into the workflow. See the Events API for details on tracking events.

​
Filter

Every event-based trigger supports an optional filter that adds an additional eligibility check before a contact enters the workflow. Even if the event fires, the contact will only enter if they also match the filter conditions. Filters use the Unified Query Engine. For example, you could configure a “Form is submitted” trigger with a filter that requires the contact’s company size to be greater than 50. The workflow would only enroll contacts who submit the form AND work at companies with more than 50 employees.

​
Re-enrollment

By default, contacts can only enter the workflow once. When you enable re-enrollment, the contact enters the workflow every time the event occurs. This is different from criteria-based triggers, where re-enrollment requires the criteria to transition from unmet back to met. With event-based triggers, each event occurrence is treated independently.

​
Exit conditions

Exit conditions define when a contact should leave the workflow early, regardless of where they are in the sequence. You configure exit conditions using the Unified Query Engine. When a contact meets an exit condition, they are immediately removed from the workflow.