PushAI – Web Push Notifications & Telegram Auto Post

By cagriuckan

★ 5.0/5 (1 ratings)100+ active installationsVersion 1.4.0

Self-hosted web push & browser notifications: unlimited subscribers, opt-in popup, click stats, scheduled sends and Telegram auto post — all free.

Description

PushAI sends web push notifications from your own WordPress site. Visitors subscribe with one click and get a browser notification on desktop and mobile every time you publish, even when your site is closed. There is no third-party account to create, no subscriber limit, and no monthly bill: notifications go straight from your server using the native Web Push standard and your own VAPID keys, created automatically on activation.

The same notification can also be posted to your Telegram channel or group, so one publish reaches browser subscribers and Telegram followers together.

🚀 Try the live demo — explore the PushAI admin without installing anything.

📖 Read the PushAI overview on Kan Themes (in Turkish) — how self-hosted push notifications work for WordPress and WooCommerce sites.

Set up in two minutes

  1. Activate PushAI and turn on the push service in PushAI → Settings.
  2. Turn on the opt-in popup, or place the [pushai_button] subscribe button anywhere.
  3. Publish a post. Subscribers get a browser notification automatically.

What you get for free

  • Unlimited subscribers and notifications. No caps, no per-subscriber pricing.
  • Automatic notifications for new posts, updated posts, and any custom post type you choose, with a per-post opt-out in the editor.
  • Opt-in popup in six positions and four designs (Compact, Classic card, Dark, Automatic) with a live preview, plus a list of pages where it never appears.
  • Telegram auto post. Share new posts, updated posts, and campaigns in a Telegram channel or group through your own bot, with the image, a “Read more” button, and silent posting.
  • Manual and scheduled campaigns. Write a notification, preview it, send it now or at a set time, and target everyone or specific users.
  • Click tracking and dashboard stats. Signed, tamper-proof links with delivered and click counts for the last 7 days, and UTM tags so the traffic shows up in Google Analytics.
  • Email fallback. Registered users who have not enabled browser notifications can receive the same notification by email.
  • Built to scale. A background queue sends large lists in chunks with retries, WP-CLI commands process the queue, and a Site Health check warns you if your cron runs late.
  • Your data stays on your site. Subscribers live in your own database, with GDPR export and erasure built in.
  • Separate phone and desktop subscriptions, guest subscriptions, and a developer API with functions, actions, and filters.

PushAI Pro (optional)

PushAI Pro is a paid add-on for sites that want more automation. It adds:

  • AI features with your own API key — AI-written notifications, smart filtering that holds routine posts, scheduled AI digests, and social media posts for X, Facebook, LinkedIn, Instagram, and Threads. Works with OpenAI, Google Gemini, Anthropic Claude, xAI Grok, DeepSeek, and OpenRouter.
  • WooCommerce automation — order and stock alerts, order-status updates, abandoned-cart reminders, cross-sell follow-ups, and trending-product pushes.
  • Advanced statistics — custom date ranges, per-notification performance, the best hour to send, and CSV export.
  • More Telegram channels, audience segments, action buttons, A/B tests, template rules, and a built-in installable web app (PWA).

Actively developed. New features ship regularly, and every release is documented in the changelog below. Feature requests and feedback shape the roadmap.

Free vs Pro

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

  • One-click subscribe button (shortcode)
  • Customizable opt-in popup (permission prompt)
  • Automatic new-post notifications
  • Custom post type automation
  • Click tracking & 7-day dashboard stats
  • Manual notification composer
  • Scheduled notifications (composer + developer API)
  • Per-user / specific-subscriber targeting
  • Separate mobile & desktop subscriptions
  • Guest subscriptions
  • Email fallback for users without a push subscription
  • Automatic posting to a Telegram channel or group
  • Automatic VAPID key generation
  • Background delivery queue with retries
  • WP-CLI queue processing (wp pushai queue)
  • Automatic UTM link tagging
  • Delivery history & status
  • Privacy / GDPR export & erasure
  • Developer API (functions + action hooks)

