1. Home
  2. Blog
  3. Progressive Web App (PWA)

Schedule WordPress Push Notifications and Send Them Only to the Right People

For most of its life, a manual push notification in a WordPress PWA had two settings that you could not change: it went to every subscriber, and it went right now. That is fine for “We just published our annual report”. It is a poor fit for a flash sale that only ships to two countries, a lesson reminder that only paying members should see, or an image-heavy announcement that iPhones will display without the image anyway.

Progressify 1.5.0, released on WordPress.org on 18 October 2026, changes both. Its changelog lists a new option to schedule a manual push for later, and choose who receives it by login status, role, device, operating system or country. This guide walks through three real use cases for that feature, with the groundwork to do first and the mistakes worth avoiding, so you can schedule WordPress push notifications that reach the right people at the right time instead of everyone at once.

What changed in Progressify 1.5.0 for push

Several items in the 1.5.0 release notes touch push notifications. Here they are in plain terms.

Change in 1.5.0What it means for you
Schedule a manual push for laterWrite the message when you have time, send it when your audience is awake
Choose recipients by login status, role, device, operating system or countryOne list, many audiences, without separate plugins or lists
Subscriptions are checked before they are savedOnly known push services are stored, so your list holds real subscribers
Incomplete subscription keys are turned away, repeated attempts are slowedFewer junk rows from broken or abusive requests
Messages and app short names are shortened on character boundariesPortuguese, Cyrillic, Georgian, Chinese and other scripts stay intact when trimmed
Install and push prompt wording can be translatedLeave a field blank for the translated default, or write your own text and let WPML or Polylang translate it
Automatic notifications are sent in the background in batchesNew content, WooCommerce, BuddyBoss and Fluent Community automations finish with a sent and failed summary

The current documentation still describes manual sends as going to every subscriber, so treat the release notes as the newer source until the docs catch up.

Groundwork before you schedule anything

Targeting can only work with what your subscriber list knows. Spend ten minutes here first.

Look at the subscriber list

Sending happens on Progressify > Overview, below the subscriber list. Every subscription appears there with the country, operating system, browser and date it was created. That list is your audience map:

  • If almost nobody shows iOS, remember why: iOS only delivers Web Push to sites the visitor has added to the home screen, and only on iOS 16.4 or later. An iPhone user browsing in Safari cannot subscribe.
  • If the list is empty, nothing you schedule will go anywhere. The docs say the cause is almost always that no subscription control is enabled or the site is not on HTTPS.

Country comes from a server side lookup: the WordPress.org listing explains that Progressify resolves the IP address to a country through GeoJS when someone subscribes, and stores the country only.

Subscribe on your own devices

The documentation is blunt about this: a sent notification cannot be undone or edited. Subscribe on your own phone and laptop so you can see a real delivery. With targeting, you can now aim a test at a narrow audience you are part of, for example your own country and device type, before you schedule the full send.

Check the clock and the delivery settings

Confirm the site timezone under Settings > General is correct, then compare the scheduled time shown in the compose form with your own clock before you save. Two delivery settings on Progressify > Settings > Push Notifications matter more once sends are scheduled:

  • Time To Live (TTL): seconds a push service keeps trying to deliver to a device that is offline. The default is 2,419,200 seconds, which is four weeks. A sale that ends tonight should be a few hours, not four weeks, or it arrives after the sale is over.
  • Batch Size: default 1,000. Delivery is chunked so a large list does not exhaust PHP memory. Lower it to 250 or 500 if sends time out on shared hosting.

Use case 1: A WooCommerce flash sale by country

You run a store that ships to Georgia and Germany, and the sale starts at 9:00 in the morning. A single send at one time would land at breakfast in one country and an hour or more off in the other, and it would reach subscribers in countries you do not ship to at all.

The setup

  1. Write one notification per country, each targeted by country, and schedule each one for 9:00 local time in that country.
  2. Keep the Notification Title under about 50 characters. Android and desktop both truncate longer titles, and the truncation lands mid-word.
  3. Assume about 120 characters of the Notification Message are visible before it collapses. Put the discount and the deadline first.
  4. Set the Notification URL to the sale category or the product, never the homepage.
  5. Add a Notification Image if it helps. It shows when the notification is expanded on Android and desktop Chrome; iOS and most other platforms ignore it.
  6. With Pro, add up to two Action Buttons, each with its own text and URL, for genuinely distinct choices such as “Shop the sale” and “See delivery times”.
  7. Lower the TTL so a delayed device does not receive a sale alert after the sale ends.

Why the 1.5.0 text handling matters here

If your Georgian notification runs longer than the space allowed, Progressify 1.5.0 trims it on a character boundary, so the text stays intact. You should still write short, because a trimmed message still loses its ending.

What to leave to automations

