Guides

Website Push

In this area you can set up your app to support Web Push and Safari Website Push. In this area you will be able to provide all the information we need to start sending notifications on your behalf.

Under the Settings menu, you should start by clicking in Services:

menu

You should then click in the Configure button from the following box:

box

You should start by uploading an image that will be used as the icon push notifications:

icon field

This should be a 256x256px PNG file without alpha channel.

Once you've uploaded it, you will see your icon as follows:

icon uploaded

Allowed Domains

Notificare supports a multi-domain configuration, and you should provide all the domains where you want to support web push. If you run our library in a domain not specified here, you will receive 403 responses.

You should also provide at least one domain in the following section:

allowed domains

VAPID

To receive push notifications in web apps running in Chrome, Edge, Opera, Firefox, Safari 16 (desktop) and Safari 16.4 (iOS) you only need to provide (or generate) VAPID credentials.

If you already have VAPID credentials generated in another provider, you can paste the Public Key in the following field:

public key field

And paste the Private Key in the following field:

private key field

If this is the first time you are setting up your web app to receive push notifications, then you should simply generate new VAPID credentials, by clicking the following button:

generate vapid button

Once you've pasted your keys or generate new keys, you will see your VAPID configured as follows:

current vapid keys

You can delete a VAPID key by clicking in the button in the top right corner. You can also retrieve stored VAPID keys by clicking in the following button:

show vapid button

This will open a window as follows:

show vapid window

YOu can use this information to migrate from Notificare to another provider.

Safari Website Push

If you want to also want to receive notifications in Safari 15 and below (desktop only), you will need to provide us with a Safari Website Push ID too. You can upload any .p12 file exported (using a password) from your Keychain Access app after being generated in Apple's Developer Portal. To learn how to generate these files, please read our guides located here.

First, you will need to provide us with the URL Format String:

url field

This will be the page where users will land, when they click a notification in Safari 15 or below (desktop). For us to be able to collect metrics, in this field you should provide a URL with a query parameter that includes a placeholder for the notification identifier (e.g. https://mydomain.com?nid=%@).

Then you should provide us the .p12 file you've generated, by uploading it in the following field:

p12 upload field

You will also need to provide us the password you used when you've exported this certificate from your Keychain Access app:

password field

If everything is correct, you will then see your stored SSL Certificate as follows:

ssl certificate

You can also delete your current SSL Certificate, by clicking the button in the top right corner. SSL certificates have an expiration date, when they are expired, you will see something like this:

expired ssl certificate

Launch Configurator

In our Web SDK v3 and higher, the launch mode should be defined in this page too. This will define how our library launches, and you have three different options at your disposal.

If you want to deal with the push permission dialogue yourself, you should select the following option:

launch mode none

In this mode, you will need to use our SDK to develop your own custom onboarding flow.

If instead you want to use one of two managed solutions we offer, you can either select the Dialog mode:

launch mode dialog

Or the Button mode:

launch mode button

Both modes can be customized to fit your needs, including localized versions in as many languages as you need.

Finally, once you've provided all the information required, hit the Save button to store your changes:

save button