Event triggers

This page describes how to set triggers for event-triggered single or multistage campaigns. To see how to set triggers for In-App / On-Site campaigns, see Set Triggers for In-App and On-site Campaigns.

The Triggers tab is where you specify the rules and behavior of the event trigger for your single or multistage campaign.

Event data may be passed from:

• Android application
• iOS application
• Website
• External API
• Various automatic, system events; for example application_install, session_start and profile_create. These can only be used for mobile app campaigns.

Learn more about real-time events in our dedicated guide.

Select event

In the Triggers section, you can select the event which will trigger the notification. Events that have been previously manually created from Data > Data Manager > Events or fired from your website, app or via the external API at least once will appear in the dropdown menu.

Limit triggering on some events

When this checkbox is selected, hits to the selected event will only trigger the notification when additional filtering conditions are passed.

Conditions can be set in relation to event values or nested event properties. An event value corresponds to a string (a simple value like homepage), so this filtering condition will be able to perform evaluations in relation to this value (for instance whether something is equal/not equal to this value).

An event property is a complex value, expressed with a JSON object as shown in the following example:

{
   "order_no": "ABC123",
   "order_date": "2021-03-14",
   "price": 304.67,
   "quantity": 5
}

Filtering based on event properties allows you to perform evaluations in relation to the information contained in this object (for instance, that this property contains a specific value).

Send with a delay

Select this box if you want to send the message with a delay after the event has been hit.

👍

Campaign segmentation is evaluated when the campaign is sent rather than when the event is fired. When a delay is used, this means the segmentation is applied after the delay has passed, allowing the most recent up-to-date information available in the system to be used.

Message limits

This section allows to establish limits on the number of times a notification will be shown.

• Maximum number of triggers: User/device notification limit is the maximum number of notifications a user or device can receive either per day or per campaign. If they continually hit an event, they will not receive more notifications than specified.
• Number of events before the first trigger: defines the number of times per day or per campaign an event must be hit before the user or device receives a notification (in the case of single-stage campaigns) or enrolls a workflow (in the case of multi-stage campaigns).
• Block Re-entry During Active Journey: Enable this toggle in multistage campaigns to prevent profiles from re-entering the journey while they are still actively participating. Users can only re-enter once they have completed the current journey.