Getting started

EngageNudge is the web-push product that decides whether a message is worth sending, who should receive it, and who should be left alone.

This guide gets you from an empty workspace to a notification on a phone or browser you control.

What you need

An EngageNudge account. Signup is invite-only during soft launch. If you cannot sign in, contact us.
A site on HTTPS. Browser push does not work on plain HTTP.
Access to add a script, a WordPress plugin, or a Google Tag Manager tag on that origin.

1. Create your site

Sign in to the dashboard.
Complete setup: site name, origin (https://…), and how you will install (script, WordPress, or GTM).
Open Integrations. Copy the install snippet, site key, and VAPID public key.

The origin you enter must match the site people actually visit. Pairing and Install Doctor are origin-bound.

2. Install on your origin

Pick one path. Details live in Install and the developer articles.

Script: add the snippet and serve /en-sw.js on the same origin. See JavaScript SDK.
WordPress: pair the plugin. It injects the SDK and serves the worker. It never live-sends on publish.
GTM: import the SDK template. GTM cannot install a same-origin service worker. You still host /en-sw.js.

3. Confirm install

Open a public page on your origin. In the dashboard, run Install Doctor. You want the SDK loaded, the worker reachable and controlling the page, and VAPID present.

If something is red, start with Troubleshooting.

4. Register a test device

On a browser or phone you control, allow notifications for your site. Mark that subscriber as a test device in the dashboard.

A live send to your whole audience is a later step. A test Nudge only hits test devices and does not start a trial.

5. Send a test Nudge

Open Campaigns (or compose from a suggested story).
Write a short title and body, or use a URL preview.
Send a test. You should see the notification on the test device.

When that works, you can send to a real audience. Accept the DPA in Settings first. See Send a Nudge.