PushAI
tr
Get PushAI Pro
Documentation

PushAI user and developer documentation.

This guide is based on the actual PushAI Free and PushAI Pro plugin code. It covers setup, admin workflows, Pro automation, troubleshooting, and the PHP and REST surfaces available to theme and plugin developers.

Current plugin version

1.2.0

Minimum WordPress

6.4+

Minimum PHP

8.1+

What PushAI does

Overview

PushAI is a self-hosted Web Push plugin for WordPress. Browser subscriptions, notifications, queue jobs, license state, and analytics data live in your WordPress installation instead of a third-party push SaaS. Delivery uses VAPID credentials and the native Web Push standard.

Free plugin

Manual and scheduled notifications, automatic new-post and post-update notifications, subscriber collection with a mobile/desktop filter, guest subscriptions, the on-site permission prompt, custom post type automation, chunked background delivery, WP-CLI queue commands, VAPID credentials, GDPR export/erasure hooks, and developer APIs.

Pro plugin

Licensed automation for audience segments, action buttons, A/B tests, signed webhooks, abandoned-browse reminders, AI digests, analytics, templates, comments, admin alerts, WooCommerce events, Trending Today, and PWA.

PushAI Pro requires the main PushAI plugin and an active Pro license. Installing the Pro plugin alone does not unlock paid features.

First install

Quick start

  1. 1Install and activate PushAI from WordPress -> Plugins.
  2. 2Open PushAI -> Settings and enable Push service.
  3. 3Leave Guest subscriptions enabled if visitors without WordPress accounts should subscribe.
  4. 4Set a square notification icon. A 192x192 PNG is recommended.
  5. 5Open PushAI -> Credentials and confirm that VAPID credentials exist.
  6. 6Add the shortcode [pushai_button] to a page, post, widget, or template.
  7. 7Open the page in a supported browser, click the button, and allow notifications.
  8. 8Go to PushAI -> Notifications and send a manual test campaign.
[pushai_button]
[pushai_button label="Enable browser notifications" align="center"]
<?php echo do_shortcode( '[pushai_button]' ); ?>

Common tasks

How-to guides

Start here when you want to do a specific job in the WordPress admin. Each guide assumes the main PushAI plugin is installed and active.

Add the subscribe button to a page

Outcome: Visitors can click one button and allow browser notifications.

  1. 1Open the WordPress page or post where you want the button to appear.
  2. 2Paste [pushai_button] into the content editor, shortcode block, widget, or template.
  3. 3Optional: customize it with label, on, blocked, align, and class attributes.
  4. 4Update the page, open it in a supported browser, and click the button.
  5. 5Accept the browser permission prompt. The browser should appear under PushAI -> Subscribers.
[pushai_button label="Enable browser notifications" align="center"]

Send your first test notification

Outcome: Confirms that subscription collection, VAPID credentials, and delivery queue all work.

  1. 1Subscribe from the front end first. Use the same browser you will use for testing.
  2. 2Go to PushAI -> Notifications.
  3. 3Create a manual notification with a short title, message, and destination URL.
  4. 4Send it to all subscribers, or select your WordPress user if you are testing a targeted send.
  5. 5Open PushAI -> Dashboard and check Recent notifications, Queue depth, and Failed jobs.

Automatically notify subscribers when a post is published

Outcome: PushAI queues a notification whenever a post is published.

  1. 1Go to PushAI -> Settings.
  2. 2Enable Push service.
  3. 3Enable New post automation.
  4. 4Publish a new post. Existing already-published posts will not re-trigger unless republished through a new transition.
  5. 5Check PushAI -> Notifications to confirm that a new campaign was created.

Allow visitors without accounts to subscribe

Outcome: Logged-out readers can become browser subscribers.

  1. 1Go to PushAI -> Settings.
  2. 2Enable Guest subscriptions.
  3. 3Place [pushai_button] somewhere public on the site.
  4. 4Test in an incognito/private window.
  5. 5Confirm the new row appears in PushAI -> Subscribers under Guests.

Automatically notify for custom post types

Outcome: Publishing selected content types queues a browser notification.

  1. 1Go to PushAI -> Settings -> Post types.
  2. 2Select the public post types you want to notify for.
  3. 3Add comma-separated custom post type slugs if a type does not appear in the checkbox list.
  4. 4Save settings and publish a new item in that post type.

