AJO Web Push custom data is absent from the service worker payload

Delivery success does not prove payload completeness. In a new Experience League question, a team says an AJO Web Push notification reaches the browser while keys configured under Custom data do not appear in the raw payload observed by its service worker. An Adobe employee asks whether this feature is supported for Web Push; the thread does not provide a confirmed answer. That makes a small compatibility test the right next step.

Capture the exact wire payload

Use a staging push configuration and one consented test browser. Record the channel, browser, service worker version, AJO surface and template version. Log the raw push event data before parsing or application transforms, with personal information removed. Compare that capture with the configured key names and values; a UI preview is not a wire-level assertion.

Check the documented scope

Adobe’s push design guide describes custom data in relation to mobile application configuration. Do not assume that a control visible in the authoring UI has identical Web Push delivery semantics. Ask Adobe Support for the supported Web Push contract for the exact channel and version, attaching the minimal configuration and redacted payload. Separate unsupported behavior from a serialization or service worker parsing problem.

Design a safe fallback

If the browser cannot reliably receive those keys, do not make notification navigation or consent handling depend on them. Use a supported destination URL or a server-side lookup keyed by a non-sensitive identifier, with expiration and access control. Retest in each target browser before rollout; browser behavior and push providers can differ.

Adovo’s view

A notification is an interface contract, not a creative asset alone. The custom field matters only if it survives delivery and can be read safely where the user acts. Release on the captured payload, not on a filled-in authoring form.