Step by step, grounded in exactly what the plugin does today.
Appushy turns the events your site already has — orders, enrollments, messages, new posts — into push notifications, with built-in Web Push and optional Appilix app delivery. These guides cover every screen and setting, free and Pro alike.
Activate the plugin and run the setup wizard.
2Turn on your channels, free Web Push included.
3Write, preview and send to your audience.
Install, connect your channels, and send your first push.
Automatic events, who's subscribed, and identity matching.
Delivery logs, common problems, and what Pro adds.
Install and activate Appushy the way you would any other WordPress plugin — from Plugins → Add New, or by uploading the zip file, then clicking Activate.
Right after activation, a short setup wizard walks you through turning on Web Push (works immediately, nothing to sign up for) and/or connecting an Appilix app, if you have one. Pick either, both, or skip the wizard entirely and set things up later from Appushy → Platforms.
Appushy also detects WooCommerce, Tutor LMS, and Better Messages automatically — each integration's notifications only turn on once that plugin is active. None of them are required just to install Appushy; new-post notifications work on any WordPress site with no other plugin at all.
Toggle it on and it works. Appushy generates its own encryption keys and installs the small background file browsers need to deliver notifications when your site isn't open — all automatically, on your own server. No account, no third-party service, no API key.
Click Configure any time to see your keys and the background worker's address — useful only if something stops working and you want to check what's there.
Appilix reaches your native Android/iOS app instead of a browser. Get these right on the Appilix side before connecting — skipping them won't break anything, but test pushes simply won't arrive until they're done:
Once that's done, go to Appushy → Platforms → Appilix → Configure and paste your App Key and API Key, both from your Appilix dashboard's Push Notification API panel. Save, then use the same panel's test field to confirm a push actually reaches a device.
Go to Appushy → Send. Write a title and message, see exactly how it'll look on desktop, Android, and iPhone before you send, then choose who gets it and where it goes.
Under Who receives it, send to everyone subscribed, or — on Pro — a saved segment. Under Where it goes, uncheck any connected channel to skip it just for this send.
Send a test to me (just your own device), Send now (goes out immediately), or Schedule for later (pick a date and time, optionally repeating).
Go to Appushy → Push Automation to see and toggle every notification each connected integration can send.
| Integration | Event | Free / Pro | Notes |
|---|---|---|---|
| WordPress Posts | New post, page, product, or course published | Free | Works on any WordPress site, no other plugin needed. Choose which content types notify in this panel. |
| WooCommerce | Pending payment, Processing, On Hold, Completed, Cancelled, Refunded, Failed | Free | All 7 statuses, no send caps. |
| Tutor LMS | Enrollment | Free | Sent automatically when a student enrols in a course. |
| Tutor LMS | Completion, Assignment graded, Course access expired | Pro | Visible with a padlock on the free plugin, with a sample preview you can try before upgrading. |
| Better Messages | Direct message | Free | Sent when someone gets a new unread direct message. |
| Better Messages | Group conversation, chat room, @mention | Pro | Direct messages stay free either way. |
Every event's text is editable — click Edit on any row to change the title and message, insert variables like the customer's name, and preview the result before saving.
New-post notifications get their own panel: pick which content types should notify, and optionally limit a send to one segment of your Web Push subscribers.
Appushy → Audience lists everyone who's opted in to Web Push on your site — searchable, exportable, with a breakdown of which browsers and devices they're using. There's no subscriber limit on any plan.
Appilix devices aren't listed here — Appilix keeps its own device list on its side, since it matches by identity rather than a subscriber record Appushy stores.
This section only applies to Appilix — Web Push subscribers don't need any identity matching, they're tracked automatically. Appilix delivers a push by matching an identity — an email address or a WordPress user ID — not a customer record in your store directly. Choose which one under Appushy → Settings → Identify customers by:
Each row shows a status:
Seeing the same event more than once isn't a duplicate: Appilix sends retry automatically — 30 seconds later, then 2 minutes, then 5 minutes — before giving up, with each attempt logged as its own row.
Queued means Appushy successfully handed the notification off — confirmation of delivery to Appilix or to each browser's own push service, not confirmation a phone or screen actually displayed it. If something stays Queued but never visibly arrives, that's almost always a delivery issue on the Appilix/browser side, not something Appushy's own log can diagnose further.
For Appilix, almost always because they haven't opened your app and been identified yet — the log shows "Not delivered — Hasn't opened your app yet" for these, the expected outcome, not an error. For Web Push, the usual cause is the subscriber's browser permission being revoked, or their device being offline for a long stretch — Appushy marks that subscriber Inactive automatically rather than retry forever.
That's WordPress's own background task scheduling (Action Scheduler), not Appushy — by default it only runs when someone visits your site, so a quiet site can see a short delay. For instant delivery regardless of traffic, set up a real server cron job: add define( 'DISABLE_WP_CRON', true ); to wp-config.php, then have your host run wp-cron.php on a real schedule. Manual sends aren't affected — those go out immediately.
Better Messages only checks for unread messages on its own schedule — Notification Interval (Better Messages → Settings → Notifications, default 15 minutes, floor of 1 minute) plus Offline Delay on the same page. Appushy sends once Better Messages itself decides to fire, and can't speed that up.
Yes, when identifying by email (the default). Appushy registers the order's billing email with Appilix automatically on the order-confirmation page, whether or not the customer has an account.
Every event has sensible default text with variables like the customer's name filled in automatically. Editing that text per event, and saving the edit so it's reused across sends, is a Pro feature.
Your Appilix App Key and API Key are never displayed after saving (masked in the UI) and never appear in the notification log. Web Push delivers directly from your server to each browser's own push service — never through any Appushy-operated server.
The free plugin is a complete, unlimited tool on its own — no subscriber caps, no send-rate limits, no channel-count limits, ever. Appushy Pro adds:
See Pricing to purchase a plan.
Once you've purchased, log into your Appushy account to find everything you need:
appushy-pro plugin zip file.
appushy-pro zip the same way you would any WordPress plugin.Once active, the same screen shows your plan and a Deactivate button — use that if you ever need to free up a site slot before activating the license somewhere else.