Web Push Notifications overview

Getting started

Choose how to integrate the Web Push SDK into your HTTPS website:

• Web push SDK 3.0 - main integration guide, loaded from the Pushwoosh CDN
• Usage with npm - install the SDK as an npm package instead

Panel-managed vs. snippet-configured

A Web platform is either snippet-configured (the SDK reads autoSubscribe, subscribeWidget, and similar keys from your init call) or panel-managed (the Control Panel’s Web SDK configuration card owns those same keys instead, once you click Move the settings here). Moving settings to the panel is one-way - on an application already using the unified web platform, there’s no switching back. See Web push SDK 3.0 for where to find this card.

Subscription UI

Invite website visitors to opt in to push notifications:

• Subscription widget - a prompt and a launcher bell configured together, the recommended starting point for a new integration
• Manage user consent - control when the SDK asks for permission
• Push subscription button - legacy, superseded by the Subscription widget’s bell
• Custom subscription Popup - legacy, superseded by the Subscription widget’s prompt

Alternative integrations

Ways to add web push without the full SDK setup above:

• Chrome and Firefox web push for HTTP websites - for a site without HTTPS
• AMP web push - for AMP pages, Android only
• Web push via Google Tag Manager - no direct code changes to your site

Additional features

Web inbox widget - an on-site message inbox, reaches visitors who haven’t granted push permission

Support and community

Have questions or problems with the Pushwoosh SDK? Reach out to our support team!