Send Web Push composes a notification and delivers it to the people who have already subscribed. It is the second half of web push in Personyze — collecting subscribers is a separate campaign, covered in Web Push Subscription. If you have not built the opt-in prompt and installed the service worker yet, start there; this campaign has nobody to send to until you do.
In the panel: New campaign › Web Push › Send Web Push.
The steps
Four steps: Content, Target, QA and Performance.
Note the order — unlike most campaigns, Content comes first. You compose the notification, then decide who receives it.
1. Content — composing the notification
This step has two tabs: Message look and Timing.
Message look
A web push notification is rendered by the operating system, not by your page, so the fields map onto what the OS supports:
- Title — the headline. Required; the notification will not send without one.
- Body — the message text. Also required.
- Icon — the image shown beside the message, usually your logo.
- Badge — the small monochrome glyph some platforms show in the status bar.
- Image — a larger picture displayed inside the expanded notification, where the platform supports it.
- Action URL — where the visitor lands when they click. Send them to the specific thing the notification is about, not the homepage.
- Action buttons — optional extra buttons inside the notification, each with its own label and destination.
There are also delivery-behaviour options: a tag with replace and renotify (so a newer message can supersede an older one instead of stacking up), silent delivery, and vibrate.
Not every platform honours every field. Treat title, body, icon and the action URL as the reliable core, and the rest as enhancements.
Timing
Set the time frames and limits. While a user matches the audience, the notification can be sent to them once or repeatedly, according to what you configure here. This is what stops a recurring campaign from notifying the same person every day.
2. Target — who receives it
Narrow the subscriber base to the people who should get this message. All of Personyze’s targeting is available: behaviour on site, profile and CRM fields, interests, cart contents, segments.
Because a push notification interrupts someone outside your site, precision matters more here than in an on-site campaign. A badly targeted push does not just underperform — it costs you the subscription.
3. QA — before it goes out
Review the message and the audience, and check the forecast of how many subscribers currently match. A push cannot be recalled once sent, which makes this the one step worth being slow about.
4. Performance — after it goes out
Delivery and engagement for the campaign once it is running.
Sending recommendations in a push
Alongside the plain notification, Personyze offers two recommendation-driven push types:
- Web Push Send – Products — the notification is built around a product picked for that individual subscriber.
- Web Push Send – Articles — the same, for content.
These use the same recommendation engine as on-site widgets, so the item in the notification is chosen per person from their behaviour rather than being the same for everyone. They need a product or article catalog in place first.
Practical notes
- Say something worth interrupting for. Subscribers are easy to lose and impossible to win back — once someone blocks notifications, that decision sticks at the browser level.
- Land people on the relevant page. The action URL should point at the thing you mentioned.
- Use tag and replace for recurring campaigns, so a subscriber sees the current message rather than a pile of old ones.
- Set the timing limits deliberately. The default behaviour of a matching audience is to keep matching.
Related
- Web Push Subscription (Opt-In Prompt) — collecting subscribers, and the service worker setup.