Pro — $21/year — everything in Free, plus:

  • AI with your own API key (OpenAI, Gemini, Anthropic Claude, Grok, DeepSeek, OpenRouter): Write with AI, smart post notifications, and scheduled AI digests
  • WooCommerce order & stock alerts
  • WooCommerce order-status & customer notes
  • Abandoned-cart reminders
  • Cross-sell follow-ups
  • “Trending Today” (post & product daily-view alerts)
  • Built-in PWA (installable manifest + service worker)
  • Statistics & analytics (7/30/90-day or custom ranges with period comparison, CTR, per-notification performance, best hour to send, most-clicked links, per-category performance, audience segment CTR, A/B CTR, digest conversion, CSV export, data cleanup)
  • Audience segments in the composer and developer API (role, device, category, tag)
  • Action buttons and A/B tests in the composer
  • AI social media posts for X, Facebook, LinkedIn, Instagram and Threads from the post editor
  • More Telegram channels with per-category routing
  • Outbound webhooks and an inbound REST trigger for Zapier / Make
  • Abandoned-browse reminders (non-WooCommerce)
  • Site-management admin alerts (pending comments, posts awaiting review, published posts, new subscribers)
  • Comment notifications (authors, replies & administrators)
  • Notification templates with tokens, category and post type rules, and saved composer templates

Upgrade to PushAI Pro

PushAI is developed and maintained by PushAI.

Shortcode

Place a subscribe button anywhere with:

[pushai_button]

Optional attributes:

  • label — default button text.
  • on — text shown after notifications are enabled.
  • blocked — text shown when the visitor has blocked notifications.
  • align — left, center, or right.
  • class — extra CSS classes.

Example:

[pushai_button label="Enable browser notifications" align="center"]

In PHP templates:

<?php echo do_shortcode( '[pushai_button]' ); ?>

The shortcode is also shown on the PushAI → Settings screen with a copy button.

Show a logged-in visitor whether they currently have an active push subscription:

[pushai_notification_badge]

Guests see nothing. Logged-in users see “Notifications Enabled” plus the number of active devices, or “No Active Subscriptions”. Use it on account pages or membership dashboards.

Developer API

Queue a notification from a theme or plugin:

pushai_trigger_notification( array(
    'title' => 'Title',
    'body'  => 'Message',
    'url'   => home_url( '/' ),
    'image' => '',
) );

The same notification can be triggered with a WordPress action:

do_action( 'pushai_send_notification', array(
    'title' => 'Title',
    'body'  => 'Message',
    'url'   => home_url( '/' ),
) );

Scheduling a notification

Pass scheduled_at in the site timezone to store the notification and send it later. The delivery queue picks it up once that time is reached:

pushai_trigger_notification( array(
    'title'        => 'Evening briefing',
    'body'         => 'Here is what happened today.',
    'scheduled_at' => '2026-09-21 18:00',
) );

Targeting specific users

By default a notification is delivered to every active subscription. To send it to specific WordPress users instead, pass target_user_id (a single user) or target_user_ids (an array of users). Only subscriptions tied to those user accounts receive the message.

Send to one user:

pushai_trigger_notification( array(
    'title'          => 'Your order shipped',
    'body'           => 'Track it from your account.',
    'url'            => home_url( '/my-account/' ),
    'target_user_id' => 123,
) );

Send to several users:

pushai_trigger_notification( array(
    'title'           => 'Members-only update',
    'body'            => 'A new perk is available.',
    'target_user_ids' => array( 12, 45, 78 ),
) );

Targeting an audience segment

With an active PushAI Pro license, pass target_segment to filter subscriptions by WordPress role, device type, category, or tag. Dimensions are combined with AND; values inside a dimension are OR. Category and tag IDs match logged-in users who published or commented on posts in those terms. Device-only filters include guests; role and term filters require a logged-in subscriber. Explicit target_user_ids are intersected with the segment.

pushai_trigger_notification( array(
    'title'          => 'Editors on mobile',
    'body'           => 'A draft is waiting.',
    'target_segment' => array(
        'roles'    => array( 'editor' ),
        'devices'  => array( 'mobile' ),
        'categories' => array( 4, 9 ),
    ),
) );

Without a Pro license, a non-empty target_segment returns a pushai_segment_requires_pro error instead of sending.

