Web Push Notifications Explained

What are Web Push Notifications?

1.1 Introduction
Web push notifications are clickable rich content messages sent to your device by a website or a web app. Push notifications are delivered to your mobile device or desktop, even when your browser is closed. These notifications can only be sent to users who have subscribed for these notifications from a specific website. As these notifications are pushed to user’s device, users don’t have to be present on the specific website to receive these notifications.
Push Notifications are best used for delivering content in a timely manner and engage users. Other common use cases include retargeting, activation and retention.
They can do a lot of things; for instance, display the latest Cricket Match Score, get the user to take a specific action, such as downloading a coupon, or remind user about an event, such as a flash sale.
1.2 What are web push notifications used for?
Web Push notifications like app notification facilitate seamless flow of information. To receive these notifications, users are not required to download any new app. All a user needs to do is to opt-in for these notifications. Web push notifications are used by marketers, developers and product managers to drive user engagement and user retention. Marketers are increasingly relying on web push notifications as a channel for retargeting. Some of the popular use cases are:
Learn about industry-specific use cases on web push notifications here.
For publishers (and bloggers), web push notification is a great way to communicate directly with their users. They are better than the existing push communication channels such as email or SMS because -

1

They are not impacted by ad blockers

2

They are not blocked by spam filters

3

They are not lost inside already crowded inbox

4

CTRs for web push can be 10X of email.
They can also remind users about a specific event, whether the website is open or not. By adding Call To Actions, they can also be used to drive specific actions, such as :

1

Driving repeat traffic / sharing on social media

2

Promoting products or offers to increase sales

3

Converting web traffic into loyal subscribers

4

Sending transactional communication swiftly
1.3 History of Web Push Notifications
  • June 2009
    Apple launches Apple Push Notification Service (APNs), the first push service.
  • April 2015
    Chrome introduces Service Workers and supports Web Push API with Chrome 42
  • Dec 2015
    Chrome introduces Custom Notification Buttons with Chrome 48.
  • Jan 2016
    Firefox rolls out web push support with Firefox 44 for Desktop
  • May 2016
    Microsoft Edge Releases support Service Workers
  • Aug 2016
    Firefox extends web push API support for mobile with Firefox 48
  • Feb 2017
    Chrome introduces Rich Notifications with Chrome 56
  • April 2017
    Native Chrome Desktop Push Notifications in Mac OS with Chrome 59
1.5 Where do these notifications appear on desktop and mobile
Web push notifications are delivered even when the user is not on the website. On Desktop, these notifications are delivered to the browser, right next to the taskbar.
The user must be an active subscriber to receive these notifications. It is important to note that Apple is yet to support web push notifications on iOS. Follow this thread on the status of push notifications and service workers on iOS.

How do Web Push notifications work?

2.1 Anatomy of a Web Push Notification Message
Title - Every notification needs an eye catching title. The catchier your headline, the better chances that the people click on it.
Description - A description is a short message that supports your title and offering. Write all that needs to be conveyed but squeeze it the form of a short message making sure you don’t compromise with its effectiveness.
Website URL - The website URL from which you subscribed for web push notifications.
Call to Action Buttons - These buttons can be used to trigger different actions – for eg taking the user to a landing page, sending out a social message (Tweet), triggering the Play Store or the Dialer.
Icon - People might be getting numerous notifications. So it becomes essential to let them know when your push notification pops up. Adding your logo will easily let the users know that the push notification is from you.
Banner Image - Relevant images should be used to support you text. As much as your notification title and message should be eye catchy, adding a bright banner image related to your notification content will simply just increase your chance at getting that click.
Dimension : 360*240px
2.2 How do they work?
There are three actors involved with delivering a push notification, along with a fourth, optional, component for advanced functionality.
  1. Push Notification Service: Each browser, including Chrome, Safari and Firefox have their own notification delivery service. Chrome users Google Cloud Messaging ( and now Firebase Cloud Messaging ), Safari users Apple Push Notification Service ( APNS ) and Firefox uses
  2. Service Worker Registration: Developer must register the service worker on the browser. This is only for Chrome and Firefox. Safari does not support service workers.
2.3 Adding to a Website / Web App
  1. Website owners can start by implementing service workers for Chrome and Firefox browsers, and by generating APN certificate for Safari browsers.
  2. Browsers provide standard API calls to read user subscription permissions for the domain and to prompt visitors for notification consents.
  3. Website owners can additionally use service providers like iZooto and use their SDK to take care of the first two steps.
  4. Website owners can push notifications to their subscribers by executing APIs provided by browser push system. This can also be done through UI.
