Web Push notifications are notifications sent by a website to a user on a device/browser (mobile or desktop) that a user has opted to receive notifications on. These notifications work similar to mobile push notifications and could be used by B2C companies to engage with users in many ways - cross-sell products, reminders about products added to cart etc.
WebEngage currently supports web push notifications for the following browsers: Chrome, Firefox, Microsoft Edge, Opera, UC and Samsung Browser.
Before you can start sending out web push notifications, your users have to specifically opt-in to receive these notifications on their browsers. The opt-in process is of 2 types: 1-step opt-in, and 2-step opt-in.
This requires only 1 step for the user to opt-in and can be used only for HTTPS websites (those with an SSL certificate). In this method, the browser displays the native prompt asking the user to subscribe to web push notifications. The user only has to click on Allow in order to start receiving notifications from that website.
2-step opt-in, on the other hand, requires 2 steps for the user to opt-in and can be used for HTTPS websites (those with an SSL certificate) and HTTP websites (those that don’t have an SSL certificate). In this method, an on-site notification prompt is shown to the user asking the user to subscribe to web push notifications.
As soon as the user clicks on Allow, a new browser window opens up and the browser now displays the native prompt on the new window asking the user to subscribe.
In 1-step opt-in, users are subscribed to receive notifications from your domain (eg. mywebsite.com).
In 2-step opt-in, users are subscribed to receive notifications from a WebEngage domain (eg.mywebsite.webengagepush.com)
Browsers do not support web push notifications for HTTP websites. In order to enable an HTTP website to send web push notification, WebEngage has implemented a 2-step method of opt-in. Regardless, HTTPS websites also can choose to go the route of a 2-step opt-in if they prefer users being subscribed to a WebEngage domain instead of their own domain.