Web push delivery and analytics

Interpret push-service responses, choose retry behavior, measure the full funnel, segment responsibly, and diagnose delivery failures.

Build an event model before a dashboard

StageEvidenceWhat it does not prove
EligibleThe endpoint passed audience, preference, and frequency rules.That the subscription is still valid.
AttemptedThe application created a send attempt.That a network request completed.
AcceptedThe push service returned a successful response.That the device received or displayed it.
ClickedThe notification-click flow or destination recorded a campaign token.That every click produced a useful outcome.
ConvertedA defined downstream action was attributed under a stated window.That push alone caused the action.

Keep a minimum send-attempt record

Identity
Internal site, campaign, subscription-record, and attempt identifiers that can be joined without logging the complete push endpoint.
Eligibility
The audience rule, preference state, frequency decision, and suppression reason evaluated when the worker selected or skipped the record.
Request
Attempt time, VAPID-key version, TTL, topic or urgency when used, payload schema version, and encrypted body size.
Response
Push-service host, HTTP status, bounded response metadata, latency, and the operational class assigned by your system.
Lifecycle action
Whether the endpoint remained active, was retired, entered delayed retry, or was held for configuration review.

This record supports incident reconstruction without turning logs into a second subscription database. Restrict access and retention because endpoint-related metadata can still reveal relationships and sending activity.

Classify responses before choosing retries

Group push-service responses by operational meaning. A malformed request needs correction. Authentication failures need key or token investigation. Rate limits need delayed, bounded retry. Server errors may be transient. An expired or invalid subscription needs endpoint retirement. Never retry every non-success response with the same schedule: that wastes capacity and can turn one bad endpoint into recurring noise.

Response classImmediate actionRetry decision
Malformed request or payloadStop the affected campaign path and inspect serialization, required headers, encryption, and size.Do not retry unchanged input. Release a corrected request only after a reproducible test passes.
Authorization or sender identity failurePause the affected key population and compare the VAPID audience, key, token lifetime, and server clock.Resume only after configuration evidence changes; repeated requests do not repair authorization.
Rate limitHonor available retry guidance, reduce concurrency, and protect other tenants or campaigns from the same queue pressure.Use delayed, capped attempts with jitter and a deadline tied to message usefulness.
Temporary provider failureRecord the provider and time window, check whether the failure is isolated, and preserve the original attempt.Retry within a bounded policy only while TTL and product value remain.
Expired or unknown subscriptionRetire the endpoint and exclude it from later campaigns.Do not retry. Allow the browser to create and submit a new subscription through the normal product flow.

Choose TTL from the usefulness window

RFC 8030 requires a TTL header and allows a push service to retain a message for less time than requested. Set TTL to the period during which the message remains useful. A live-event alert may deserve minutes; a weekly digest may remain useful for hours. If a price or status can change again, design the destination to show current truth even when the notification text reflects an earlier moment.

Use denominators that match the question

Permission grant rate starts with people who were actually shown a meaningful opt-in opportunity. Push-service acceptance rate starts with attempts. Click-through rate should clearly state whether the denominator is attempts or accepted sends. Downstream conversion should define both the eligible action and attribution window. Opt-out and permanent-failure rates belong beside clicks because they reveal channel cost.

Worked reporting example

A campaign selects 12,000 eligible subscriptions. Frequency and preference rules suppress 1,500 before delivery, so the worker makes 10,500 attempts. Push services accept 10,080 requests, reject 120 permanently, and return temporary failures for 300. The campaign records 620 notification clicks and 240 completed destination actions within its stated attribution window.

  • Suppression rate: 1,500 divided by 12,000 eligible records. This describes policy pressure before a request exists.
  • Acceptance rate: 10,080 divided by 10,500 attempts. This describes push-service responses, not display.
  • Click rate by attempts: 620 divided by 10,500. Label the denominator rather than publishing an ambiguous “CTR.”
  • Action rate by clicks: 240 divided by 620. Also report action rate by attempts when evaluating the full channel.
  • Endpoint retirement rate: 120 divided by 10,500 attempts. Review it beside opt-outs and inactivity, not as a delivery success metric.

The values are illustrative. A production report must state its time zone, attribution window, deduplication rule, late-event policy, and whether bots or repeated clicks are excluded.

Diagnose from left to right

  1. Confirm the browser is capable, permission is granted, and a current subscription exists.
  2. Confirm the endpoint belongs to the correct site and VAPID key population.
  3. Inspect the exact request, TTL, encryption, and push-service response.
  4. Inspect the service-worker push event and notification-display call.
  5. Inspect operating-system settings, Focus modes, click handling, and destination behavior.

Use the protocol as the reporting boundary

RFC 8030 defines TTL, push-service behavior, and protocol responses. The W3C Push API describes delivery to the active worker. Keep reporting language within what those stages actually establish, then use your own click and destination events for the rest.

Trace evidence from send to outcome

Use the status-code guide during incidents, the metrics and segmentation guides during planning, and the diagnostic when a trace breaks.

  1. Web push status codes and retry decisions

    Turn push-service HTTP responses into safe retry, pause, or endpoint-removal decisions without inflating delivery reports.

  2. Web push TTL, urgency, and topic replacement

    Choose Web Push TTL, urgency, and topic replacement values from a message's useful lifetime, offline behavior, and stale-message risk.

  3. Push notification metrics without vanity reporting

    Measure attempted, accepted, clicked, unsubscribed, expired, and downstream outcomes with the correct denominator for each campaign.

  4. Push notification segmentation without guesswork

    Build segments from declared preferences and recent behavior, set minimum audience rules, and evaluate incremental value honestly.

  5. Debug web push notifications step by step

    Trace permission, registration, subscription, server response, push events, notification display, and click handling in order.