2.4 User Subscription and Activation
  1. Users are prompted for notification subscription whenever they visit the website with a default browser prompt. Developers and website owners can chose to trigger subscription prompts conditionally.
  2. A unique registration key is generated by browser for every user who subscribes to notification.
  3. Notification service provider stores the keys at their end along with any additional data points to identify subscribers uniquely.
2.5 Pushing A Notification
The process of sending notifications follows a 3-step approach.
  1. What - You can define the notification content using either a interface or APIs exposed by the service provider.
  2. When - You may choose to send the notification immediately, basis action/trigger or at a scheduled time.
  3. To whom - You can define the audience to whom you would want to send notifications. The audience filters are typically managed by the service provider, and provide options to send notifications to all, to a specific subscriber, to a segment of subscribers.
Web Push notifications can be targeted and personalised to select segments of your user base, and even personalized for specific users. As compared to email or SMS, in the context of web push, users are not required to do away with their personal information. Segmentation basis a user’s browsing and purchasing pattern ( events and properties ) can used to create powerful audience segments. Marketers / developers would need a interface for writing messages, selecting the target audience and pushing or scheduling notifications.
Publishers can build this infrastructure themselves, or leverage existing tools such as iZooto. Increasingly, web developers opt for iZooto for these services instead of building them, so that they can focus on building their web apps. Building and maintaining a cross-platform web push notification service is bound to consume significant resources and time. SaaS Platforms such as iZooto are best suited because:
2.6 Which browsers support web push notifications?
Currently, only Chrome, Firefox on Android OS, Windows, OS X, Linux and Safari on OS X support web push notifications. All Chromium based browsers also support web push notifications. None of the browsers support web push notifications on iOS.
On Desktop or the large screen, web push notifications are supported by Chrome, Firefox and Safari across Windows, Mac OS and Ubuntu.
For example - while segmenting your subscriber base by their recent activity, it can help you identify some of your most loyal subscribers. It could also allow you to send follow-up campaigns to your most unengaged subscribers — the ones who haven’t done any activity in the past few days.
Device OS Browser
  • Mobile
  • Android
  • iOS
  • Chrome 42+, Firefox 48+
  • NOTHING
  • Desktop
  • Windows
  • Ubuntu (Linux)
  • Mac OS
  • Chrome ( 42+)
    Firefox ( 44+)
    Safari ( 9.3, 10)
    Edge (Latest)
  • Tablet
  • Android/Windows
  • iOS
  • Chrome 42+, Firefox 48+
  • NOTHING
Desktop vs Mobile
Desktop Mobile
Permissions Opt-in Required Opt-in Required
Character limits for notification Depends upon the screen size, width, and the input language selected. Depends upon the screen size, width, and the input language selected.
Direct app open Yes Yes
Deep link support Yes Yes
User control Yes Yes
Image support Chrome only Chrome only
Badge Starting Chrome 53 Starting Chrome 53
Sound support No No
Payload limit 2 kilobytes 4 kilobytes
Interactive buttons Only for Chrome Web Push Limited to 2 Only for Chrome Web Push Limited to 3
Feedback Not from an app, rather through APNs Feedback Server Yes, response from the App/Device
Direct app feedback on delivery No Yes
Device management Notifications are displayed when delivered. No Notification Center Notifications are displayed on lock screen and are avaiable in the notification tray
Two way messaging support Upcoming Feature in Chrome Upcoming Feature in Chrome
2.7 Which browsers support web push notifications?
By default, web push API can only be used by websites operating on HTTPS protocol. For websites operating on HTTP protocol, subscribing to web notifications is a 2-step process. The subscription process involves the user subscribing to a subdomain such as yourdomain.izooto.com or notify.yourdomain.com. Since this is a two click process, the opt-in rates are far lower as compared to HTTPS, hovering around 1% - 3%.
2.8 Permission UX: The right way to ask for permission from a user
It is important that users are convinced to subscribe to notifications before they are prompted. There are multiple ways of educating the end user. Here are some of the recommended approaches :
  1. The user should show intent before a site asks for permission : Most of the marketers and developers commit the mistake of asking permission on page load time. This is not an ideal experience and impacts the opt-in rates adversely resulting in more users actually blocking than allowing for notifications.

Web Push Notification Statistics