Send to selected WordPress users only

Outcome: A notification reaches only users with active browser subscriptions.

  1. 1Ask the target users to log in and subscribe from their browsers.
  2. 2Go to PushAI -> Notifications.
  3. 3Create a manual notification and search/select the recipients.
  4. 4Send the notification.
  5. 5If a selected user has no active subscription, PushAI skips that target by default.

Schedule a notification

Outcome: The campaign waits until the chosen site-timezone datetime, then enters the delivery queue.

  1. 1Go to PushAI -> Notifications and create a campaign.
  2. 2Choose Schedule instead of Send now, and pick a datetime in the WordPress site timezone.
  3. 3Save. The notification stays in Scheduled status until that time.
  4. 4Edit or cancel it before it sends if the copy or time changes.
  5. 5The next queue processor run after the due time starts delivery. WP-Cron or wp pushai queue process both work.

Filter subscribers by device

Outcome: The Subscribers list shows only mobile, only desktop, or every endpoint.

  1. 1Go to PushAI -> Subscribers.
  2. 2Use the device filter: All devices, Mobile, or Desktop.
  3. 3Each row shows a device badge. One person can appear twice if they subscribed from two browsers.

Change the notification icon

Outcome: Notifications show a recognizable site or brand icon.

  1. 1Prepare a square PNG image. 192x192px or larger is recommended.
  2. 2Go to PushAI -> Settings.
  3. 3Use Notification icon -> Select image.
  4. 4Save settings.
  5. 5Send a test notification. Some browsers may cache old icons briefly.

Licensed workflows

Pro how-to guides

These tasks require PushAI Pro to be installed and the site license to be active from PushAI > Plans & License.

Activate PushAI Pro

Outcome: Unlocks Pro menus and licensed automation.

  1. 1Install and activate the main PushAI plugin first.
  2. 2Install and activate PushAI Pro.
  3. 3Go to PushAI -> Plans & License.
  4. 4Paste or confirm the license key and activate it for this site.
  5. 5Reload the PushAI menu. AI Digests, Statistics, Templates, and Pro settings become available.

Set up scheduled AI digests

Outcome: Recent posts are collected and sent as scheduled browser push summaries.

  1. 1Go to PushAI -> AI Digests.
  2. 2Enable AI digest service.
  3. 3Set Delivery times using the WordPress site timezone, for example 09:00,18:00.
  4. 4Choose Lookback window, Minimum posts, Maximum posts, and Digest language.
  5. 5Optionally add an OpenAI API key and model. Without a key, PushAI uses a template fallback.
  6. 6Save AI settings and watch Recent AI Digest Summaries after the next scheduled run.

Notify authors about new comments

Outcome: Post authors receive browser notifications when their content gets comments.

  1. 1Go to PushAI -> Settings.
  2. 2Enable Comment notifications.
  3. 3Enable Notify post author.
  4. 4Select the post types that should trigger comment notifications.
  5. 5Make sure authors are logged in and subscribed to browser notifications.

Turn on WooCommerce order and stock alerts

Outcome: Subscribed administrators and registered customers receive store events by push.

  1. 1Make sure WooCommerce is active before configuring this section.
  2. 2Go to PushAI -> Settings and find WooCommerce.
  3. 3Enable WooCommerce notifications.
  4. 4Enable the exact events you need: admin orders, admin stock, customer order status, customer order notes, or customer cross-sell.
  5. 5For cross-sell, set Delay after order and Max suggested products.
  6. 6Remember: customer notifications only reach registered, subscribed customers. Guest checkouts cannot be targeted.

Customize automatic notification text

Outcome: Automatic notifications use your own titles and message templates.

  1. 1Go to PushAI -> Templates.
  2. 2Edit the template for the event you want: new content, comments, trending, admin alerts, or WooCommerce.
  3. 3Use placeholders such as {title}, {excerpt}, {post_title}, {comment_author}, {order_number}, or {product_names}.
  4. 4Leave a field blank to fall back to the plugin default.
  5. 5Save templates and trigger the event again to test the output.

Target an audience segment

