Send Triggers Based on the Trigger Event Property

Do you want to remind your users about their booked flight, 2 hours before the flight time? Do you want to remind them about the expiry of their subscription that they bought last month? Do you want them to recharge their mobile data pack 2 days before it expires?

You can achieve such scenarios with Event Triggered Push and Event Triggered Email notifications. With event triggers, you can trigger the messages with respect to the attribute values of the IF event.

For example, you can remind your users who have booked a flight, 2 hours before the flight time. You need to create a trigger on the "flight booked" event using the flight_time event property.

To create a trigger:

  1. In the IF user section, from the Has Executed drop-down list, select the "flight booked" event as shown below:
    event trigger.png
  2. In the THEN trigger the message section, set the result for a message to be sent 2 hours before the flight time as shown below:

The following are some of the scenarios for which you can use this feature:

  • Send discounts or reminders to your subscribers before the subscription expiry
  • Send a communication before the flash sale to customers who have registered for it
  • Send a reminder before customers' travel date or time
  • Send a message to cross-sell hotels, experiences, local transport, restaurant bookings
  • Send a reminder to customers to refill consumables before they end


Event-triggered campaigns are sent only when:

  • The event property or attribute, which is used to create these type of triggers (such as flight_time in previous example), is in a valid date-time format. Here are the  supported formats. If the selected attributes do not contain data in any of these formats, the campaigns are not sent to the users.
  • The date or time value from the attribute is greater than the time at which the trigger condition is fulfilled.
  • The date or time value from the attribute is less than 30 Days + the time at which the trigger condition is fulfilled. For example, if your trigger condition is fulfilled at date D, the notification is sent only when the attribute value is less than D+30.
  • The intelligent delay optimization (With Delay) does not work for campaigns sent on relative timing.

Supported Formats

The following formats are supported for Date/Time attributes:

  • Date/Time format sent through the MoEngage SDK
  • Date/Time values sent in string formats as follows:

“EEE MMM dd HH:mm:ss Z yyyy”,
“EEE MMM dd HH:mm:ss yyyy zzz”,
“EEE, MMM dd HH:mm:ss yyyy zzz”,
“EEE, dd MMM yyyy HH:mm:ss zzz”,
“EEE,dd MMM yyyy HH:mm:ss zzz”,
“EEE, dd MMM yyyy HH:mm:sszzz”,
“EEE, dd MMM yyyy HH:mm:ss”,
“EEE, dd-MMM-yy HH:mm:ss zzz”,
“yyyy/MM/dd HH:mm:ss.SSS zzz”,
“yyyy/MM/dd HH:mm:ss.SSS”,
“yyyy/MM/dd HH:mm:ss zzz”,
“yyyy.MM.dd HH:mm:ss”,
“yyyy-MM-dd HH:mm”,
“MMM dd yyyy HH:mm:ss. zzz”,
“MMM dd yyyy HH:mm:ss zzz”,
“dd.MM.yyyy HH:mm:ss zzz”,
“dd MM yyyy HH:mm:ss zzz”,
“dd.MM.yyyy; HH:mm:ss”,
“dd.MM.yyyy HH:mm:ss”,
“dd.MM.yyyy zzz”


  • ZZZ: Represents the reported timezone
  • EEE: Represents the day of the week, for example, Tue
  • MMM: Represents the month of the year, for example, Jun
  • HH:MM:SS: Represents the hour of the day, minutes of the hour, and seconds of the minute
  • DD:MM:yyyy and DD:MM:YY: Date formats most commonly used


We do not support MM/DD/YYYY formats. If time-zone is not mentioned in your event property, the UTC is considered and a notification is sent accordingly.

Was this article helpful?
3 out of 3 found this helpful

How can we improve this article?