Push Notifications Overview

What are web push notifications?

Web push notifications are messages that can appear on a visitor’s device—even when they are not actively browsing your site—after they have chosen to receive them. They are delivered through the browser’s push channel and can include a title, short text, and optional actions or links.

Unlike email or SMS, web push is tied to the browser and the site where the user opted in, so messaging stays contextual to your web presence.

Why use web push?

• Timely reach — Send updates, reminders, or offers when they matter.
• Re-engagement — Bring people back to your site or key flows.
• Direct surface — Notifications appear alongside other system alerts the user already uses.
• Consent-based — Users choose whether to subscribe, which supports clearer expectations than broad outbound channels alone.

What you need in practice

Effective web push setup usually involves:

• Permission — A clear moment when the visitor can opt in (or decline).
• Technical integration — Your site must load the HoodEngage Web SDK (and, for push, a service worker) so subscriptions and delivery work correctly.
• Configuration in HoodEngage — Site setup, prompts, tags, and campaigns aligned with how you want to message subscribers.

Requirements and exact steps depend on your stack; the guides in this section walk through each path.

Where to go next

Choose the guide that matches how your site is built:

• Web SDK instructions — Custom sites and manual integration (service worker, configuration).
• WordPress Push notifications — HoodEngage plugin on WordPress.
• Shopify Push notifications — HoodEngage app on Shopify.

For dynamic values used in prompts and messaging, see also Variables.