Outcome: A send reaches only subscriptions that match role, device, category, and tag filters.

  1. 1Go to PushAI -> Notifications with Pro licensed.
  2. 2Leave Recipients empty, or keep specific users — the segment is applied on top of that list.
  3. 3Open Audience segment. Role, device, category, and tag filters apply together; within one group, any selected value matches.
  4. 4Category and tag are not a topic interest list. They reach logged-in subscribers who published a post in that term, or left an approved comment on one. Guests are never included.
  5. 5Selecting both mobile and desktop is the same as leaving device empty.
  6. 6Send or schedule. Statistics groups clicks under Audience segment.

Add action buttons and A/B copy

Outcome: The OS notification can show up to two buttons, and half of the list receives variant B.

  1. 1In the composer, add up to two action buttons with a label and URL. They appear on the native OS toast, not in the admin Preview. macOS and Safari often hide them.
  2. 2Optional: fill variant B title and body. Even subscription IDs receive the original copy; odd IDs receive B.
  3. 3Send the campaign. Open PushAI -> Statistics to compare variant CTR.

Connect Zapier or Make

Outcome: External tools can fire a PushAI send, and PushAI can POST signed events back.

  1. 1Go to PushAI -> Settings -> Automations.
  2. 2Copy the inbound URL POST /wp-json/pushai/v1/trigger and the automation token. Send the token as X-PushAI-Token or Authorization: Bearer.
  3. 3POST JSON with the same fields as pushai_trigger_notification(), including title and body.
  4. 4To receive events, add webhook URLs for notification.queued, notification.sent, or notification.clicked. Each POST is HMAC-signed as X-PushAI-Signature; the event name is X-PushAI-Event.
  5. 5A JSON blueprint for Make is available on the same tab.

Send abandoned-browse reminders

Outcome: A subscriber who reads a post and leaves receives one reminder for the last article after the delay.

  1. 1Go to PushAI -> Settings -> Automations.
  2. 2Enable abandoned-browse reminders and choose public post types. WooCommerce products are skipped so they do not overlap with abandoned-cart alerts.
  3. 3Set the delay. Each new view resets the timer; editors are skipped.
  4. 4Subscribe, view a post, wait the delay, and confirm a campaign appears under Notifications.
Pro features are gated by the license check at runtime. If Pro is installed but locked, activate or refresh the license from PushAI > Plans & License.

Operational checks

Fix common issues

Button does not subscribe

Confirm Push service is enabled, guest subscriptions are allowed when testing logged out, HTTPS is active in production, and the browser supports Web Push.

Notifications stopped after VAPID change

Regenerating credentials invalidates all existing browser subscriptions. Visitors must subscribe again.

Queue is not moving

Check WP-Cron, server loopback requests, and the Dashboard cards for queue depth and failed jobs. The same processor also runs from WP-CLI: wp pushai queue process, wp pushai queue status, and wp pushai queue prune.

WooCommerce customer alerts do not arrive

Customer order status, order note, and cross-sell notifications reach registered customers with active subscriptions. Guest checkouts cannot be targeted.

Use PushAI > Dashboard as the first diagnostic screen. Service health tells you whether Push service, new-post automation, guest subscriptions, and VAPID credentials are currently active.

WordPress admin

Admin reference

Dashboard

PushAI -> Dashboard

Monitors active subscribers, sent notifications, completed campaigns, queue depth, failed jobs, recent notifications, and service health.

Notifications

PushAI -> Notifications

Creates manual campaigns, send-now or scheduled, filters history by queued, processing, sent, scheduled, cancelled, or failed status, and supports targeted sends to selected WordPress users. With Pro, the same composer adds audience segments, action buttons, and A/B copy.

Subscribers

PushAI -> Subscribers

Lists browser subscriptions for registered users and guests. Filter by mobile or desktop. Each row represents one browser endpoint, not one human account, and shows a device badge.

Settings

PushAI -> Settings

Controls the push service, automatic new-post notifications, guest subscriptions, notification icon, shortcode usage, Pro panels including Automations, and maintenance actions.

Credentials

PushAI -> Credentials

Shows the masked public VAPID key and can regenerate Web Push credentials. Regeneration invalidates existing browser subscriptions.

Plans & License

