This page describes the trigger options available when you create a standalone In-App / On-Site campaign from the Campaigns tab. For information on trigger options for single or multistage campaigns, see Event Triggers.

In the Triggers tab of your In-App or On-Site campaign, you can specify the trigger for your campaign message. You can also define the number of times a message is displayed and the number of events required to trigger the display of the message.

Select Trigger Type

The three types of events you can use trigger your messages are:

Server Events

Messages triggered by server events are queued and only displayed to a user when they open your app or website. Server events include any backend events that are triggered from integrations or through external API using the hit event method.

With this trigger option, you can also set an expiration date for messages that prevents users that have been offline for extended durations from receiving outdated messages. To set an expiration date, go to the Message Lifetime section in the Schedule tab of your campaign.

For more information on server events, see Configure Server-triggered Messages.

SDK Events

Messages triggered by SDK events are displayed in real time after a user action triggers the specified event. With this option, you can select events that are tracked directly from your application or website.

For more information on triggering campaigns using SDK events, see Real-time events and Trigger real-time response to events.

Session Start

A system event that needs to be implemented on your applications through the SDK. With the Session Start trigger, campaign messages are displayed when a user opens your application.

👍

Session start event

Only in-app messages can be triggered on Session Start.

For more details on how to trigger session start events from your mobile apps, see Fire real-time events in Android and Fire real-time events in iOS.

Select Event

After you select either Server or SDK event, specify the event that triggers the campaign. These events are configured in the Data Manager tab. For more information on configuring events, see Real-time events.

Use Apply Filter to apply conditions to the event using event values or event properties:

• Event Value: A simple string you can use to create conditions for the event. For example, you can set a condition that the specified event will trigger the campaign only if the event value home_page_clicks is more than 10.
• Event Property: Contains nested values expressed in a JSON object as shown in the example below:////

//Event Property: order_details

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

Filtering based on event properties allows you to create conditions for any property in the event object. Using the order_details example above, you can set a condition that the campaign message is triggered only if the object quantity oforder_details is less than 5.

Apply Trigger Limits

You can define the following rules for your campaign triggers:

• Set the maximum number of times a user or device can trigger a campaign. For example, if you set the maximum number of triggers to one per user per campaign, your user will only trigger the campaign once.
• Define the number of events before a user or device triggers a campaign for the first time.