.public-content{max-width:860px;margin:48px auto;padding:0 24px 64px;color:#242424;font:16px/1.65 Geist,Arial,sans-serif}.public-content h1,.public-content h2{font-family:"Instrument Serif",Georgia,serif;font-weight:400;line-height:1.15}.public-content h1{font-size:42px}.public-content h2{font-size:32px;margin-top:48px}.public-content h3{font-size:20px;margin-top:32px}.public-content a{color:inherit;text-underline-offset:4px}.public-content table{border-collapse:collapse;display:block;overflow-x:auto}.public-content td,.public-content th{padding:12px;border:1px solid #ddd}.public-content dt{font-weight:600}.public-content dd{margin:0 0 16px}.public-content nav{margin-top:48px;border-top:1px solid #ddd;padding-top:24px}.public-content-brand{font-weight:600;text-decoration:none}.public-content ul{padding-left:24px}@media(max-width:600px){.public-content{margin:24px auto;font-size:15px}.public-content h1{font-size:34px}.public-content h2{font-size:28px}}PIING

Reading Piing: AlertsWeb push

Piing: Alerts

In this guide

Enable shopper opt-in
Send a notification as push
Who receives it
What the push contains
Operational setup
Consent and expectations
Test before launch
Next steps

Search or browse documentation

Piing: Alerts 7 / 14

Web push

Offer opt-in browser notifications for public announcements, separate from your targeted on-site feed.

Web push is optional in Piing: Alerts. The feed remains the primary on-site experience. Shoppers can opt into browser notifications from the feed. Public announcements can then reach those subscribers when the card goes live.

Web push is separate from Piing Wallet messages. Browser push belongs to Piing: Alerts and requires browser permission. Wallet messages belong to the Apple or Google Wallet pass.

Enable shopper opt-in

Open Appearance.
Open Web push (browser notifications).
Turn on Let shoppers turn on browser notifications.
Set the opt-in title, body and button label, or keep the defaults.
Save.

The opt-in appears in the feed footer only when web push is configured for the deployment and the merchant has enabled it. The shopper must choose the prompt and accept the browser's own permission request. No subscription is created when permission is refused.

Send a notification as push

Open or create a notification.
Complete its title, body, link and image. Choose the Everyone audience.
Open Web push broadcast.
Turn on Also send this as a web push when it goes live.
Publish or schedule the notification.

A live card is eligible to send when published. A scheduled card becomes eligible when its start time arrives. The editor records completed broadcasts. Check the send status before publishing a duplicate card; receiving a push depends on the browser and its notification settings.

Who receives it

Web push broadcasts go to all opted-in browser subscribers, not to a selected customer segment. Only cards using the Everyone audience are eligible. Signed-in-only, signed-out-only, segment-targeted and personal restock cards are not broadcast. Keep private offers and customer-specific updates in the targeted on-site feed.

Browser or operating-system restrictions can prevent delivery. A stale or revoked subscription is removed when the push service reports it as gone.

What the push contains

The broadcast uses the notification's title, body, destination and image where supported. The browser decides the final visual treatment. Test on the devices your customers use. Chrome, Firefox, Edge and Safari use their respective push providers; a self-hosted push service is not supported.

Operational setup

Web push requires VAPID credentials on the Alerts deployment. If those credentials are not configured, the app keeps the shopper opt-in and per-notification broadcast controls disabled and sends nothing. This is an infrastructure setting, not a field the shopper supplies.

Consent and expectations

Browser permission is separate from email, SMS and analytics consent. Explain what shoppers will receive before asking them to subscribe. Use broadcasts sparingly for public launches or store-wide announcements. Shoppers can turn notifications off in their browser or device settings. Turning off new sign-ups in Appearance does not revoke an existing browser permission.

Test before launch

Subscribe in a supported browser on a test device.
Publish a test notification with web push enabled.
Confirm it arrives once and opens the correct destination.
Test a scheduled card.
Re-save the sent card and confirm it does not broadcast again.
Revoke browser permission and confirm the storefront does not pretend the subscription is still active.
Select a restricted audience and confirm the card cannot be broadcast. Test with controlled accounts, not a live customer list.

Next steps

Related guides

Was this guide helpful?

Next guide in Piing: Alerts

Segments and audiences

Build audiences with rules on tags, metafields, VIP tier, spend, and browse intent, or mirror segments in from Klaviyo and Ometria.

Still need a hand? Contact us