PushAI -> Plans & License

Manages checkout, license activation, refresh, renewal, and site deactivation for PushAI Pro.

What Pro adds

  • Scheduled AI digests with delivery times, lookback window, minimum posts, maximum posts, language, public digest pages, OpenAI API key, and model setting.
  • Audience segments in the composer: WordPress role, device, category, and tag. Filters apply together. Category and tag match logged-in authors and approved commenters of those topics, not a topic interest list.
  • Action buttons (up to two) on the OS notification toast, plus a 50/50 A/B copy split. Statistics shows variant CTR. Preview does not show buttons; macOS and Safari often hide them.
  • Outbound signed webhooks (notification.queued, notification.sent, notification.clicked) and an inbound REST trigger for Zapier or Make, configured under Settings -> Automations.
  • Abandoned-browse reminders for public posts and pages. The timer resets on each view; products are skipped so WooCommerce abandoned-cart alerts stay separate.
  • Comment notifications for post authors and comment replies, scoped by post type.
  • Site management notifications for administrators with manage_options: moderation queue, pending review, and published post alerts.
  • WooCommerce admin order alerts, stock alerts, customer order status updates, customer order notes, and delayed cross-sell follow-ups.
  • Trending Today notifications based on daily post view milestones, with per-day caps.
  • Notification templates for posts, comments, admin alerts, WooCommerce events, cross-sell messages, and trending alerts.
  • Statistics for deliveries, clicks, subscriber growth, clicked links, category CTR, audience-segment CTR, A/B variant CTR, and AI digest conversion.

PHP integration

Developer API

Developers can queue notifications directly from a theme, plugin, or custom automation. The helper returns the notification ID on success or a WP_Error on failure.

$notification_id = pushai_trigger_notification( array(
  'title'           => 'New update',
  'body'            => 'A new article is available.',
  'url'             => home_url( '/news/' ),
  'image'           => '',
  'source_type'     => 'developer',
  'source_id'       => 0,
  'target_user_ids' => array( 12, 34 ),
  'exclude_user_ids'=> array( 56 ),
  'scheduled_at'    => '2026-09-22 09:00:00',
  'target_segment'  => array(
    'roles'     => array( 'editor' ),
    'devices'   => array( 'mobile' ),
    'categories'=> array( 12, 18 ),
    'tags'      => array( 4 ),
  ),
  'actions'         => array(
    array( 'title' => 'Read', 'url' => home_url( '/news/' ) ),
  ),
  'ab'              => array(
    'title' => 'Fresh headlines',
    'body'  => 'Open the latest story.',
  ),
) );

Equivalent action form:

do_action( 'pushai_send_notification', array(
  'title' => 'Order ready',
  'body'  => 'Your order is ready for pickup.',
  'url'   => wc_get_endpoint_url( 'orders', '', wc_get_page_permalink( 'myaccount' ) ),
) );

Supported arguments

title, body, url, image, source_type, source_id, target_user_id, target_user_ids, target_guest_id, target_guest_ids, exclude_user_ids, scheduled_at (site timezone or UTC MySQL datetime), target_segment (Pro), actions (Pro), and ab (Pro). A non-empty segment without an active Pro license returns WP_Error pushai_segment_requires_pro.

License helpers

Use pushai_license_is_active(), pushai_license_is_active_cached(), and pushai_get_license() when building integrations that depend on Pro.

Browser integration

REST endpoints

GET/wp-json/pushai/v1/subscription-nonce

Returns a PushAI nonce and a fresh wp_rest nonce for the current browser session.

POST/wp-json/pushai/v1/subscriptions

Stores or updates the browser push subscription. Requires X-Pushai-Nonce and same-origin validation. Guests are accepted only when Guest subscriptions is enabled.

GET/wp-json/pushai/v1/subscriptions

Checks whether the current browser endpoint is active.

DELETE/wp-json/pushai/v1/subscriptions

Marks the current browser endpoint as unsubscribed. This remains available even if guest subscriptions are later disabled.

GET/wp-json/pushai/v1/notification-status

Returns the current logged-in user notification status.

POST/wp-json/pushai-pro/v1/click

Pro endpoint used by the service worker to record signed notification click events.

POST/wp-json/pushai/v1/trigger

