An in-app message is a type of mobile message where the notification is displayed within the app. It is not sent at a specific time but it is shown to users when the user is using the app.
Examples include popups, yes/no prompts, banners, and more.
In order to show in-app messages, there is no permit requirement.
- D·engage SDK 4.2.1+
Created messages will be stored in D·engage backend and will be served to mobile SDKs.
If you integrated mobile SDK correctly for push messages, for using in-app features you just have to add setNavigtion function to every page navigation.
If you want to use a screen name filter, you should send the screen name to setNavigation function in every page navigation.
You should pass the current activity to setNavigation function.
// Page navigation without extra information DengageManager.getInstance(getApplicationContext()).setNavigation(CurrentActivity);
// Page navigation with screen name DengageManager.getInstance(getApplicationContext()).setNavigation('product', CurrentActivity);
For D-engage SDK to detect application state changes (like "bring to front"), please register DengageLifecycleTracker for your application
// Register activity lifecycle callback to handle application bring-to-foreground time Application.registerActivityLifecycleCallbacks(new DengageLifecycleTracker())
Settings > Applications > Mobil Push App > Definition > "In-App Messaging" enable click on
Minimum Interval For Fetching Messages: SDK will fetch messages for that user periodically and stores those messages in local storage. This determines the minimum required elapsed time before fetching the new messages again. (min 15 minutes)
Minimum Duration Between Displaying Messages: If there are multiple messages in the local storage waiting. Most of the time you don't want them to be shown every page navigation. This may disturb the user. So this determines the minimum required elapsed time before showing the next message from the queue.