What the browser returns
An endpoint URL, a public encryption key, and an authentication secret. Together they identify a delivery route and let the sender encrypt a payload for that browser.
A web push notification crosses four systems: your website, your application server, a browser-operated push service, and the subscriber's browser. PushNotifications.org coordinates the send, but browser permission and final presentation remain under browser and operating-system control.
A site cannot manufacture permission or import an email list as browser subscribers. A visitor must grant notification permission in a supported browser context, and the browser returns an origin-bound subscription.
An endpoint URL, a public encryption key, and an authentication secret. Together they identify a delivery route and let the sender encrypt a payload for that browser.
The subscription record, website origin, consent context, state, timestamps, and application-server key identity. Raw key material is protected and never treated as a marketing profile.
Permission withdrawal, browser-data clearing, subscription replacement, an expired endpoint, or a permanent rejection from the push service.
The browser owns the permission prompt and subscription. PushNotifications.org can explain the request and record the result, but it cannot override a denial.
Before any provider request is created, the campaign needs approved copy, a valid HTTPS destination, a registered website, and a send time. The delivery worker then evaluates each subscriber separately.
No records that are opted out or permanently invalid.
Recent promotional contact can suppress a new promotional attempt.
The campaign pauses when the configured monthly allowance is exhausted.
These checks are product controls, not Web Push protocol rules. Read the frequency-cap design guide for the policy logic and edge cases.
For every eligible subscriber, the application server creates a Web Push request for that subscription's endpoint. The visible payload is encrypted before it leaves the sender; the push service routes ciphertext and does not need the title or message body.
Creates the payload, encrypts it with the subscription keys, signs the request with the website's VAPID identity, and applies an expiry time.
Validates the request and endpoint, returns a provider status, and queues an accepted message for the browser. Acceptance is not proof of display.
Wakes the correct service worker when possible, decrypts the payload, and gives the worker a short execution window.
See the payload encryption guide for the key agreement and content-encoding details, or use the SDK and API documentation to implement the send path.
The site's service worker receives the push event and calls the Notifications API. The browser and operating system then control truncation, grouping, sound, placement, and whether the notification is visible in the current device state.
Parse only expected fields, use a safe fallback, and keep asynchronous work inside event.waitUntil().
Show a specific title and message. Treat icons, images, badges, and actions as enhancements because presentation varies.
Validate the destination, focus an existing same-origin window when appropriate, or open the intended HTTPS page.
A trustworthy report does not label every accepted provider request as “delivered.” PushNotifications.org records the evidence it actually has and leaves unsupported conclusions out.
| Observed result | What it supports | Next action |
|---|---|---|
| Provider accepts | The provider accepted a valid request for the endpoint. | Record acceptance; do not claim display. |
| Permanent rejection | The endpoint is no longer usable or authorized. | Retire the subscription and stop retrying it. |
| Temporary provider failure | The provider or network could not complete the request now. | Retry with backoff only while the message is still useful. |
| Click event | The service worker observed a notification interaction. | Open the intended page and record the click once. |
| No click event | No click was recorded. | Do not infer whether the notification was displayed or read. |
No. The application server submits an encrypted request to the push service named by the browser subscription. The browser then receives a push event and its service worker decides how to display the notification.
No. Provider acceptance confirms that the push service accepted the request. It does not prove operating-system display, human attention, or a click.
A permanent provider response means the endpoint should no longer be used. Retiring it prevents repeated failed attempts and keeps the active audience count useful.