An on-site message is a type of web message where the notification is displayed within the website. It is not sent at a specific time but it is shown to users when users are using the app. Examples include popups, yes/no prompts, banners, and more. In order to show on-site messages, there is no permit requirement.
Created onsite messages will be stored in D·engage backend and will be served to web SDKs.
On-site messages on the D·engage platform is triggered by page navigation. For displaying onsite massages 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.
// Page navigation without extra information dengage('setNavigation');
// Page navigation with screen name dengage('setNavigation', 'cart');
How to enable onsite messaging
Settings > applications > Web Push App > Definition > “On-Site 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.
Trigger On SDK Load: This will trigger setNavigation function automatically when the SDK loaded. If your website is not a single page application and you don’t want to use screen name filtering, then you can use this option. By using this option you don’t have to do any code changes to your website.