Add EngageNudge from GTM. Verify before you go live.
If you already live in GTM, import the template and check the install in Preview before anyone gets a prompt. You still host the service worker on your origin. Chrome is picky about that, and I would rather say so up front.
Talk to usGoogle Tag Manager
Who it's for
Marketing and ops teams on larger sites who already run GTM and want a governed SDK install path without a custom deploy every time.
- Marketers who need consent-aware SDK init in the container
- Teams that want Preview diagnostics before production
- Sites that can host a same-origin service worker file
What the template handles
SDK init tag
Loads en-sdk.js with your site key, VAPID public key, and API URL from tag fields.
Consent gating
Waits for Consent Mode or CMP signals before init when required. Surfaces consent_not_granted in Preview.
Install diagnostics
Pushes engagenudge_install_diagnostic to dataLayer so you can catch missing SW or wrong origin early.
Supported setup path
- 01Download template.tpl from the EngageNudge dashboard Integrations tab, then import it in GTM
- 02Create a tag with site key and VAPID key from your dashboard
- 03Host /en-sw.js on your origin (standalone or merge into existing SW)
- 04Preview in GTM, then confirm green checks in Installation Doctor
Know when to nudge.
Honest boundaries
GTM can inject the SDK and relay consent. GTM cannot install a same-origin service worker. Web push still requires browser permission on your domain.
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.