Publishing and sharing
Send web push notifications to app subscribers
Where notifications are available, enable visitor subscriptions in Publishing. Visitors must separately choose Enable notifications and grant browser permission. You can then review and send a message to subscribers with a live page as its destination. A send accepted by a push service does not guarantee a device displayed it.
Check the prerequisites
Publish Home, enable the app link, and save its settings. In Publishing → Notifications, check the availability message. Notifications need platform support and a dedicated app address or connected custom domain; the shared Div-idy website address cannot supply project-specific notification permission. Select Allow visitor subscriptions and choose Save notification settings. If setup is unavailable, the ordinary app link can still be useful for opening the app.
Let visitors opt in on their device
Have visitors open the saved app link directly and choose Enable notifications, then allow the browser’s permission request. On supported iPhones and iPads, they must first add the app to their Home Screen and open its icon. Installation alone does not subscribe them. A visitor can choose Turn off notifications in the app or manage permission in their browser or device settings.
Write a useful message and review it
After at least one visitor subscribes, enter a Notification title of up to 80 characters and a Message of up to 240 characters. Choose a Live destination. For example, “New weekly plan” can open a published planner page with the new details. Choose Review notification, check the wording, destination, and subscriber count, then choose Send notification. A sent message cannot be recalled.
Read status without assuming delivery
The status reports attempts accepted by push services, failures, expired subscriptions, and skipped subscriptions. Use Refresh distribution for updated status. Acceptance is not a delivery or read receipt: browser support, permission, network conditions, and device settings affect the result. Test with an opted-in device and confirm that tapping the notification opens the intended live page. An unavailable destination should be fixed before sending another message.
Respect current limits and retry carefully
The current service supports up to 500 subscriptions per app, requires at least a minute between new sends, and permits up to 20 broadcasts in a rolling 24 hours. Wait for an active send to finish. If a request cannot be confirmed, follow the interface’s instruction to review the same message again for a safe retry. Changing the app’s address can require visitors to subscribe again on the new address.