How web push delivery works

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.

The browser creates the subscription

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.

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.

What the platform stores

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.

What can invalidate it

Permission withdrawal, browser-data clearing, subscription replacement, an expired endpoint, or a permanent rejection from the push service.

Control boundary

The browser owns the permission prompt and subscription. PushNotifications.org can explain the request and record the result, but it cannot override a denial.

A campaign becomes an eligible-attempt list

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.

Subscription active?

No records that are opted out or permanently invalid.

Inside a contact window?

Recent promotional contact can suppress a new promotional attempt.

Allowance available?

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.

The payload is encrypted for one subscription

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.

The application server builds and signs

Creates the payload, encrypts it with the subscription keys, signs the request with the website's VAPID identity, and applies an expiry time.

The browser push service accepts or rejects

Validates the request and endpoint, returns a provider status, and queues an accepted message for the browser. Acceptance is not proof of display.

The subscriber browser receives the event

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 service worker handles display and click behavior

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.

Push event

Parse only expected fields, use a safe fallback, and keep asynchronous work inside event.waitUntil().

Visible notification

Show a specific title and message. Treat icons, images, badges, and actions as enhancements because presentation varies.

Notification click

Validate the destination, focus an existing same-origin window when appropriate, or open the intended HTTPS page.

Test a message in the notification decision lab

Reporting keeps transport evidence separate from attention

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.

Attempted
The worker created a provider request for an eligible subscription. This is the unit used for plan allowance.
Accepted
The push service accepted the request. Browser receipt, operating-system display, and human attention are still unknown.
Failed
The request failed before or during provider submission. A retry depends on whether the failure is temporary and the message remains useful.
Invalid endpoint
The provider indicated that the subscription should no longer be used. The record is retired instead of retried indefinitely.
Clicked
The site's click handler recorded an interaction and destination. A click is useful evidence but does not explain every conversion.

What happens after an attempt

Observed resultWhat it supportsNext action
Provider acceptsThe provider accepted a valid request for the endpoint.Record acceptance; do not claim display.
Permanent rejectionThe endpoint is no longer usable or authorized.Retire the subscription and stop retrying it.
Temporary provider failureThe provider or network could not complete the request now.Retry with backoff only while the message is still useful.
Click eventThe service worker observed a notification interaction.Open the intended page and record the click once.
No click eventNo click was recorded.Do not infer whether the notification was displayed or read.

Questions about the delivery boundary

Does a push service deliver directly to a person?

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.

Does an accepted Web Push request prove display?

No. Provider acceptance confirms that the push service accepted the request. It does not prove operating-system display, human attention, or a click.

Why are invalid subscriptions removed?

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.

Ready to test the complete path?

Register one HTTPS origin, install the service worker, create one current subscription, and verify each boundary with a test message.

Create a free account