Create a website connection
- Open Settings > Channels > Web Push as a workspace owner or admin.
- Name the website, choose its environment, and enter the exact HTTPS origin where visitors will subscribe. Use only one Web Push application per origin; staging and development need distinct origins.
- Import customer-owned VAPID keys or ask Wepy to generate a dedicated pair for this website.
- Use a mailto or HTTPS VAPID subject that your organization controls.
- If Wepy generates the keys, download or copy the one-time private-key backup before acknowledging it. Wepy does not reveal the private key again.
- If saving is interrupted, keep the form unchanged and retry the exact setup. Wepy safely recovers the original completed response instead of creating another website or another set of credentials.
Keep website credentials private
Each website connection belongs to the active workspace. Keep production and test origins separate, and never paste VAPID private keys, subscription endpoints, or browser key material into support messages.
Create a new connection when the origin changes
After a website gains subscriptions, you cannot change its origin, environment, service-worker path, or scope. Create a new connection if those settings need to change. You can still edit the connection name, branding, and permission-prompt copy.
VAPID rollover affects new enrollments only
A VAPID rollover changes the key used for new subscriptions. Save the one-time private-key backup before confirming. If the response is interrupted, keep the form unchanged and retry the same action to recover that backup. Existing subscriptions continue using their earlier keys, so rollover does not revoke an exposed old key. Pause the Push app if you suspect a key has been exposed.
Rotate signed-identity credentials with an overlap
Owners and admins can rotate the identity signing secret separately from VAPID keys. Copy or download the new secret to approved secure storage and acknowledge the backup before leaving. Update WEPY_PUSH_IDENTITY_SIGNING_SECRET on your backend before the overlap deadline shown in Wepy; the old secret works only until that deadline. Existing VAPID keys, subscriptions, and contact matches do not change.
Install and verify Web Push
- Generate a short-lived verification code, publish it as the exact plain-text contents of /.well-known/wepy-push-verification.txt on the configured origin, and keep the file available during the installation handshake. You may remove it after Wepy shows Verified.
- Download, review, and host the matching SDK and service-worker files on your configured website. Use version 1.0.1, replace both files together, and check the checksum shown by Wepy. Version 1.0.0 remains available but does not include the permission-prompt fix.
- Configure the versioned browser SDK with the public application ID, service-worker path, and short-lived verification token shown by Wepy.
- Call WepyPush.showPrompt from a meaningful, persistent Notification settings action. The soft primer uses your saved copy; native permission follows only its Allow click. Wepy never asks for browser permission during page load. Use subscribe directly only when your own UI provides the primer.
- Run Verify installation in Wepy and resolve any origin, SDK, service-worker, or configuration diagnostic that fails.
- Subscribe the exact test browser, run WepyPush.createTestDevicePairing() from a protected, explicit website action, and enter its single-use code in Wepy within 10 minutes. Then send a controlled test notification.
Make the verification file accessible
The verification file must be publicly accessible at the exact HTTPS address shown in setup, with no redirect. Wepy reads that file to confirm website ownership; supplying the code only in browser settings or a request header is not enough.
Subscription details stay private
Wepy shows only a device label, broad browser/platform capability, status, and timestamps in Settings. Subscription endpoints, authentication secrets, encryption keys, and raw user-agent strings stay hidden.
Pairing proves control of the current browser
Create the pairing code on the browser you want to test, then enter it in Wepy as an owner or admin. The code works once and only while that subscription remains valid. Creating a new code invalidates the previous one; entering a subscription ID alone cannot pair a browser.
Browser and iPhone/iPad compatibility
Web Push requires HTTPS, a service worker, and a supported version of Chrome, Edge, Firefox, or Safari. On iOS or iPadOS 16.4 and later, visitors must first add the website to their Home Screen before subscribing. Native mobile apps use the separate Mobile Push setup. Wepy shows general browser and platform labels, not device fingerprints.
Signed identity stays server-side
To associate a subscribed browser with a customer, mint a signed assertion only on your authenticated backend. Bind version 1, publicAppId, the exact subscriptionId returned by WepyPush.status() or subscribe(), externalId, a unique jti, iat, and an expiry no more than five minutes later; optional profile fields may be included. Return only the assertion to the browser and pass it to WepyPush.identify(). Never expose the identity signing secret in browser code.
Detach shared browsers before account changes
Before logout or account switching, wait for WepyPush.detachIdentity() before clearing the customer session. This prevents the shared browser from remaining linked to the previous customer. Show the permission primer again and require fresh Wepy consent for the next customer, even if browser permission is still granted. Then create a new signed assertion for the new subscription ID; do not identify the next customer automatically.
Test a campaign and read its results
After verification, create a Web Push campaign, select the website application, target all active subscribers or narrow by List or Segment, compose and preview the notification, test the exact saved notification on a reachable test browser, then send now or schedule. Results separates device attempts, push-service acceptance, signed presentation callbacks, click events, uncertain outcomes, failures, expirations, and skips without exposing endpoints or recipient identities. For Web Push, a presentation callback means showNotification() resolved; operating-system settings can still suppress visible UI, while a signed click is human-interaction proof.
Shared campaign tools, separate platform setup
Web and Mobile destinations now share the Push composer, app-scoped topics, reusable templates, automation sends, quiet hours, frequency controls, experiments, and results vocabulary. Browser setup remains separate because VAPID, service workers, and browser permission do not apply to native apps.
Pause safely without blocking privacy controls
Owners and admins can pause a Web Push website without deleting its installation or history. Pausing stops new subscriptions, controlled tests, and campaign sends, while existing browsers can still unsubscribe or detach identity. Resuming restores future activity after normal readiness checks and never launches a saved campaign automatically.