Price drops, sale prices and back in stock alerts are already WooCommerce automations in Pro, and they fire per event with no manual send. Keep the scheduled manual push for the planned campaign and let the automations carry routine store traffic. Sending both for the same product on the same morning reads as spam.

Use case 2: A membership or course site by login status and role

A membership site has at least two audiences on the same list: people who are signed in and paying, and visitors who subscribed while browsing but never joined. They need different messages.

Login status

Target logged in subscribers with things only members can use, such as “Module 4 is open”. Target logged out subscribers with a reason to join, such as a free sample lesson.

If your site only ever wants members on the list, the Logged In Users Only setting on the push tab shows subscription controls only to signed-in visitors. That keeps the list member-only from the start, and login status targeting becomes less important.

Role

Roles make targeting precise. WooCommerce adds a customer role, and membership plugins often add one per tier. Target a role when the message is only true for that group:

  • “Your renewal is coming up” to the role that renews.
  • “New advanced workshop” only to the tier that includes it.
  • “Staff meeting moved” to an internal role, if staff subscribe too.

Schedule member reminders shortly before the event and set the TTL to match. A reminder that arrives after the session starts is worse than none.

Community sites

BuddyPress and Fluent Community automations already target the relevant people per event, such as the members of a space. Use scheduled manual sends for announcements that cross spaces, not for activity the automations already cover.

Use case 3: A publisher by device and operating system

A news site or blog has a different problem: how the notification looks depends on the device.

Send image-rich and text-only versions

Because the notification image is supported on Android and desktop Chrome but ignored by iOS and most other platforms, you can now write two versions of a big announcement:

  • Android and desktop: a strong image, a short title, a message that complements the picture.
  • iOS: no reliance on the image, so the title and message must carry the whole story on their own.

Time sends by device

If your analytics show desktop readers arriving at lunch and mobile readers in the evening, schedule two sends rather than one compromise.

Reach the people who installed the app

iOS subscribers are, by definition, people who added your site to their home screen, since that is the only way iOS delivers Web Push. Targeting iOS therefore reaches installed app users on iPhone and iPad.

Targeting options at a glance

Target byGood forWatch out for
Login statusMembers versus visitorsVisitors who forget to log in on a second device
RoleTiers, customers, staffRoles created by plugins you later remove
DeviceDesktop versus mobile timing and layoutLaptops with touch screens and tablets
Operating systemiOS home screen users, image versus text versionsSmall groups that make a send look like it failed
CountryShipping regions, local time, local offersVPN users and travellers

Keep the list clean so targeting means something

A segment is only as good as the rows in it. Progressify 1.5.0 checks subscriptions before they are saved, so only known push services are stored, turns away incomplete subscription keys, and slows repeated attempts from the same visitor.

On your side:

  • You can remove individual subscribers on the overview page. The docs note this deletes the subscription rather than hiding it.
  • A steady small failure count is normal. Subscriptions expire when a browser is uninstalled, site data is cleared or the browser rotates the endpoint.
  • Changing domain invalidates subscriptions, because a Web Push subscription is bound to its origin. Moving hosts with the same domain and database keeps them.

Translate the prompts that build the list

Targeting by country is wasted if half your visitors never subscribe because the prompt is in the wrong language. In 1.5.0, install and push prompt wording can be translated. Leave a field blank to use the translated default, or enter your own text and WPML or Polylang can translate it. If you use the Pro Notification Prompt, say what you will send and roughly how often. The docs point out that “Order updates and shipping alerts” earns more subscriptions than “stay updated”.

A scheduling checklist

Before you press schedule, run through this list:

  1. The subscriber list on Progressify > Overview contains the audience you are targeting.
  2. You are subscribed on a device inside that audience and have seen a real test delivery.
  3. The title is under about 50 characters and the key point sits in the first 120 characters of the message.
  4. The URL opens the exact page the message is about.
  5. The TTL matches how long the message stays true.
  6. The site timezone and the scheduled time are both correct.
  7. No automation will send something similar to the same people the same day.
  8. Persistent is only switched on if the message genuinely needs a response.

The docs’ advice still applies: send when something happened, and remember that a visitor who blocks notifications cannot be asked again.

Free and Pro

The free Progressify plugin on WordPress.org includes push notifications, the notification button, the welcome notification, manual sending, the subscriber list, TTL and batch size. Pro adds the branded notification prompt, action buttons, and every automation for new content, comments, WooCommerce, BuddyPress and Fluent Community. The 1.5.0 changelog does not say which plan includes scheduling and targeting, so check the compose form on your own install after updating.

Pro is part of the DaftPlug membership: one license covers Progressify, Lightify, Generatify, Crownify and Snapshotify. Plans start at $37.99 a year for one site and differ only in the number of site activations, with a 14-day money-back guarantee. Compare them on the DaftPlug pricing page.

If you have not sent a manual notification from wp-admin before, start with our guide to sending WordPress PWA push notifications from your own dashboard, then come back and schedule your first targeted send.