Every in-appmessage or push notification coming from MBurger can have an array of triggers, those are managed entirely by the MBAutomation SDK that evaluates them and show the mssage only when the conditioon defined by the triggers are matched.
If thre are more than one trigger, they can be evaluated with 2 methods:
any: once one of triggers becomes true the message is displayed to the user
all: all triggers needs to be true in order to show the message.
Here's the list of triggers managed by automation SDK:
MBTriggerAppOpening: Becoomes true when the app has been opened n times (
timesproperty), it's checked at the app startup.
MBTriggerEvent: Becomes true when an event happens n times (
MBTriggerInactiveUser: Becomes true if a user has not opened the app for n days (
MBTriggerLocation: If a user enters a location, specified by
radius. This trigger can be activated with a ttime delay defined as the
afterproperty. The location data comes from the MBAudienceAndroid SDK.
MBTriggerTagChange: If a tag of the MBAudienceAndroid SDK changes and become equals or not to a value. It has a
tagproperty (the tag that needs to be checked) and a
valueproperty (the value that needs to be equal or different in order to activate the trigger)
MBTriggerView: it's activated when a user enters a view n times (
timesproperty). If the
seconds_on_viewthe user needs to stay the seconds defined in order to activate the trigger.