Notes on targeting:

  • Only users who subscribed while logged in can be targeted; guest subscriptions have no user account and are never matched.
  • A user with several browsers or devices receives the notification on each active subscription (mobile and desktop are tracked separately).
  • If targeting arguments are supplied but none resolve to a valid user, the notification is rejected with a WP_Error instead of being broadcast to everyone.

Supported arguments

  • title (required) — notification heading.
  • body (required) — notification message.
  • url — link opened when the notification is clicked. Defaults to the site home URL. UTM parameters are appended automatically.
  • image — image URL shown in the notification.
  • target_user_id — a single WordPress user ID to deliver to.
  • target_user_ids — an array of WordPress user IDs to deliver to.
  • source_type — a short label describing what triggered the notification (e.g. post, manual, developer). Metadata only — shown in admin history and used to build the utm_campaign value; it does not affect who receives the message. Defaults to developer.
  • source_id — the ID of the object that triggered the notification, paired with source_type (e.g. the post ID for a post source). Metadata only, not a recipient — use target_user_id/target_user_ids to choose recipients. Defaults to 0.
  • scheduled_at — send later instead of immediately. Accepts a site-timezone datetime (Y-m-d H:i or Y-m-d H:i:s), an ISO-8601 value with offset, or a Unix timestamp. Omit it, or pass a time that is already past, to queue delivery now.
  • target_segment — Pro-licensed audience filters: roles, devices (mobile and/or desktop), categories (term IDs), and tags (term IDs). Empty dimensions are ignored. Selecting both devices is the same as omitting the device filter.
  • actions — Pro-licensed action buttons. An array of {title, url} objects (max two). The service worker opens the button URL when pressed.
  • ab — Pro-licensed A/B copy: {title, body} for variant B. Variant A is the main title/body. Even subscription ids receive A; odd ids receive B.

Available hooks:

  • pushai_should_create_post_notification — filter whether a published post creates a notification.
  • pushai_should_send_to_subscription — filter, per subscription, whether it should receive a given notification.
  • pushai_notification_payload — filter the payload sent to the browser.
  • pushai_utm_parameters — filter (or disable) the UTM parameters appended to push links.
  • pushai_notification_queued — fires after a notification is queued for delivery.
  • pushai_notification_scheduled — fires after a notification is stored for a future send.
  • pushai_notification_failed — fires when a notification fails to send.
  • pushai_notification_delivery_completed — fires after each delivery chunk finishes, with success/failed/expired counts for that chunk.
  • pushai_loaded — fires once PushAI has initialized its services.
  • pushai_queue_batch_size — filter how many pending jobs one processor run claims (default 5, clamped 1–50).
  • pushai_delivery_chunk_size — filter how many subscriptions one delivery job sends (default 250, clamped 1–1000).
  • pushai_completed_job_retention_days — filter how many days completed queue jobs are kept (default 7).
  • pushai_should_record_post_views — filter whether daily post/product view tracking runs.
  • pushai_admin_pages — filter the admin page list (menu, sidebar, and assets). PushAI Pro uses this to replace Free preview screens.
  • pushai_can_target_segment — filter whether a non-empty target_segment may be stored. Defaults to false; PushAI Pro returns true when licensed.
  • pushai_can_use_actions — filter whether action buttons may be stored. Defaults to false; PushAI Pro returns true when licensed.
  • pushai_can_ab_test — filter whether A/B copy may be stored. Defaults to false; PushAI Pro returns true when licensed.
  • pushai_notification_composer_fields — extra fields inside the notification composer. PushAI Pro adds audience segments, action buttons, and A/B fields here.
  • pushai_notification_composer_payload — filter composer arguments before they are queued.
  • pushai_notification_clicked — fires after a signed click is recorded.

Automations (Pro)

With an active PushAI Pro license, Settings → Automations can POST signed JSON (X-PushAI-Signature, X-PushAI-Event) when a notification is queued, sent, or clicked. The same screen exposes POST /wp-json/pushai/v1/trigger for Zapier and Make: send X-PushAI-Token and a JSON body using the same fields as pushai_trigger_notification(). A blueprint file is linked from that settings tab.

WP-CLI

