One plugin. Browser audience. First Nudge today.
Paste the plugin, pair the site, send a test to your own phone. We do not blast the list when you hit Publish. I have seen that habit. I do not want it here.
Talk to usWordPress
Who it's for
WordPress publishers, blogs, and content-led businesses that want permission-based browser reach without another notify-everyone workflow.
- Site owners who outgrew blast-on-publish habits
- Editors who want a Nudge Score hint before sending
- Teams that need honest install diagnostics, not silent failures
What the plugin handles
Secure pairing
A one-time code links your WordPress site to your EngageNudge workspace. Revoke anytime from the dashboard.
SDK and service worker
Injects en-sdk.js and same-origin en-sw.js routes on your domain so push can work on your origin.
Publish suggestions
Optional draft and score hooks when you publish. Send stays in EngageNudge; we do not auto-send from WordPress.
Supported setup path
- 01Create an EngageNudge workspace and choose WordPress as your platform
- 02Upload the plugin and paste your pairing code in Settings
- 03Open your site in a browser and allow notification permission
- 04Send a test Nudge from the dashboard and confirm with Installation Doctor
Know when to nudge.
Honest boundaries
The plugin connects your site to EngageNudge. Browser push still requires visitor permission. We do not silently replace unrelated service workers.
Requires an EngageNudge account. Invite-only; contact us for access.
Know when to nudge.
Know when a notification is worth sending.
The useful question is who should not get this one.