3.1 How many users subscribe (opt-in) for web push notifications
All browsers - Chrome, Safari and Firefox require users to grant permission for a website (web app) to send them push notifications. Subscription or opt-in rates vary from anything between 10% to 35% depending upon implementation. These opt-in rates are usually far higher than that of email.
3.2 How many users click on push notifications?
The click-through rate of a notification is defined as the number of clicks on a notification divided by the number of subscribers to whom the notification was delivered, expressed as a percentage. For example, if a notification is delivered to 100 subscribers and receives one click, then the click-through rate for the notification would be 1%.
Most email marketers use this metric to understand the effectiveness and success of their push notification campaigns. In general there is no ideal click-through rate. This metric can vary based on the type of notification sent, how frequently notifications are sent, how the list of subscribers is segmented, how relevant the content of the notification is to the audience, and many other factors. Even time of day can affect click-through rates.
3.3 CTRs: Targeted Notifications vs General Broadcast Campaigns
‘One size fits all’ doesn’t work very well with Web Push Notifications. You cannot assume that all your subscribers will have the same preferences and adopt a general spray-and-pray approach.
It’s common knowledge that sending targeted notifications can help you engage better and get higher click rates. Also by narrowing your focus and targeting selective segments, your subscribers will find your notifications to be much more relevant and keep them from churning away.
For example - while segmenting your subscriber base by their recent activity, it can help you identify some of your most loyal subscribers. It could also allow you to send follow-up campaigns to your most unengaged subscribers — the ones who haven’t done any activity in the past few days.
Similarly, if you planned to target recent subscribers with a “Subscription Date” segment, you might encounter higher engagement and lower bounce rates (due to definite recall) than you would if older subscribers were targeted.

What can you use Web Push notifications for?

4.1 Understanding the Impact of Web Push Notifications
While the adoption of web push notification has been nothing short of crazy, the question on the impact of web push implementation still exists in the minds of marketers.
Well, here is the short answer – No.
There is no negative impact of implementing web push notification. The fact that Google has been pushing for it aggressively, definitely suggests that there is no possible negative impact.
Read this detailed data-driven post on the impact of Web Push Notifications on SEO.
4.2 Industry wise use cases

How to create an effective Web Push notification strategy

5.1 Best Practices
An effective Web Push Notification campaign can easily outform Email Marketing when executed well. Here are tips you can follow to ensure that your web push notification campaign is a success:
Personalization - Personalized messages teamed up with behavioral data perform much better. The messages are highly targeted, timely, and personalized. For example: An eCommerce site sends you a message that those shoes you were browsing last week are now available in your size. When you tap in, the message takes you right to the product page for the shoe with your size checked.
Add Call To Action Buttons - A Call-to-action (CTA) can be added to provoke an immediate response, usually using an imperative verb such as "Buy now", "Know more" or "Share on Twitter".
Push Notifications with Images - We all know “a picture is worth a thousand words”. Notification with an image and call-to-action is worth a lot more than that. Along with call-to-action buttons, Chrome Rich Notifications capture mobile user’s attention and offer powerful ways to interact with push notifications, providing more data for personalization and creating refreshing experiences for users.
Location based targeting - While subscribing to notifications, there are few properties that are captured by-default at the browser end - with one of them being Location. Websites can use location data combined with behavioral data to send relevant notifications such as -
Time Zone Based Delivery of Push Notifications - Internet is everywhere and so are your users – prospects and clients. Clearly, you can no longer afford to ignore that “international-time zone-user-set”. Especially, in such cases, communicating with users across different timezones is a key challenge. More than often marketers not paying heed to this, end up irritating customers. End result – user churn. It is for this reason, understanding your audience is extremely critical. There is fair amount of sensitivity attached to receiving notification on the wrong time – we help you take cognisance of that.
5.2 The Don'ts

Should I build my own Web Push Solution or use a 3rd party service provider?

There are couple of points to keep in mind before taking that “Make or Buy” decision. Building a web push notification platform will, in fact, make it a second product altogether within your core business - a product that demands continuous resources to -
When making that rather important “Make or Buy” decision, ask yourself - are you ready to put in that amount of resource, time and money?
Your sheer focus rightfully needs to be spent on your core business/product, which, as we all know pretty well, isn’t web push notifications. So why not let the “others” take care of it, the ones for whom building web push notifications is the core product? They’ll help you do a much better job at it, don’t you think?
6.1 Checklist for selecting a 3rd party push notification provider
Compatibility
Segmentation
Features
Support
Reporting

Compare with iZooto