Onsite messaging and Mobile In-app in MoEngage Flows are currently a Beta Feature. If you wish to try out this feature, reach out to us directly from your MoEngage Dashboard -> Need Help? -> Contact Support or send an email to firstname.lastname@example.org.
MoEngage Flows was envisioned to enable personalized interactions with users on multiple channels. Expanding on this vision, now you can use our Onsite and Mobile in-apps channels in addition to our existing channels to interact with your users via MoEngage flows.
When enabled, you can add these stages at any point in your flows. Once added, please configure all the mandatory fields before publishing the flow. You can read about how to add an In-App message here and about Onsite messaging here.
For both In-App and onsite action campaigns, the user qualifies to receive the configured message as soon as they reach that stage during their flow trip.
Upon qualification, the users must satisfy the configured trigger conditions to receive the message. You can wait for users to interact with the action campaign using one of the below conditional stages.
Similarly, for the Onsite messaging campaign, you can use one of the below conditional stages.
If you do not wish to wait using the conditional nodes, the user will move forward in the flow to the next stage after successfully qualifying for both In-App and onsite action campaigns.
Unlike the other channels, for both In-App and onsite action campaigns, you can choose to schedule how long the configured action campaign should remain "active" this can be set up relative to when each user reaches that stage in the flow or can be fixed.
If you choose to set up a fixed schedule that ends at 4:00 PM on Friday the 13th 2021. Then any users reaching that flow stage after that point will not qualify for the configured action campaign and will move forward to the next flow stage instantaneously.
Once a user has qualified for a campaign, they can perform the trigger action only till the end schedule configured by you. After that, they will not receive the configured message even after performing the trigger condition.
If you want to stop showing the campaigns to users based on their behaviour after qualifying for the campaigns, then you can optionally add such user behaviour events under the validity section on the last step of campaign creation.
As a common practice, you can choose to add the conversion goal event under the validity section so that the qualified users who have performed the conversion without doing the trigger event will not receive the configured In-app or On-site message.
While adding the campaign, you can use any of the below-mentioned attributes to personalize the content of your message
- User profile attributes
- Campaign trigger event attributes
- Flow entry trigger event attributes (in case of triggered flows)
- Flow has done event attributes