In this area you can setu your app up to receive Web Push notifications. This service is capable of sending remote push notifications to the majority of the modern internet browsers. In this area you will be able to upload a GCM/FCM server key necessary for Chrome and Opera notifications, a VAPID for Firefox notifications and a Website Push ID for Safari desktop notifications.
To access these pages, expand the Settings menu and click in Services like shown below:
Then you should click the Configure button in the Website Push box:
Please note that before you finish successfully this setup, this service will show the Inactive sign. While inactive you will not be able to send browser notifications at all.
To start configuring website push notifications, please upload an icon for your app. This will be the icon shown in the native browser notifications, make it's a .png file without alpha channels:
For Web Push to work correctly in your web app, you'll need to provide at least one domain where your website runs, if your website runs in several domains you should also provide all those domains. Type the domain name and click in the + button:
As you add domains they will be shown in the list below, you can remove or edit them as you might see fit:
You'll also will need to provide us the URL Format String which will be the landing page for your notifications. This will be the page that will be open when users click the native notification in their browsers. It must provide a placeholder with the format %@ where we will place the notification ID:
To be able to send notifications to Chrome and Opera browsers, you'll need to upload a GCM/FCM server key. To learn how to get this key please visit our guide here. Once you have a server key, paste it in the following field:
Once you have successfully uploaded the server key, we will display something like this:
To be able to send notifications to Firefox users, you'll need to upload an existing VAPID or generate one. If you already have a public and private VAPID keys, paste them in the following fields:
If this the first time you are setting VAPID keys, you can simply hit the Or Generate a VAPID button.
Once you have successfully uploaded the VAPID keys or generated a new one, we will display something like this:
Finally to be able to send notifications to Safari desktop browsers, you'll need to upload a Safari website Push ID certificate, to learn how to generate this certificate please visit our guide here. Once you have a certificate upload it in the following field:
Because these files give access to any Web Push provider to send notifications to your website, it's a good practice to protect these files with a password. In the following field you should provide the password so we can open and extract the information in the file:
Once uploaded, a valid Safari Website Push ID will look like this:
Finally you should click in the Update button to make sure you store these changes:
At this point your service will also show as Active in the Services list:
At any point in time you can change any of the details in this page. Please note that any change in this page in a production web app, might cause the disruption for subscribers of your website notifications. Specially any GCM/FCM server keys, VAPID or Safari Push certificates make it impossible to send messages to older subscribers.