Pro inbound automation. Requires an active license and X-PushAI-Token (or Authorization: Bearer). JSON body uses the same fields as pushai_trigger_notification(). Configure the token under Settings -> Automations.

Extension points

Actions and filters

pushai_send_notificationActionQueue a notification with the same arguments accepted by pushai_trigger_notification().
pushai_notification_queuedActionRuns after a notification row and queue job are created.
pushai_notification_failedActionRuns when a developer-triggered notification cannot be queued.
pushai_notification_delivery_completedActionRuns after delivery finishes with success, failed, and expired counts.
pushai_loadedActionRuns after PushAI initializes shared services.
pushai_should_create_post_notificationFilterAllow or block automatic notification creation for a published post.
pushai_post_notification_argsFilterModify title, body, URL, image, targeting, or context before a post notification is queued.
pushai_should_send_to_subscriptionFilterDecide per subscription whether it should receive a notification.
pushai_notification_payloadFilterChange the browser payload before delivery. Pro uses this to add click tracking.
pushai_utm_parametersFilterCustomize or disable UTM parameters appended to notification URLs.
pushai_skip_inactive_targetsFilterControl whether targeted users without active subscriptions are pruned before queueing.
pushai_localize_configFilterExtend the front-end JavaScript config. Pro uses this for the permission prompt.
pushai_can_target_segmentFilterAllow a non-empty target_segment. Defaults to false; PushAI Pro returns true when licensed.
pushai_can_use_actionsFilterAllow notification action buttons. Defaults to false; PushAI Pro returns true when licensed.
pushai_can_ab_testFilterAllow A/B variant copy. Defaults to false; PushAI Pro returns true when licensed.
pushai_notification_composer_fieldsActionExtra fields inside the notification composer. PushAI Pro adds audience segments, action buttons, and A/B fields.
pushai_notification_scheduledActionRuns after a scheduled notification row is created, with the UTC datetime.
pushai_notification_clickedActionRuns after a signed click is recorded.
pushai_queue_batch_sizeFilterHow many queue jobs the processor claims per run.
pushai_delivery_chunk_sizeFilterHow many subscriptions one send job delivers before re-queuing the rest.
pushai_completed_job_retention_daysFilterHow long completed jobs stay in the queue table before automatic prune.
pushai_pro_notification_post_typesFilterAdjust Pro automatic notification post types.
pushai_pro_comment_notification_post_typesFilterAdjust Pro comment notification post types.

Storage

Data and privacy

Core tables

PushAI stores browser subscriptions, notifications, and queue jobs in WordPress database tables with the site table prefix.

Pro analytics

Pro creates a pushai_pro_analytics table for delivery and click events. Click tracking uses a signed token and rate limiting.

Subscriber data

Stored subscription data includes endpoint, public key, auth token, content encoding, device type, status, user ID or guest ID, and delivery timestamps.

Maintenance

Settings includes Clear Cache and Delete All Data. Delete All Data removes subscriptions, notifications, and jobs and cannot be undone.

Release notes

Changelog

Version 1.2.0

Free · Current
  • Changed: The minimum PHP version is 8.1. Bundled Web Push libraries are pinned to versions that run on PHP 8.1.
  • Improved: Large sends go out in subscription chunks (250 by default) so a queue job cannot time out. Delivery totals accumulate across chunks; email fallback runs after the last chunk.
  • Added: WP-CLI commands wp pushai queue process, wp pushai queue status, and wp pushai queue prune.
  • 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: Audience segment delivery (roles, devices, categories, tags), action buttons, A/B variant payloads, and signed webhook jobs. Targeting a segment, actions, or A/B without PushAI Pro returns a license error.
  • Added: A Preview button in the notification composer, a device filter on Subscribers, and higher-contrast admin badges.
  • Improved: Settings are cached for the current request. Completed jobs older than 7 days are pruned. Daily post view tracking runs only when Pro Trending Today is licensed and enabled.

Version 1.0.8

