Self-hosted web push with unlimited subscribers, opt-in popup &amp; click stats — free. AI digests &amp; WooCommerce automation with Pro.

PushAI – Self-Hosted Web Push Notifications

🚀 <a href="https://demo.wpushai.com/" rel="nofollow ugc">Try the live demo</a> — explore the PushAI admin panel without installing anything. | 💎 <a href="https://wpushai.com" rel="nofollow ugc">Upgrade to PushAI Pro</a> — AI digests, WooCommerce automation, and more.
PushAI turns your WordPress site into a re-engagement channel. Visitors subscribe with one click, and you reach them directly in their browser — even when your site is closed — using the native Web Push standard. No third-party SDK, no per-subscriber pricing, no external delivery service: notifications go straight from your own server using your own <a href="https://datatracker.ietf.org/doc/html/rfc8292" rel="nofollow ugc">VAPID</a> credentials, generated automatically on activation.
Everything stays on your site. Subscribers live in your own database, delivery runs through a background queue so large sends never block your site, and every push link is tagged with UTM parameters automatically so traffic shows up correctly in Google Analytics and your other reporting tools. The free plugin covers the full lifecycle out of the box: subscribe button, a customizable opt-in popup, automatic notifications for posts and custom post types, a manual composer, per-user targeting, click tracking with 7-day dashboard stats, delivery history, and GDPR export/erasure. With the optional email fallback, registered users who haven&#8217;t subscribed to browser push still get the same notification as a clean HTML email — so no one is left out.
PushAI is device-aware: when a logged-in visitor subscribes, PushAI keeps one active subscription per device type — one mobile, one desktop — so the same person can opt in independently on each device and receive notifications on whichever ones they enabled. Stale and duplicate subscriptions are pruned automatically.
PushAI Pro adds the three things self-hosted push plugins almost never offer out of the box:
<ul>
<li>AI-summarized post digests, powered by OpenAI, Google Gemini, xAI Grok, DeepSeek, or any OpenRouter model — with a template fallback so digests always send, even without an API key.</li>
<li>Deep WooCommerce automation — order and stock alerts, order-status updates, abandoned-cart reminders, cross-sell follow-ups, and trending-product pushes.</li>
<li>A built-in Progressive Web App (PWA) — an installable manifest and service worker, so visitors can add your site to their home screen without a separate PWA plugin.</li>
</ul>
<blockquote>
Actively developed. New automations, AI providers, and WooCommerce flows ship regularly, and every release is documented in the changelog below. Feature requests and feedback directly shape the roadmap.
</blockquote>
<h4>Why choose PushAI?</h4>
<ul>
<li>You own your subscriber list. Subscriptions live in your WordPress database, never on a third-party platform.</li>
<li>Unlimited subscribers and notifications — on Free and Pro. No per-subscriber pricing, no monthly send caps.</li>
<li>No third-party SDK or delivery service. Native Web Push + your own VAPID keys, straight from your server.</li>
<li>Transparent, flat pricing. Free stays free forever; Pro is one flat price no matter how big your audience gets.</li>
<li>AI digests, built in (Pro). Summarize your latest posts and send them on a schedule, across multiple AI providers.</li>
<li>WooCommerce automation (Pro). Order, stock, status, abandoned-cart, cross-sell, and trending-product pushes.</li>
<li>Built-in PWA (Pro). Make your site installable — no separate PWA plugin required.</li>
</ul>
<h4>Free vs Pro</h4>
Both plans include unlimited subscribers, unlimited notifications, the self-hosted setup, and the developer API. Pro adds automation, AI digests, WooCommerce, the built-in PWA, and analytics on top — you only pay for the automation and AI layer, not for audience size.
Free — $0 forever
<ul>
<li>One-click subscribe button (shortcode)</li>
<li>Customizable opt-in popup (permission prompt)</li>
<li>Automatic new-post notifications</li>
<li>Custom post type automation</li>
<li>Click tracking &amp; 7-day dashboard stats</li>
<li>Manual notification composer</li>
<li>Per-user / specific-subscriber targeting</li>
<li>Separate mobile &amp; desktop subscriptions</li>
<li>Guest subscriptions</li>
<li>Email fallback for users without a push subscription</li>
<li>Automatic VAPID key generation</li>
<li>Background delivery queue with retries</li>
<li>Automatic UTM link tagging</li>
<li>Delivery history &amp; status</li>
<li>Privacy / GDPR export &amp; erasure</li>
<li>Developer API (functions + action hooks)</li>
</ul>
Pro — $21/year — everything in Free, plus:
<ul>
<li>Scheduled AI digests (OpenAI, Gemini, Grok, DeepSeek, OpenRouter + template fallback)</li>
<li>WooCommerce order &amp; stock alerts</li>
<li>WooCommerce order-status &amp; customer notes</li>
<li>Abandoned-cart reminders</li>
<li>Cross-sell follow-ups</li>
<li>&#8220;Trending Today&#8221; (post &amp; product daily-view alerts)</li>
<li>Built-in PWA (installable manifest + service worker)</li>
<li>Statistics &amp; analytics (7/30/90-day, CTR, most-clicked links, per-category performance, digest conversion)</li>
<li>Site-management admin alerts (pending comments, posts awaiting review, published posts, new subscribers)</li>
<li>Comment notifications (authors &amp; replies)</li>
</ul>
<a href="https://wpushai.com" rel="nofollow ugc">Upgrade to PushAI Pro</a>
PushAI is developed and maintained by <a href="https://wpushai.com" rel="nofollow ugc">PushAI</a>.
<h3>Shortcode</h3>
Place a subscribe button anywhere with:
<pre><code>[pushai_button]
</code></pre>
Optional attributes:
<ul>
<li><code>label</code> — default button text.</li>
<li><code>on</code> — text shown after notifications are enabled.</li>
<li><code>blocked</code> — text shown when the visitor has blocked notifications.</li>
<li><code>align</code> — <code>left</code>, <code>center</code>, or <code>right</code>.</li>
<li><code>class</code> — extra CSS classes.</li>
</ul>
Example:
<pre><code>[pushai_button label="Enable browser notifications" align="center"]
</code></pre>
In PHP templates:
<pre><code>&lt;?php echo do_shortcode( '[pushai_button]' ); ?&gt;
</code></pre>
The shortcode is also shown on the PushAI → Settings screen with a copy button.
<h3>Developer API</h3>
Queue a notification from a theme or plugin:
<pre><code>pushai_trigger_notification( array(
 'title' =&gt; 'Title',
 'body' =&gt; 'Message',
 'url' =&gt; home_url( '/' ),
 'image' =&gt; '',
) );
</code></pre>
The same notification can be triggered with a WordPress action:
<pre><code>do_action( 'pushai_send_notification', array(
 'title' =&gt; 'Title',
 'body' =&gt; 'Message',
 'url' =&gt; home_url( '/' ),
) );
</code></pre>
<h4>Targeting specific users</h4>
By default a notification is delivered to every active subscription. To send it to specific WordPress users instead, pass <code>target_user_id</code> (a single user) or <code>target_user_ids</code> (an array of users). Only subscriptions tied to those user accounts receive the message.
Send to one user:
<pre><code>pushai_trigger_notification( array(
 'title' =&gt; 'Your order shipped',
 'body' =&gt; 'Track it from your account.',
 'url' =&gt; home_url( '/my-account/' ),
 'target_user_id' =&gt; 123,
) );
</code></pre>
Send to several users:
<pre><code>pushai_trigger_notification( array(
 'title' =&gt; 'Members-only update',
 'body' =&gt; 'A new perk is available.',
 'target_user_ids' =&gt; array( 12, 45, 78 ),
) );
</code></pre>
Notes on targeting:
<ul>
<li>Only users who subscribed while logged in can be targeted; guest subscriptions have no user account and are never matched.</li>
<li>A user with several browsers or devices receives the notification on each active subscription (mobile and desktop are tracked separately).</li>
<li>If targeting arguments are supplied but none resolve to a valid user, the notification is rejected with a <code>WP_Error</code> instead of being broadcast to everyone.</li>
</ul>
<h4>Supported arguments</h4>
<ul>
<li><code>title</code> (required) — notification heading.</li>
<li><code>body</code> (required) — notification message.</li>
<li><code>url</code> — link opened when the notification is clicked. Defaults to the site home URL. UTM parameters are appended automatically.</li>
<li><code>image</code> — image URL shown in the notification.</li>
<li><code>target_user_id</code> — a single WordPress user ID to deliver to.</li>
<li><code>target_user_ids</code> — an array of WordPress user IDs to deliver to.</li>
<li><code>source_type</code> — a short label describing what triggered the notification (e.g. <code>post</code>, <code>manual</code>, <code>developer</code>). Metadata only — shown in admin history and used to build the <code>utm_campaign</code> value; it does not affect who receives the message. Defaults to <code>developer</code>.</li>
<li><code>source_id</code> — the ID of the object that triggered the notification, paired with <code>source_type</code> (e.g. the post ID for a <code>post</code> source). Metadata only, not a recipient — use <code>target_user_id</code>/<code>target_user_ids</code> to choose recipients. Defaults to <code>0</code>.</li>
</ul>
Available hooks:
<ul>
<li><code>pushai_should_create_post_notification</code> — filter whether a published post creates a notification.</li>
<li><code>pushai_should_send_to_subscription</code> — filter, per subscription, whether it should receive a given notification.</li>
<li><code>pushai_notification_payload</code> — filter the payload sent to the browser.</li>
<li><code>pushai_utm_parameters</code> — filter (or disable) the UTM parameters appended to push links.</li>
<li><code>pushai_notification_queued</code> — fires after a notification is queued.</li>
<li><code>pushai_notification_failed</code> — fires when a notification fails to send.</li>
<li><code>pushai_notification_delivery_completed</code> — fires after a delivery batch finishes, with success/failed/expired counts.</li>
<li><code>pushai_loaded</code> — fires once PushAI has initialized its services.</li>
</ul>
<h3>Bundled Libraries</h3>
PushAI bundles the following open-source libraries in its <code>vendor/</code> directory. All are MIT-licensed and GPL-compatible.
<ul>
<li><a href="https://github.com/web-push-libs/web-push-php" rel="nofollow ugc">minishlink/web-push</a> — Web Push delivery (MIT)</li>
<li><a href="https://github.com/guzzle/guzzle" rel="nofollow ugc">guzzlehttp/guzzle</a> — HTTP client used by web-push (MIT)</li>
<li><a href="https://github.com/web-token/jwt-framework" rel="nofollow ugc">web-token/jwt-library</a> — JWT signing for VAPID (MIT)</li>
<li><a href="https://github.com/Spomky-Labs/base64url" rel="nofollow ugc">spomky-labs/base64url</a> — Base64url encoding (MIT)</li>
<li><a href="https://github.com/Spomky-Labs/pki-framework" rel="nofollow ugc">spomky-labs/pki-framework</a> — PKI utilities (MIT)</li>
<li><a href="https://github.com/brick/math" rel="nofollow ugc">brick/math</a> — Arbitrary-precision math (MIT)</li>
<li>Various PSR interfaces and Symfony polyfills (MIT)</li>
</ul>
<h3>Third-Party Services</h3>
PushAI communicates with two categories of external services. No personal data is sent without user action.
<h4>Browser push services</h4>
When a visitor subscribes and a notification is delivered, the encrypted push payload is sent directly from your server to the browser&#8217;s native push service:
<ul>
<li>Google Chrome / Edge — Google&#8217;s Firebase Cloud Messaging (FCM): <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
<li>Mozilla Firefox — Mozilla&#8217;s Autopush service: <a href="https://www.mozilla.org/en-US/privacy/" rel="nofollow ugc">Privacy Policy</a></li>
<li>Apple Safari — Apple Push Notification service (APNs): <a href="https://www.apple.com/legal/privacy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
This follows the Web Push standard (RFC 8030). Only the encrypted notification payload (title, body, URL, optional image) is transmitted; the subscriber&#8217;s email address or identity is never sent. You control the VAPID keys used to sign each push.
<h4>PushAI license API (Pro only)</h4>
Sites with a PushAI Pro license send license key verification requests to the PushAI license server at <code>wpushai.com</code>. This happens:
<ul>
<li>When the license is first activated.</li>
<li>On a periodic background check (at most once per day) to confirm the license remains valid.</li>
<li>When the admin manually refreshes the license status.</li>
<li>When WordPress checks for Pro plugin updates.</li>
</ul>
The request includes your site URL (so the license can be validated against the registered domain) and the license key. No personal data beyond these two values is transmitted. <a href="https://wpushai.com/en/privacy-policy" rel="nofollow ugc">PushAI Privacy Policy</a>

Alternative Plugins for

Discover the Lists with PushAI – Self-Hosted Web Push Notifications