Browsing the web, you may have noticed that most websites use a double opt-in process for subscribing the users to notifications. Basically these websites first show a custom prompt (designed with HTML / CSS) that asks you if you are interested in the notifications, then, when you click the subscribe button, they display another prompt (with native appearance) asking you if you really want to allow the notifications from the website. Isn’t one prompt enough?
Are you wondering what is the maximum length of text that you can include in your web notifications?
It’s easy to create segments based on the user preferred language. In this way you can send different notifications to users with different language preferences.
There are many reasons to add a service worker to WordPress: for example you may want to improve caching or add web push notifications. Let’s see how to do that.
A notification that is successfully delivered to the browser push service, may not reach the end user for various reasons:
Would you like to send web push notifications only to people located in a given place? If you use Pushpad you can implement that in different ways.
Are you stuck with an old version of the service worker or your imported scripts are not being updated as you expect? This guide shows you how to ensure that your service worker and the imported scripts are updated in a timely manner.
Now you can use Pushpad for delivering time-sensitive messages. For example you can notify urgent alerts or incoming phone calls.
What if you want to send a web push notification only to 10% of your users? This can be useful for example for testing and for measuring CTR for that notification before sending it to all your users. There are many ways to achieve that, but in this tutorial we will show a simple method with tags.