Pro · Current
  • Added: Outbound webhooks for notification.queued, notification.sent, and notification.clicked. Payloads are HMAC-signed (X-PushAI-Signature) and delivered through the Free queue. Configure them under Settings → Automations.
  • Added: Inbound REST trigger POST /wp-json/pushai/v1/trigger with an automation token, for Zapier, Make, or any HTTP client.
  • Added: Action buttons (up to two) and A/B tests in the notification composer. Variant CTR is shown on Statistics. Requires PushAI Free 1.2.0 or later.
  • Added: Abandoned-browse reminders for public posts and pages (not WooCommerce products). The timer resets on each view; one reminder is sent for the last article after the delay.
  • Improved: Audience segment category and tag fields now explain they match logged-in authors and approved commenters of those topics, not a topic interest list.

Version 1.0.7

Pro
  • Added: Audience segments in the notification composer — filter by WordPress role, device (mobile/desktop), category, and tag. Filters apply together; category and tag match authors and commenters of those topics. Requires PushAI Free 1.2.0 or later.
  • Added: Statistics now include click-through rates grouped by audience (Everyone, Specific users, Audience segment, and known campaign keys).
  • Added: target_segment on pushai_trigger_notification() is allowed when this site has an active Pro license.

Version 1.1.7

Free
  • 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.
  • 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.

Version 1.1.6

Free
  • 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.

Version 1.0.6

Pro
  • Added: A "Post updated" template for the new updated-post automation in PushAI Free, so an edit is announced in its own words instead of reusing the "new content published" wording. Requires PushAI Free 1.1.7 or later.
  • Added: Templates now cover the site-management alerts sent to administrators — comment awaiting moderation, post pending review, post published, and new subscribers. Previously these four had no editable template and always used their built-in wording.
  • Fixed: The Trending Today title and description fields on the Templates screen raised "Undefined array key" warnings, and the warning text broke the field markup, on any site that had never saved them.

Version 1.0.5

Pro
  • Changed: Comment, Site management, WooCommerce, and Trending Today settings each appear on their own Settings tab in PushAI Free and save independently, so one panel no longer overwrites another. Requires PushAI Free 1.1.5 or later.

Version 1.1.5

Free
  • 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.

Version 1.0.4

Pro
  • Fixed: Notification template placeholders (post title, site name) no longer leave HTML entities such as &quot; in delivered push titles and messages. Requires PushAI Free 1.1.4 or later for full coverage on all notification paths.

Version 1.1.4

Free
  • Fixed: Notification titles and messages no longer show HTML entities such as &quot; 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.

Version 1.1.3

Free
  • 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.

Version 1.1.2

Free
  • 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.

Version 1.1.1

Free
  • 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.

Version 1.0.3

Pro
  • Changed: PushAI Pro pricing is now $21/year.
  • Fixed: Customer order-note push notifications are sent only once per note. Duplicate deliveries from re-fired WooCommerce hooks are blocked, and WooCommerce order_note comments are excluded from regular comment notifications.

Version 1.1.0

Free
  • Added: The on-site permission popup is now a free feature. Enable and customize it from Settings — no Pro license required.
  • Added: Custom post type automation is now a free feature, including custom slugs.
  • Added: Built-in click tracking with signed links, plus Delivered and Clicks cards for the last 7 days on the Dashboard.
  • 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 for new sites.
  • Added: A dismissible review invitation on PushAI screens after 10 successful notifications.

Version 1.0.2

Pro
  • Changed: The on-site permission prompt, custom post type automation, and click tracking are now part of PushAI Free (1.1.0+) — they no longer require Pro. Saved settings and analytics data migrate automatically.
  • Changed: The Statistics dashboard now reads from the click-tracking data recorded by PushAI Free.

Version 1.0.2

Free
  • Added: Email fallback recipients list in notification history.
  • Added: Delete data on uninstall setting (Settings → Data & privacy). Off by default so data is kept if you reinstall later.

Version 1.0.1

Pro
  • New-subscriber admin alerts are now sent as a batched "+N new subscribers" digest with a configurable batch window, instead of one alert per subscriber.

Version 1.0.1

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

Version 1.0.0

Free & Pro
  • Initial release of PushAI Free and PushAI Pro.
  • Self-hosted web push, subscribe button, VAPID credentials, delivery queue, manual campaigns, and guest subscriptions.
  • Pro: AI digests, WooCommerce automation, comment notifications, site-management alerts, Trending Today, templates, statistics, and licensing.