Process, inspect, and prune the delivery queue from the command line:

wp pushai queue process
wp pushai queue process --jobs=20
wp pushai queue status
wp pushai queue prune<h3>Bundled Libraries</h3>

PushAI bundles the following open-source libraries in its vendor/ directory. All are MIT-licensed and GPL-compatible.

Third-Party Services

PushAI communicates with the external services below. No personal data is sent without user action.

Browser push services

When a visitor subscribes and a notification is delivered, the encrypted push payload is sent directly from your server to the browser’s native push service:

  • Google Chrome / Edge — Google’s Firebase Cloud Messaging (FCM): Privacy Policy
  • Mozilla Firefox — Mozilla’s Autopush service: Privacy Policy
  • Apple Safari — Apple Push Notification service (APNs): Privacy Policy

This follows the Web Push standard (RFC 8030). Only the encrypted notification payload (title, body, URL, optional image) is transmitted; the subscriber’s email address or identity is never sent. You control the VAPID keys used to sign each push.

Telegram Bot API (optional)

Only when a site administrator turns on Settings → Telegram and enters a bot token, PushAI sends eligible notifications to api.telegram.org so the bot can post them to the chosen channel or group. Each request contains the bot token, the channel or chat ID, and the notification’s title, message, link and image URL. Only notifications sent to all subscribers are posted; no subscriber or visitor data is sent. Telegram Terms of Service, Telegram Privacy Policy

PushAI license API (Pro only)

Sites with a PushAI Pro license send license key verification requests to the PushAI license server at wpushai.com. This happens:

  • When the license is first activated.
  • On periodic background checks to confirm the license remains valid: a weekly scheduled check, plus a refresh when the saved license status is more than 12 hours old.
  • When the admin manually refreshes the license status.
  • When WordPress checks for Pro plugin updates.
  • Once a day, a license heartbeat that also includes the PushAI, PushAI Pro, WordPress, and PHP version numbers and the site’s install ID, so the license server can show which versions licensed sites run.

