Please Ensure That Your Website is Integrated with WebEngage Before Proceeding
Web Push Notifications are clickable media messages that are sent to a user's desktop, mobile, or tablet through a website or web app, even when they're inactive your the site. This makes Browser Push Notifications highly visible and easy to respond to for a user.
Web Push is supported by all major browsers like Chrome, Firefox, Microsoft Edge, Opera, UC Browser. However, notifications containing images are currently supported only by Chrome.
We recommend that you leverage the channel to communicate time-bound messages, reactivate dormant users, and re-engage users who dropped off from your site mid-way in their lifecycle.
However, users need to explicitly opt-in to receive messages from your domain. Once you've set up Web Push opt-in, you can start engaging subscribers with contextually personalized notifications!
Here's how you can go about it:
As shown above, head over to Integrations > Channels > Web Push in your dashboard and click the toggle button to enable Web Push Notifications for your domain.
Looking to Set Up Web Push for AMP Pages?
Depending on whether or not you have an HTTPS domain, Web Push opt-ins can be collected in two ways:
- Directly through Browser-based opt-in prompts. (1-Step Opt-in)
- In-directly through an On-site Notification (shown by WebEngage) that initiates the opt-in process. Users are then led to the Native Browser opt-in prompt to complete the subscription. (2-Step Opt-in)
Let's quickly walk you through how these opt-in models work:
(works for only HTTPS websites/ sites that have SSL Certificate)
The opt-in model enables users to subscribe by simply clicking the Allow button on the native prompt shown by their browser.
Highly recommended if you have an HTTPS domain as users can receive notifications from your custom sub-domain! Opt-in prompts can be customized too.
(works for both HTTP & HTTPS domains)
Since Web Push Notifications are not supported for HTTP sites, we created the 2-step opt-in model to enable messaging for such domains. For the same reason, users will be subscribed to a WebEngage domain like mywebsite.webengagepush.com, and not your domain.
This model requires users to subscribe to your channel in 2 steps:
Step 1: User is prompted by an intermediary On-site Notification (triggered by WebEngage) that conveys why they should subscribe to your Web Push Notifications.
- Once they click the Allow button on the On-site Notification, the browser-based native prompt intimates the User.
Step 2: The User will need to click the Allow button on the second prompt to confirm their subscription.
Highly recommended if you have an HTTP domain.
(HTTPS websites can choose to set it up too if you prefer that users subscribe to a WebEngage domain instead of your own.)
Web Push Opt-in configuration varies as per the option selected at Step 2.
Please Navigate to the Respective Guide to Complete Your Setup
You can always choose to change the way users opt-in to your Web Push Notifications from 2-Step Opt-in to 1-Step Opt-in and vice-versa. However, do keep in mind that doing so causes the loss of your existing subscriber database. Subscribers will be prompted to resubscribe to your channel if the opt-in model is changed. Hence, we recommend that you do so only when deemed necessary.
Here's how you can go about it:
As shown above:
Step 1: Click the Reset button placed on the bottom right of the Configuration section.
- In doing so, you will be prompted to confirm your decision.
Step 2: Click Reset on the pop-up to change the existing opt-in model.
Step 3: Select your preferred Opt-in Type and configure it.
Please feel free to drop in a few lines at [email protected] in case you have any queries or feedback. We're always just an email away!
Updated 4 months ago
So, what's next?
Continue Web Push Opt-in set up...
|Enabling 1-step Opt-in|
|Enabling 2-step Opt-in|
|Web Push for AMP|