Web Push

Reach people when they are not looking at your site or dashboard. Web push sends native browser notifications to workspace members (for new live-chat messages) and to visitors on your website (from journey Web Push nodes).

Web push in 3 minutesTutorial · 2–4 min · Not recorded yet

Script to read

Hey everyone — in this video I want to show you web push in Leadara. There are two sides: alerts for your team when a visitor messages in live chat, and push messages you send from a journey to people on your website.

Let's start with the team side. Open Live Chat → Settings. You'll see Browser notifications for your team — it's on by default. That means when a visitor sends a message, every teammate who allowed notifications in their browser can get an alert, even if the dashboard tab is in the background or closed.

The first time someone opens the dashboard after this is enabled, the browser asks for notification permission — they need to click Allow. Leadara handles the rest automatically.

Now the visitor side — journeys. In Templates, create a Web Push template with a title and body. You can use the same personalization fields as SMS or email. Then in a journey, add a Web Push node and pick that template.

For the push to actually arrive, the visitor must have subscribed on your site — usually after they click an opt-in on your site and your developer enables push subscription with the small service worker file at your site root. You can download that file from the Leadara integration guide.

When the journey runs, Leadara sends the notification through the browser's push network. Clicks can open a URL you put in the template data.

That's web push — team alerts for live chat, and journey pushes for visitors who opted in on your site.

What you can do

• Alert workspace members when a visitor sends a new live chat message — configurable in Live Chat → Settings, on by default.
• Send Web Push messages from journeys using reusable templates.
• Personalize title and body with visitor traits and event properties.
• Log delivery in Web Push logs per user and template.

Team notifications (live chat)

1. In Live Chat → Settings, keep Browser notifications for your team enabled (default).
2. Each teammate opens the dashboard and allows notifications when the browser prompts.
3. When a visitor sends a message, members receive a notification with a preview and a link to the conversation.

Turn the toggle off if you only want in-app sounds while the dashboard is open.

Visitor notifications (journeys)

1. Create a Web Push template under Templates.
2. Add a Web Push node in a journey and select the template.
3. On your website, complete the visitor push setup below.
4. After the visitor opts in, your site calls leadara.subscribePush() (usually behind a button or after login).

Visitors who never subscribed will not receive journey pushes — the Web Push step is skipped (shown as Skipped in journey run history, not green Finished) and the run continues. Check Web Push logs for FAILED with No push subscriptions.

Visitor push setup on your website

This is separate from the main SDK snippet. Team live-chat alerts in the dashboard do not require hosting anything on your site.

1. Download the Leadara push service worker from your API base URL:

   https://api.example.com/leadara-push-sw.js

   (Use the same API base shown on Integrations → Install.)

2. Host the file at your site root — it must be available at:

   https://your-shop.com/leadara-push-sw.js

   Same domain as your pages (www vs non-www counts as different origins).

3. Subscribe after opt-in — ask for notification permission in context (after sign-up, order, or a settings toggle), then:

   const result = await leadara.subscribePush();

   When result is subscribed, that visitor can receive journey pushes.

4. Identify logged-in users so subscriptions follow the same profile as your analytics.

After the first opt-in, Leadara automatically ensures a browser subscription on each page load and after identify() when notification permission is already granted — it creates the subscription if missing and posts it to your workspace without a second prompt.

Optional: add data-auto-subscribe-push="true" on your SDK script tag to prompt for permission right after identify() for logged-in users (useful on admin or member-only areas).

Check a visitor's subscription

Open Users → pick a person → Messages. The Web push section shows:

• Whether they have an active browser endpoint registered for journey push
• Each endpoint (masked for privacy) and when it was last updated
• Recent journey push attempts with SENT or FAILED and any error (for example No push subscriptions)

The user Overview tab also shows Push subscription: Yes/No at a glance.

Tips

• Ask for notification permission in context — after signup or a meaningful action — not on first page load.
• Keep titles short; the body can carry the offer or update.
• Pair live-chat push with the existing inbox sound for teammates who keep a dashboard tab open.
• Test on Chrome or Firefox desktop first; Safari requires macOS Ventura+ or iOS 16.4+ with a added-to-home-screen PWA for web push.