The request includes your site URL (so the license can be validated against the registered domain) and the license key. No personal data about your visitors or subscribers is transmitted. The free plugin on its own never contacts the license server: these requests only happen after a site administrator enters a PushAI Pro license key (the daily heartbeat additionally requires PushAI …

Installation

  1. Upload the plugin to /wp-content/plugins/pushai, or install it from your WordPress admin, then activate it.
  2. Open PushAI in the WordPress admin menu.
  3. On the Settings page, turn on the push service. VAPID credentials are generated automatically.
  4. Add the [pushai_button] shortcode to a page, post, or widget so visitors can subscribe.
  5. (Optional) Turn on Settings → Telegram to post your notifications to a Telegram channel or group as well.
  6. (Optional) Install PushAI Pro and activate your license to unlock AI features, WooCommerce automation, and the built-in PWA.

Note: Web Push requires HTTPS in production. Browsers also allow localhost during development.

FAQ

How do visitors subscribe?

Two ways, both free: place the [pushai_button] shortcode anywhere on your site, or enable the permission popup in Settings — a customizable prompt (title, description, and button labels are all editable) that invites visitors to enable notifications until they subscribe or dismiss it.

Does PushAI need a third-party push service?

No. Notifications are delivered directly from your server using the native Web Push protocol and your own VAPID keys. There’s no per-subscriber cost and no external SDK.

Where are subscribers stored?

In your own WordPress database. You own your subscriber list.

Can the same person subscribe on both their phone and their computer?

Yes. PushAI keeps one active subscription per device type for each logged-in account — one mobile, one desktop — so a visitor can opt in independently on each device and receive notifications on whichever ones they enabled.

What happens if a user hasn’t subscribed to browser push?

Enable the email fallback in Settings and registered users without an active push subscription receive the same notification as a responsive HTML email instead. Per-user targeting and exclusions are honoured, users can opt out of these emails from their profile, and guests are never emailed.

Can PushAI post my notifications to Telegram?

Yes, for free. Create a bot with @BotFather, add it as an administrator of your channel or group, then enter the bot token and channel in PushAI → Settings → Telegram. New posts, updated posts, and notifications sent to all subscribers are posted with the image and a “Read more” button. Personal notifications, such as comment replies or order updates, are never posted. A “Send test message” button checks the setup.

Does it add tracking parameters to links?

Yes. Every push link is tagged with utm_source, utm_medium, and a source-aware utm_campaign (e.g. post-42 or ai-digest) so clicks are attributed in Google Analytics and similar tools. Customize or disable this with the pushai_utm_parameters filter.

Does it work with WooCommerce?

Yes, with PushAI Pro. Pro can alert admins about new, cancelled, and refunded orders and about low/out-of-stock products; send order-status changes and order notes to customers; remind customers about abandoned carts; follow up with cross-sell suggestions after a purchase; and push trending products. Customer-facing notifications require the customer to have a WordPress account with an active push subscription.

Does PushAI include a PWA?

Yes, with PushAI Pro. Pro outputs an installable web-app manifest and registers a service worker so visitors can add your site to their home screen, with a configurable app name, icon, and theme color. The free plugin focuses on push delivery.

Which AI providers power the digests?

PushAI Pro supports OpenAI, Google Gemini, Anthropic Claude, xAI Grok, DeepSeek, and any model available through OpenRouter, with your own API key. Digests are generated only when the active provider has an API key; if a request to the provider fails, a short template backup is sent for that scheduled slot.

Does it work on every browser?

Web Push is supported in modern versions of Chrome, Firefox, Edge, and Safari (including iOS 16.4+ when the site is added to the Home Screen). PushAI only shows the subscribe control where Web Push can be used.

Is HTTPS required?

Yes, in production. Browsers also allow localhost for local development.

Why are my notifications sent late?

PushAI delivers through a background queue that runs on WP-Cron, and WP-Cron only runs when someone visits your site. On quiet sites a notification can wait until the next visit. PushAI shows a warning on its admin screens and in Tools → Site Health when a due notification has waited more than 10 minutes. For on-time delivery, set define( 'DISABLE_WP_CRON', true ); in wp-config.php and add a server cron job that requests https://your-site.com/wp-cron.php every minute. Developers can change the warning delay with the pushai_queue_delay_threshold filter.

My site is behind Cloudflare or another proxy. Do the rate limits still work?

By default PushAI uses the connection address (REMOTE_ADDR) for its rate limits, because forwarding headers can be faked by any visitor. If your server sees the proxy’s address instead of the visitor’s, every visitor shares one limit. Either let your web server restore the real address (for example mod_remoteip or nginx real_ip), or tell PushAI which header your proxy sets:

add_filter( 'pushai_trusted_ip_headers', fn() => array( 'CF-Connecting-IP' ) );

Only do this when all traffic reaches your site through that proxy. The pushai_client_ip filter can override the result entirely.

How many subscribers and notifications can I send?

Subscribers and notifications are unlimited on both Free and Pro. There’s no per-subscriber pricing and no monthly send cap.

Does it cost more as my subscriber list grows?

No. The free plugin is free forever, and Pro is a single flat price ($21/year) regardless of how many subscribers you have. You only pay for automation and AI features, not for audience size.

Is PushAI still being developed?

Yes — actively. New automations, AI providers, and WooCommerce flows ship regularly. Every release is documented in the changelog, and user feedback shapes the roadmap.

Do I have to show “powered by” branding?

No. PushAI doesn’t add vendor branding to your subscribe control or to the notifications you send.

Screenshots

Changelog

1.4.0

  • Added: Settings → Telegram. Post new posts, updated posts and manual notifications sent to all subscribers to a Telegram channel or group through your own bot, with the image, a “Read more” button, silent posting and a test message. Notifications aimed at specific users, guests or a segment are never posted. Developers can add chats with the pushai_telegram_targets filter, change the post with pushai_telegram_message, and add sources with pushai_telegram_source_labels.
  • Fixed: Saving the Popup tab with PushAI Pro active showed a false “the saved database values did not match” error.

1.3.1

  • Fixed: A user’s “Do not email me notifications” choice was erased when their profile or WooCommerce account details were saved while the email fallback was switched off, so they could receive emails again once it was turned back on. The saved choice is now kept.
  • Fixed: Email fallback jobs already in the queue kept sending after the email fallback was switched off. They now stop without sending.
  • Fixed: Sites running PHP 8.1 stopped with a fatal error (“Cannot use ‘PushAI\Rest\true’ as class name”) as soon as PushAI loaded. PushAI now runs on PHP 8.1 again, as its minimum requirement says.
  • Fixed: The error log could show “invalid_schedule” errors for the pushai_process_queue event, and the per-minute queue event was sometimes dropped until the next page load. The per-minute schedule is now registered as soon as the plugin file loads, so WordPress can always reschedule it.
  • Changed: The free plugin no longer contacts the PushAI license server. The daily license heartbeat now runs only when PushAI Pro is installed and a license key is entered, and the Third-Party Services section lists exactly what it sends.
  • Changed: Audience segments, notification action buttons, A/B tests and daily view tracking now live entirely in PushAI Pro. PushAI provides extension hooks instead (pushai_notification_context, pushai_handled_notification_args, pushai_delivery_audience_sql, pushai_email_audience_sql, pushai_subscription_variant, pushai_subscription_payload, pushai_notification_recipient_parts, pushai_notification_category_ids). Passing target_segment, actions or ab without an extension that handles them now returns an error instead of being stored.
  • Improved: A notification whose audience was narrowed by an extension is not sent if that extension is no longer active, so it can never reach every subscriber by mistake.
  • Security: Browser subscriptions are accepted only for HTTPS endpoints on the known browser push services (Google FCM, Mozilla, Apple, Windows). Previously any address could be registered, which let a visitor make the server send requests to internal addresses. Stored subscriptions with other addresses are retired at the next send instead of being contacted, and push requests no longer follow redirects. Developers can extend the list with the pushai_push_service_hosts filter.
  • Added: A warning on PushAI’s admin screens and a Tools → Site Health check when queued or scheduled notifications are more than 10 minutes late, with steps to set up a server cron job. Developers can change the delay with the pushai_queue_delay_threshold filter.
  • Added: pushai_trusted_ip_headers and pushai_client_ip filters so sites behind Cloudflare or another proxy can rate-limit by the real visitor address instead of the proxy’s.

1.3.0

  • Added: Position setting for the permission popup (Settings → Popup). Choose bottom center, bottom right, bottom left, top center, top right, or top left. On phones the popup still spans the screen width at the top or bottom edge, and top positions leave room for the WordPress toolbar.
  • Added: Design setting for the permission popup with four styles: Compact (a slim single-line bar), Classic card, Dark, and Automatic (follows the visitor’s light or dark system theme).
  • Added: Live popup preview on Settings → Popup. It updates as you change the position, design, or text, and can show the blocked state and a phone-sized screen.
  • Added: “Do not show on” setting for the permission popup. List paths or URLs (one per line, * for everything below a path) such as checkout or login pages. On those pages neither the popup nor the browser’s own permission request appears; shortcode subscribe buttons keep working. Developers can use the pushai_prompt_excluded filter.
  • Added: Pressing Escape closes the permission popup, the same as “Not now”.
  • Added: pushai:prompt-render and pushai:prompt browser events so extensions can adjust the popup before it renders and react when it is shown, accepted, blocked, or dismissed.
  • Added: A “What’s new” page in the PushAI menu that lists the highlights of each release. The menu item shows a “New” badge until each administrator opens it. Extensions can add items with the pushai_whats_new_items filter.
  • Improved: When notifications are blocked, the compact popup expands to show the instructions for re-enabling them in the browser.
  • Changed: The default popup is now Compact at the bottom center of the screen. To keep the previous look, choose Classic card and Bottom right in Settings → Popup.

1.2.1

  • Fixed: Plugin load no longer fatals when PHPUnit Composer packages are missing from vendor/. Release ZIPs now always run composer install --no-dev so the autoloader never requires myclabs/deep-copy or PHPUnit, and a missing vendor file shows an admin notice instead of taking down WordPress.
  • Changed: Tested up to WordPress 7.1.

1.2.0

  • Changed: The minimum PHP version is 8.1. Bundled Web Push libraries are pinned to versions that run on PHP 8.1.
  • Improved: Large notification sends now go out in subscription chunks (250 by default) so a single queue job cannot time out on a big list. Delivery totals accumulate across chunks, and the email fallback runs only after the last chunk.
  • Improved: Each delivery chunk uses batched Web Push flush and bulk subscription updates instead of one database write per recipient.
  • Improved: Settings are cached for the current request so hot paths do not re-read options from the database on every check.
  • Improved: Daily post view tracking now runs only when PushAI Pro is licensed and a Trending Today feature is enabled (posts or WooCommerce products), so Free sites no longer write a database row on every singular page view.
  • Improved: Completed delivery jobs older than 7 days are removed automatically, so the queue table does not grow without bound.
  • Added: WP-CLI commands wp pushai queue process, wp pushai queue status, and wp pushai queue prune.
  • Added: pushai_queue_batch_size and pushai_delivery_chunk_size filters to tune queue throughput.
  • Added: Documentation for the [pushai_notification_badge] shortcode, which now also loads its styles on the front end.
  • Changed: The WordPress admin is now a shared shell with separate Dashboard, Notifications, Subscribers, Settings, and Plans screens, so PushAI Pro can reuse the same layout.
  • Added: A Preview button in the notification composer. When the browser allows it, a live system notification is shown; otherwise an in-page mock is used.
  • Added: pushai_admin_pages filter so PushAI Pro can replace Free preview pages while keeping one menu and one asset list.
  • Added: Scheduled notifications. The composer can send immediately or at a site-timezone datetime; due items enter the delivery queue on the next processor run. Scheduled campaigns can be edited or cancelled until they send.
  • Added: scheduled_at argument for pushai_trigger_notification() and the pushai_send_notification action, plus the pushai_notification_scheduled hook.
  • Added: Audience segment delivery in the queue. target_segment (roles, devices, categories, tags) is stored on the notification and applied when subscriptions are selected. Targeting a segment without an active PushAI Pro license returns pushai_segment_requires_pro.
  • Added: pushai_can_target_segment filter and pushai_notification_composer_fields action so PushAI Pro can license and render the segment builder.
  • Added: Notification action buttons in the Web Push payload and service worker (actions / actionUrls). Buttons require an active PushAI Pro license (pushai_can_use_actions).
  • Added: A/B variant delivery. Even subscription ids receive the original copy; odd ids receive ab variant B. Clicks and deliveries can be tagged with event_meta.
  • Added: dispatch_webhook queue jobs for signed outbound HTTP callbacks (X-PushAI-Signature, X-PushAI-Event).
  • Added: pushai_notification_clicked action after a signed click is recorded.
  • Added: A device filter (mobile / desktop) on the Subscribers screen, with a device badge on each row.
  • Improved: Admin status badges are larger and higher-contrast.

1.1.8

  • Fixed: Activation no longer fails with a fatal error on hosts where OpenSSL has no configuration file available — a common setup on Windows environments such as Local and XAMPP. PushAI now ships its own OpenSSL configuration and uses it to generate the VAPID keys when the host provides none. Sites that hit the error can activate normally; existing installs get their keys on the next admin page load.
  • Fixed: Key generation failures can no longer take down plugin activation or the WordPress admin. If a key pair genuinely cannot be created, PushAI now records the reason in the error log and reports the missing credentials in Dashboard → Service health instead of raising a fatal error.
  • Changed: The minimum PHP version is now correctly stated as 8.2. The bundled cryptography libraries have always required 8.2, but the plugin advertised 8.1, which caused activation to fail on PHP 8.1 sites. Those sites now see a clear notice instead.

1.1.7

  • Added: Updated post automation. On by default alongside new post automation; when enabled, editing an already-published post queues a notification. It only fires when the title, content, or excerpt actually changes, so saves that merely touch metadata, categories, or tags are ignored, and a per-post cooldown (24 hours by default) keeps one editing session from sending several pushes. The per-post auto-share opt-out applies to updates too.
  • Changed: The per-post auto-share toggle in the block editor moved from the header toolbar (undo/redo, block inserter) to the header settings area (Preview, Publish, sidebar toggle), where a per-post switch fits better next to the other publishing controls.
  • Changed: PushAI Pro is now a yearly subscription that renews automatically. The “Renew license” button is replaced by “Manage subscription”, which opens the billing portal where you can update your card, download invoices, or cancel.
  • Changed: Checkout moved to a new payment provider. Existing license keys are unaffected and keep working exactly as before.

1.1.6

  • Fixed: The permission popup no longer reappears on every page load after the visitor closes it. Dismissing the prompt (“Not now” or the close button) is now remembered and the popup stays hidden for 7 days before it can show again.

1.1.5

  • Fixed: Auto-share toolbar toggle no longer crashes Appearance → Widgets (and other non-post block editors). The script now loads only on post edit screens for enabled post types, where the editor store is available.
  • Improved: Settings are organized into tabs (Delivery, Popup, Post types, Comments, Site management, WooCommerce, Trending, Tools, Privacy). Each tab has its own Save control so changes in one section no longer overwrite another.
  • Changed: Settings use a tab bar instead of the previous accordion layout.

1.1.4

  • Fixed: Notification titles and messages no longer show HTML entities such as ” instead of quotation marks. Entities from post titles, excerpts, and site names are decoded before the push payload is queued.
  • Improved: Front-end page loads no longer run analytics table checks or read the VAPID private key. The public key and analytics version options are now autoloaded, so PushAI no longer adds extra database queries on every visitor request.

1.1.3

  • Fixed: Browser subscription no longer fails with “Cookie check failed” when the WordPress REST nonce is expired or out of sync with the login cookie. Security tokens are refreshed via admin-ajax before saving, so logged-in visitors stay linked to their account.
  • Fixed: Revoking notification permission in the browser now marks the matching subscription as unsubscribed in Subscribers, instead of leaving it shown as Active.
  • Improved: Already-subscribed browsers no longer re-register with the server on every page load. Sync runs on opt-in, permission changes, login/logout, or after 24 hours.

1.1.2

  • Fixed: Permission popup and automatic notification post type settings are now saved correctly. Turning the popup on (or choosing post types) and clicking Save settings no longer silently discarded those values.
  • Changed: Frontend subscribe-button and permission-prompt strings now use English source text (e.g. “Subscribed”, “Enable browser notifications”, “Notifications blocked”), with Turkish kept in the language pack. Previously baked-in Turkish defaults are cleared so the active locale controls the wording.

1.1.1

  • Fixed: Browser push subscription no longer fails with “no active Service Worker” when the worker is still installing. PushAI now waits for the service worker to activate before calling PushManager.subscribe.
  • Changed: PushAI Pro pricing is now $21/year.
  • Improved: Daily post view tracking for Trending Today now uses a dedicated database table instead of creating a new pushai_views_YYYYMMDD post meta key every day. Existing meta is migrated automatically and rows older than 14 days are pruned.

1.1.0

  • Added: The on-site permission popup is now a free feature. Enable and customize it (title, description, button labels, and blocked-permission message) from Settings — no Pro license required.
  • Added: Custom post type automation is now a free feature. Choose which post types trigger automatic notifications from Settings, including custom slugs.
  • Added: Built-in click tracking with signed, tamper-proof links, plus “Delivered” and “Clicks” cards for the last 7 days on the Dashboard. Notification history now shows click counts without Pro.
  • Note: These three features previously belonged to PushAI Pro; existing Pro settings and recorded analytics data are migrated automatically.
  • Added: A “Get started” checklist on the Dashboard walks new sites through enabling the service, collecting subscribers, and sending the first notification.
  • Added: A dismissible review invitation on PushAI screens after 10 successful notifications.

1.0.2

  • Added: Email fallback recipients list in notification history. When email fallback is enabled, you can now see which users received fallback emails for each notification by expanding the email summary on the Notifications page.
  • Added: “Delete data on uninstall” setting (Settings > Data & privacy). Off by default so your subscriptions, notifications, and settings are kept if you deactivate or reinstall the plugin; turn it on to have PushAI remove all of its database tables, options, and scheduled tasks when deleted from the Plugins screen.

1.0.1

  • Fixed: Pro notice kept reappearing after being dismissed.
  • Fixed: Recipient search in the notification form now works on all admin pages.

1.0.0

  • Initial release.