Skip to main content
  1. How do users enter Event Trigger Flows? MoEngage checks each time a user matches the IF condition stated in the Trigger condition to confirm whether they belong to the Target Audience. Users who are part of the Target Audience proceed to the next step of the evaluation process based on the other conditions outlined in the Flow only if they meet those conditions. Thus, it is essential that a user falls under the Target Audience category during the time they meet the entry criteria. If not, they must satisfy the same conditions after becoming a part of the Target Audience to enter the flow. Moreover, users can re-enter the flow only if they don’t belong to the active trips for the same flow and meet all the conditions outlined in it. You can also set a limit on the number of entries to control the number of times users can enter the flow. Specify the desired limit in the second step of the Flow Creation process under the When users enter the flowsection.
  2. When do we check if the user is part of the Target Audience in an Event Triggered Flow? MoEngage checks if the user is a part of the Target Audience when the trigger event is executed. Thus for a user to enter the flow, they should be part of the Target Audience before the trigger event is executed.
  3. A user performed the trigger event but did not enter the flow. Why? If the flow’s Target Audience is a non-real-time (periodic) segment, segment membership is evaluated at the segment’s last scheduled refresh rather than in real time. A user who starts qualifying between refreshes is not yet part of the Target Audience when the trigger event fires, so they do not enter the flow at that moment. Becoming part of the Target Audience at the next refresh does not trigger entry by itself — the user needs to perform the trigger event again after the refresh, while they are part of the Target Audience, for the flow to trigger entry. When your use case allows it, using a real-time segment as the Target Audience avoids this delay. Segments whose rules need periodic evaluation — for example, conditions based on the last 300 days — cannot be made real-time, so this delay is expected in those cases. For more information, refer to Real-Time Segment Evaluation.