Major admin UI upgrade with a new React-powered interface, REST API workflows, and improved extensibility for Pro add-ons. Existing campaigns remain fully compatible.<\/p>","1.2.0":"
Introduces the Free + Pro model (Freemius) and SDK 1.3.0 with opt-in deactivation feedback. The free hub is unchanged in behaviour; Pro is an optional add-on. Re-download the SDK to enable deactivation feedback in your plugins.<\/p>","1.1.0":"
Adds campaign templates, live preview, notice styles, placement control, snooze, import\/export, test-site exclusion, and SDK 1.2.0 with an analytics consent mode plus a dismiss-duration fix. Re-download the SDK for your plugins to get the new options. Database is upgraded automatically.<\/p>","1.0.1":"
This release includes important security hardening for the admin form handler and the remote SDK. All users are encouraged to upgrade.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3549159,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3562957,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3562957,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.1","1.5.0"],"block_files":[],"assets_screenshots":{"screenshot-01.png":{"filename":"screenshot-01.png","revision":3556777,"resolution":"1","location":"assets","locale":"","width":1189,"height":721},"screenshot-02.png":{"filename":"screenshot-02.png","revision":3556777,"resolution":"2","location":"assets","locale":"","width":1369,"height":737},"screenshot-03.png":{"filename":"screenshot-03.png","revision":3556777,"resolution":"3","location":"assets","locale":"","width":918,"height":944},"screenshot-04.png":{"filename":"screenshot-04.png","revision":3556777,"resolution":"4","location":"assets","locale":"","width":810,"height":930}},"screenshots":{"1":"NoticePilot Dashboard<\/strong> \u2013 Centralized hub to manage products, launch campaigns, and configure SDK integrations.","2":"Campaign Analytics<\/strong> \u2013 Track performance, impressions, clicks, and conversion rates across all remote installations.","3":"SDK Integration<\/strong> \u2013 Simple, step-by-step guide to download and initialize the remote notice client SDK.","4":"Add Campaign<\/strong> \u2013 Create HTML campaigns with customized start dates, end dates, and targeting rules."}},"plugin_section":[],"plugin_tags":[1588,26308,7557,4906,244981],"plugin_category":[],"plugin_contributors":[252241,209471],"plugin_business_model":[],"class_list":["post-297409","plugin","type-plugin","status-publish","hentry","plugin_tags-a-b-testing","plugin_tags-admin-notices","plugin_tags-announcements","plugin_tags-notifications","plugin_tags-plugin-analytics","plugin_contributors-muaz404","plugin_contributors-spiderdevs","plugin_committers-akramhossain","plugin_committers-alimran01","plugin_committers-spiderdevs","plugin_support_reps-spiderdevs"],"banners":{"banner":"https:\/\/ps.w.org\/noticepilot\/assets\/banner-772x250.png?rev=3562957","banner_2x":"https:\/\/ps.w.org\/noticepilot\/assets\/banner-1544x500.png?rev=3562957","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/noticepilot\/assets\/icon-256x256.png?rev=3549159","icon_2x":"https:\/\/ps.w.org\/noticepilot\/assets\/icon-256x256.png?rev=3549159","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/noticepilot\/assets\/screenshot-01.png?rev=3556777","caption":"NoticePilot Dashboard<\/strong> \u2013 Centralized hub to manage products, launch campaigns, and configure SDK integrations."},{"src":"https:\/\/ps.w.org\/noticepilot\/assets\/screenshot-02.png?rev=3556777","caption":"Campaign Analytics<\/strong> \u2013 Track performance, impressions, clicks, and conversion rates across all remote installations."},{"src":"https:\/\/ps.w.org\/noticepilot\/assets\/screenshot-03.png?rev=3556777","caption":"SDK Integration<\/strong> \u2013 Simple, step-by-step guide to download and initialize the remote notice client SDK."},{"src":"https:\/\/ps.w.org\/noticepilot\/assets\/screenshot-04.png?rev=3556777","caption":"Add Campaign<\/strong> \u2013 Create HTML campaigns with customized start dates, end dates, and targeting rules."}],"raw_content":"\n NoticePilot is not another admin notice plugin.<\/strong> It is a self-hosted remote campaign distribution platform<\/strong> built specifically for WordPress plugin and theme authors.<\/p>\n\n If you maintain a WordPress plugin or theme running on hundreds or thousands of remote sites, NoticePilot lets you push announcements, update prompts, sales banners, or deprecation warnings centrally from your own site\u2014without shipping new plugin releases. It operates via a hub-to-remote architecture<\/strong>: manage your campaigns centrally on your hub site, while a lightweight PHP SDK bundled in your plugin automatically fetches and renders them.<\/p>\n\n NoticePilot is built for WordPress plugin and theme developers<\/strong> who need to manage user communication across multiple remote installations from a single, self-hosted dashboard. It is not<\/strong> a tool for suppressing or customizing notices on a single site.<\/p>\n\n Integrating the NoticePilot SDK into your plugin or theme is simple. Follow these steps to get started:<\/p>\n\n Install NoticePilot on your central management site. Navigate to NoticePilot<\/strong>, click + Add New Product<\/strong>, enter your plugin\/theme name, and toggle Enable this site<\/strong>. This generates your product's API endpoint.<\/p>\n\n On your product card, click + Add Content<\/strong>. Enter your HTML notice content, configure optional targeting or scheduling rules, toggle Enable this offer<\/strong>, and save.<\/p>\n\n Download Add the following code to your plugin's main file or theme's Replace The Analytics Consent (WordPress.org Guideline 7 Compliance):<\/strong>\nIf Conversion Goals (Pro):<\/strong>\nTrack high-value user conversions (e.g., upgrading to Pro):\n Noticepilot_Remote_Notice_Client::track_goal( 'product-slug', 'goal_key' );<\/p><\/li>\n Smart Triggers (Pro):<\/strong>\nReport usage metrics (e.g., forms created) to trigger milestone campaigns:\n Noticepilot_Remote_Notice_Client::set_metric( 'product-slug', 'metric_key', $count );<\/p><\/li>\n Deactivation Feedback (Pro):<\/strong>\nCollect deactivation surveys without blocking deactivation:\n Noticepilot_Remote_Notice_Client::init( 'product-slug', [\n 'api_url' => '...',\n 'deactivation_feedback' => true,\n 'plugin_file' => 'plugin-folder\/plugin-file.php',\n ] );<\/p><\/li>\n<\/ul>\n\n Most admin-notice plugins manage, dismiss, or suppress notices on a single WordPress installation. NoticePilot serves an entirely different purpose \u2014 it is a remote campaign distribution platform<\/strong> for plugin and theme authors. You create and manage campaigns on a central hub site, and a lightweight SDK embedded in your plugin automatically fetches and displays those campaigns across hundreds or thousands of remote installations. It also includes campaign analytics, audience targeting, and scheduling \u2014 capabilities not found in typical notice-management plugins.<\/p><\/dd>\n Yes. Campaign content supports full HTML, including inline styles, Yes, within its intended use case. Campaign content can only be created by administrators who have the No. Analytics events are recorded using fire-and-forget Yes. Each campaign supports three independent targeting dimensions:<\/p>\n\n Leave all targeting fields blank to display the campaign to every eligible user.<\/p><\/dd>\n The notice is hidden for the duration configured via the No. NoticePilot does not inject any admin notices into the WordPress dashboard of the site where it is installed. It provides only a management interface under its own admin menu page. Campaign notices are displayed exclusively on remote sites<\/strong> \u2014 and only when a plugin or theme author explicitly integrates the SDK.<\/p><\/dd>\n\n<\/dl>\n\n\nWho Is This For?<\/h4>\n\n
Key Features<\/h4>\n\n
\n
<<\/code>, ><\/code>, =<\/code>), and WordPress user roles.<\/li>\nHow It Works<\/h4>\n\n
\n
SDK Integration Guide<\/h3>\n\n
1. Setup the Hub & Product<\/h4>\n\n
2. Create a Campaign<\/h4>\n\n
3. Bundle the SDK<\/h4>\n\n
class-remote-notice-client.php<\/code> from the product card's How To Integrate<\/strong> tab (or copy it from the plugin's sdk\/<\/code> folder) and place it in your extension (e.g., in an includes\/<\/code> folder).<\/p>\n\n4. Initialize the SDK<\/h4>\n\n
functions.php<\/code>:<\/p>\n\nrequire_once __DIR__ . '\/includes\/class-remote-notice-client.php';\n\nadd_action( 'plugins_loaded', function() {\n Noticepilot_Remote_Notice_Client::init( 'your-product-slug', [\n 'api_url' => 'https:\/\/your-hub-site.com\/wp-json\/noticepilot\/v1\/content\/your-product-slug',\n 'schedule' => 'daily',\n 'capability' => 'manage_options',\n 'dismiss_duration' => WEEK_IN_SECONDS,\n ] );\n} );\n<\/code><\/pre>\n\nyour-product-slug<\/code> and the api_url<\/code> with the values from your product card.<\/em><\/p>\n\nSDK Configuration Options<\/h4>\n\n
init()<\/code> method supports several optional parameters:\n* schedule<\/code> \u2014 Polling frequency: hourly<\/code>, twicedaily<\/code>, or daily<\/code> (default).\n* capability<\/code> \u2014 Required user capability to see notices. Default is manage_options<\/code>.\n* dismiss_duration<\/code> \u2014 Cooldown in seconds before a dismissed notice can reappear. Default is one week.\n* snooze_duration<\/code> \u2014 Cooldown for \"Remind me later\" links. Default is one week.\n* max_notices<\/code> \u2014 Maximum number of notices displayed at once. Default is 3<\/code>.\n* screen_ids<\/code> \u2014 Restrict notices to specific admin screen IDs. Default is []<\/code> (site-wide).\n* require_consent<\/code> \u2014 Set to true<\/code> to block tracking until the user explicitly consents (highly recommended for WordPress.org compliance).\n* plugin_version<\/code> \u2014 Current version string to enable version targeting on the hub.\n* is_pro<\/code> \u2014 Set to true<\/code> when Pro features\/plans are active to enable plan targeting.<\/p>\n\nAdvanced SDK Features<\/h4>\n\n
\n
require_consent<\/code> is set to true<\/code>, control tracking dynamically using:\n Noticepilot_Remote_Notice_Client::grant_consent( 'product-slug' );\n Noticepilot_Remote_Notice_Client::revoke_consent( 'product-slug' );<\/p><\/li>\nVerification & Testing<\/h4>\n\n
\n
wp cron event run noticepilot_rnc_fetch_content_your-product-slug<\/code> via WP-CLI on your test site to fetch campaigns immediately.<\/li>\nwp_options<\/code> under the key noticepilot_rnc_your-product-slug_contents<\/code>.<\/li>\n\n
How is NoticePilot different from other admin notice plugins?<\/h3><\/dt>\n
Can I use custom HTML and CSS in my campaigns?<\/h3><\/dt>\n
<style><\/code> blocks, and custom layouts. Your content renders exactly as written on every remote site.<\/p><\/dd>\nIs it safe to store and serve raw HTML campaign content?<\/h3><\/dt>\n
manage_options<\/code> capability, and all form submissions are protected by WordPress nonce verification. HTML is stored without additional sanitization intentionally, to preserve inline CSS and custom styling. NoticePilot is a developer tool designed for trusted authors \u2014 not for end-user-generated content.<\/p><\/dd>\nDoes the plugin collect personal data from remote sites?<\/h3><\/dt>\n
navigator.sendBeacon()<\/code> calls. Before any data is written to the database, remote site URLs are MD5-hashed server-side. No IP addresses, usernames, cookies, user agents, or other personally identifiable information is ever collected or stored.<\/p><\/dd>\nCan I target campaigns to specific users or plan types?<\/h3><\/dt>\n
\n
<<\/code>, ><\/code>, =<\/code>, <=<\/code>, >=<\/code>).<\/li>\nWhat happens when a user dismisses a notice?<\/h3><\/dt>\n
dismiss_duration<\/code> SDK option. Dismissals are recorded locally on the remote site in wp_options<\/code> using a FIFO cleanup strategy that retains only the 20 most recent dismissed campaign IDs. During each fetch cycle, the SDK also automatically prunes stale IDs for campaigns that no longer exist on the hub.<\/p><\/dd>\nDoes installing NoticePilot add notices to my own site's dashboard?<\/h3><\/dt>\n
1.5.0<\/h4>\n\n
\n
\/noticepilot\/v1\/admin\/\u2026<\/code>) replaces the old form-POST handlers for every product\/campaign action (create, edit, delete, duplicate, import).<\/li>\nnoticepilot.campaignFieldGroups<\/code> JS filter (@wordpress\/hooks), so NoticePilot Pro injects its A\/B, snooze, and trigger fields as React components. Server-side, add-ons still receive their data via the noticepilot_campaign_data<\/code> filter.<\/li>\n1.4.1<\/h4>\n\n
\n
Analytics::get_range_totals()<\/code>, get_product_daily()<\/code>, and optional date bounds on get_product_summary()<\/code> \u2014 powering the enhanced Pro analytics dashboard (date ranges, trend deltas, activity chart). Backward compatible; no schema change.<\/li>\n<\/ul>\n\n1.4.0<\/h4>\n\n
\n
country_code<\/code> column and a cached, filterable resolver (noticepilot_geoip_lookup<\/code>, defaulting to ip-api.com, with CDN-header fast-path). Collected only when the hub owner enables it in Pro's analytics settings and Pro is active (noticepilot_geo_collection<\/code> filter). No per-visitor data.<\/li>\ncountry_code<\/code>); migrates automatically on update.<\/li>\n1.3.0<\/h4>\n\n
\n
set_metric()<\/code> for usage-milestone smart triggers, plus first-seen tracking for install-age triggers. The SDK runtime ships free; the rules that drive it are authored in Pro.<\/li>\nnoticepilot_accept_goal_events<\/code> filter \u2014 the free hub ignores conversion (goal) events unless an add-on opts in, keeping conversion analytics gated. Snooze and trigger data are exposed to the SDK via the existing noticepilot_api_content_item<\/code> filter.<\/li>\nsnooze_duration<\/code> and max_notices<\/code> config options; a campaign only shows a \"Remind me later\" link when a Pro-authored snooze flag is delivered.<\/li>\n<\/ul>\n\n1.2.1<\/h4>\n\n
\n
Noticepilot_Remote_Notice_Client::track_goal( 'slug', 'goal_key' )<\/code> reports a conversion, attributed to the campaign\/variant a site last saw. The hub records goal events (and accepts them after a campaign ends). Per-variant CVR and conversion summaries surface in NoticePilot Pro.<\/li>\n<\/ul>\n\n1.2.0<\/h4>\n\n
\n
deactivation_feedback<\/code> + plugin_file<\/code> options) \u2014 asks users why they deactivated your plugin (skippable, anonymous) and reports it to your hub.<\/li>\nnoticepilot_campaign_data<\/code>, noticepilot_api_content_item<\/code>, noticepilot_test_site_hashes<\/code> filters and the noticepilot_campaign_modal_fields<\/code> action \u2014 so add-ons plug in without core changes.<\/li>\n1.1.0<\/h4>\n\n
\n
screen_ids<\/code> option) instead of site-wide, following WordPress.org guideline 11.<\/li>\n