Send triggers on basis of Trigger Event property

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

Here is a level 🆙  for your Smart Triggers Push & Email notifications. With smart triggers, you can now trigger the message with respect to attribute values of your IF event.

Say you want to remind your users who have booked a flight, 2 hours before the flight time. You will then create your trigger on Flight Booked event using the event property Flight Time.


 And set the message to be sent 2 hours before the flight time.


And the way you can use this feature is only limited by imagination:

- Send discounts/reminders to your subscribers before subscription expiry

- Send communication minutes before the flash sale to customers who have registered for it

- Send reminder before customer's travel date/time, Cross Sell Hotels/Experiences/Local Transport/Restaurant Bookings

- Remind customers to refill consumables before it ends

To note - Campaign will be sent only when

- the event property/attribute which is being used to create these type of triggers (like flight_time in above example), is in a valid date-time format. If it is not in date time format, the string should have data in one of the supported formats. If the selected attributes do not contain data in any of these formats, the campaign won't be sent to your users. 

- the date/time value from attribute is greater than the time at which trigger condition is fulfilled

- the date/time value from attribute is less than 30 Days + the time at which trigger condition is fulfilled e.g. If your trigger condition is fulfilled at date D, your notification will be sent only when the attribute value is less than D+30

- Also note that Intelligent Delay Optimization does not work for campaigns sent on relative timing 

Supported formats for Date/Time Attributes are:

- Date/Time Format sent via MoEngage SDK

- Date/Time values sent in String formats as under:

“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 Day of the Week e.g. Tue
MMM - Represents Month of the Year e.g. Jun
HH:MM:SS - Time that represents the hour of the day, minutes of the hours and seconds of the minute
DD:MM:yyyy and DD:MM:YY are the date formats as most commonly used

Note: We do not support MM/DD/YYYY formats. In case if time-zone is not mentioned in your event property, it will be considered as UTC and notification will be sent accordingly.


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