[WEB] Web Push Setting Guide

Own domain push VS alternative domain push

DFINERY supports two primary technologies for web push notifications.

If the website is a self-developed site and has a development team, it has its own domain push function and
This is an alternative domain push feature that you can utilize if you are using a web builder or do not own your own server infrastructure.

To understand your own domain push and alternative domain push, you need to understand subscription notification settings and push subscription pop-up windows .

Users may be confused if a site suddenly requests browser permission for web push notifications.

Natural guidance is needed so that users who enter the site can subscribe to web push notifications without any inconvenience.
To achieve this, you can expose notifications to encourage subscriptions at the desired timing , and this part is called “Subscription Notification Settings.”
In the settings section, you can set the text and buttons for that section.

In the case of our own domain push, when notifications are allowed, permission is requested as above.
In the case of alternative domain push, browser permission is requested in the push subscription pop-up window when notifications are allowed.

In the case of alternative domain push, even if the user clicks the allow notification button after requesting subscription notifications,
Our site cannot request browser permissions directly.

Therefore, a separate subscription pop-up window provided by DFINERY opens and
This pop-up window will request browser permission for web push notifications.

At this time, as with subscription notification settings, you can customize the pop-up window.
Set up colors and text that match your brand image so that users can grant permissions after allowing notifications. ☺️

Benefits of Each Push Type

1. First-party domain push : All website domain addresses must be HTTPS and has the following benefits :

a. You can send push messages using the domain name you own.
If the site address shown in the push message matches the brand domain, this can reduce confusion for some users.
b. After allowing web push notifications, a separate pop-up window is not required when requesting browser notification permission.

2. Alternative Domain Push : Removes restrictions on HTTPS, HTTP, and has the following benefits :

a. As mentioned, there are no restrictions on domains.
b. After allowing web push notifications, browser notification permission is requested in a separate pop-up window.
It can be customized to match your brand color.

Allow browser notification permission

Web push sends messages through the browser.
Therefore , messages can be sent only if the user's browser notification permissions are granted.

If the browser already has information about denying notification permissions,
When granting the following permissions , the user must manually set permission permissions.

- Example) Alternative domain push

The method of granting permission varies for each browser.
Typically, in the case of the Chrome browser, the user must grant permission by clicking the lock icon in the address bar.
You can edit this text in your browser notification permission settings.

Registering a Safari Certificate

A passwordless p.12 certificate is required to send push notifications to the Safari browser. [🤔How do I check?]

※ If you do not upload, push notifications cannot be sent to the Safari browser.

[[Quote:Warning:small]] You must register a p.12 certificate without a password.

Web Link Browser Open Policy

Push to our domain occurs when a user receives a web push notification.
You can choose whether to always open web links in a new window or open web links set in a tab that the user has open .
In order to utilize open tabs, the tabs opened by the user must be
Exactly matches the web link value you set, or Even the domain must match.

※ This policy is optional, and if not selected, it will always open in a new window.

[[Quote:Warning:small]] The Web Link browser open policy set in Settings will be applied to all web push messages that will be created.

What is Time To Live (TTL)?

TTL indicates the validity period for message transmission .
If the user is offline at the time the web push message is sent,
The message will be kept for a certain period of time and then the user can send it when online.

The default TTL setting is 7 days, but you can set it in days, hours, and minutes from 0 days to 4 weeks.
If you set a minimum of 0 days, the message validity period is '0'.
Messages will only be sent if the user is online and immediately reachable.

The default value set in Setting is applied to the TTL, but TTL can be reset for each message when creating a message.