NoticePilot – Remote Campaign Hub for WordPress Plugin & Theme Authors
| 开发者 |
spiderdevs
muaz404 alimran01 |
|---|---|
| 更新时间 | 2026年7月22日 20:37 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0.2 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
NoticePilot is not another admin notice plugin. It is a self-hosted remote campaign distribution platform built specifically for WordPress plugin and theme authors.
If you maintain a WordPress plugin or theme that runs on hundreds or thousands of sites, you need a reliable way to push announcements, update prompts, sale banners, or deprecation warnings to your users — without shipping a new plugin release for every message. NoticePilot solves this with a hub-to-remote architecture: you manage campaigns centrally on your own site, and a lightweight PHP SDK bundled in your plugin automatically fetches and displays them on every remote installation.
Who Is This For?
NoticePilot is purpose-built for WordPress plugin and theme developers who need to communicate with their users across multiple remote installations from a single, self-hosted dashboard. It is not a tool for managing or suppressing admin notices on a single site — there are many plugins already serving that purpose.
What Makes It Different?
Unlike most admin-notice plugins, NoticePilot is a complete developer communication platform:
- Hub-to-Remote Architecture — One central dashboard pushes campaigns to unlimited remote WordPress sites via a REST API. No third-party SaaS, no external dependencies — everything runs on your own WordPress installation.
- Single-File PHP SDK — Bundle one PHP file into your plugin or theme. Initialize with a single line of code. The SDK handles fetching, caching, rendering, and dismissal automatically.
- Privacy-First Analytics — Track impressions, clicks, and dismissals across all remote sites without collecting personal data. Remote site URLs are MD5-hashed before storage — no IP addresses, usernames, or cookies are ever saved.
- Audience Targeting — Deliver the right message to the right users by targeting campaigns based on plan type (free or pro), plugin version (with comparison operators like
<,>,=), and WordPress user roles. - Campaign Scheduling — Set start and end dates for time-sensitive campaigns. Expired campaigns are auto-disabled via WP-Cron — no manual clean-up required.
- Rich HTML Support — Write full HTML including inline CSS,
<style>blocks, and custom layouts. Your content renders exactly as authored on every remote site. - Smart Dismissal Handling — Users who dismiss a notice won't see it again for a configurable duration. Dismissals are stored locally on the remote site using a FIFO strategy, keeping only the 20 most recent dismissed IDs.
- Scalable Analytics Engine — Raw events roll up into daily summaries via an hourly WP-Cron job with automatic pruning. Built for scale — no unbounded table growth.
- Create a Product — Each product represents a plugin, theme, or service you maintain. NoticePilot generates a unique REST API endpoint for it automatically.
- Add Campaigns — Write rich HTML content, set optional scheduling and audience-targeting rules, then enable the campaign.
- Integrate the SDK — Download the single-file PHP SDK from your product card, bundle it with your plugin or theme, and initialize it with one line of code. The SDK polls your hub on a configurable schedule and renders active campaigns as WordPress admin notices on remote sites.
- Track Performance — Monitor impressions, clicks, dismissals, and click-through rates from the analytics dashboard. Drill down by product or by individual campaign with daily breakdowns.
- Plugin authors: Push update prompts, deprecation warnings, or feature announcements to all users of your plugin — without shipping a new release.
- Theme authors: Announce seasonal sales, new theme versions, or compatibility updates directly inside the WordPress admin on every active installation.
- Agency developers: Broadcast maintenance windows, policy changes, or onboarding tips across all client sites from a single central hub.
- Freemium plugins: Show upgrade prompts exclusively to free-plan users while displaying different messaging to pro users — all without code changes on the remote site.
安装:
Installing the Hub Plugin
- Upload the
noticepilotfolder to the/wp-content/plugins/directory of your central management site. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to NoticePilot in your WordPress admin sidebar to begin creating products and campaigns.
- In the NoticePilot dashboard, click the How To Integrate button on your product card.
- Click Download SDK to download the
class-remote-notice-client.phpfile. - Copy the file into your plugin or theme (e.g., into an
includes/subdirectory). - Add the following initialization code to your plugin's main file or your theme's
functions.php:
your-product-slug with the slug shown on your NoticePilot product card, and your-hub-site.com with the domain of the site running the NoticePilot hub plugin.
That single call is all you need to start displaying notices. Every other capability — snooze, frequency caps, screen placement, analytics consent, conversion goals, smart triggers, and deactivation feedback — is optional. Each is documented in the SDK Integration Guide section below, and the dashboard's How To Integrate → Add features panel gives you a copy-paste snippet for every one, pre-filled with your product slug.
Once initialized, the SDK automatically handles fetching, caching, rendering, and dismissing notices — no additional code required.屏幕截图:
常见问题:
How is NoticePilot different from other admin notice plugins?
Most admin-notice plugins manage, dismiss, or suppress notices on a single WordPress installation. NoticePilot serves an entirely different purpose — it is a remote campaign distribution platform 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 — capabilities not found in typical notice-management plugins.
Can I use custom HTML and CSS in my campaigns?
Yes. Campaign content supports full HTML, including inline styles, <style> blocks, and custom layouts. Your content renders exactly as written on every remote site.
Is it safe to store and serve raw HTML campaign content?
Yes, within its intended use case. Campaign content can only be created by administrators who have the manage_options 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 — not for end-user-generated content.
Does the plugin collect personal data from remote sites?
No. Analytics events are recorded using fire-and-forget navigator.sendBeacon() 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.
Can I target campaigns to specific users or plan types?
Yes. Each campaign supports three independent targeting dimensions:
- Plan type — Show to all users, free-plan users only, or pro-plan users only.
- Plugin version — Target by version number using comparison operators (
<,>,=,<=,>=). - WordPress user role — Restrict visibility to specific roles such as Administrator, Editor, and others.
What happens when a user dismisses a notice?
The notice is hidden for the duration configured via the dismiss_duration SDK option. Dismissals are recorded locally on the remote site in wp_options 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.
Does installing NoticePilot add notices to my own site's dashboard?
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 — and only when a plugin or theme author explicitly integrates the SDK.
更新日志:
1.5.0
- Rebuilt: The entire admin UI is now a React + JSX app (built with @wordpress/scripts) — hero, stats, product cards, and all dialogs are component-based, with modals and form fields as reusable components. Same look (reuses the existing styles); smoother, no full-page reloads.
- New: Authenticated REST CRUD (
/noticepilot/v1/admin/…) replaces the old form-POST handlers for every product/campaign action (create, edit, delete, duplicate, import). - New: Add-on extension point — the campaign modal exposes the
noticepilot.campaignFieldGroupsJS 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 thenoticepilot_campaign_datafilter. - Removed: The legacy jQuery admin script and PHP-rendered modals.
- All existing features preserved: templates, live preview, targeting, scheduling, notice styles, placement, import/export, "See More", and the SDK integration guide + download.
- Developer: Added range-aware analytics query methods to the data layer —
Analytics::get_range_totals(),get_product_daily(), and optional date bounds onget_product_summary()— powering the enhanced Pro analytics dashboard (date ranges, trend deltas, activity chart). Backward compatible; no schema change.
- Change: The Analytics screen has moved entirely to NoticePilot Pro, rebuilt as a modern React dashboard (charts, per-campaign detail, A/B variant comparison, conversions, CSV export). The free hub keeps the analytics data layer (event recording + hourly rollup) and the product/campaign stat ribbon.
- New: Opt-in geo (data layer) — a
country_codecolumn and a cached, filterable resolver (noticepilot_geoip_lookup, 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_collectionfilter). No per-visitor data. - Improvement: Analytics schema upgraded to 1.2.0 (adds
country_code); migrates automatically on update. - Removed: The legacy jQuery analytics page, its script, and its CSS.
- Change: A/B testing, conversion goals, smart triggers, and per-campaign snooze are now NoticePilot Pro features. The free hub keeps campaign push, scheduling, targeting, templates, live preview, placement, and analytics.
- New (SDK 1.5.0):
set_metric()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. - Developer: New
noticepilot_accept_goal_eventsfilter — 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 existingnoticepilot_api_content_itemfilter. - The SDK continues to support
snooze_durationandmax_noticesconfig options; a campaign only shows a "Remind me later" link when a Pro-authored snooze flag is delivered.
- New (SDK 1.4.0):
Noticepilot_Remote_Notice_Client::track_goal( 'slug', 'goal_key' )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.
- New: Freemius integration and a Free + Pro model. The free hub stays fully functional; the optional NoticePilot Pro add-on unlocks A/B testing, per-variant analytics, and deactivation feedback.
- New: A/B testing groundwork — campaigns can carry weighted variants (authored in Pro); the SDK splits traffic deterministically and tracks events per variant.
- New (SDK 1.3.0): Opt-in deactivation-feedback modal (
deactivation_feedback+plugin_fileoptions) — asks users why they deactivated your plugin (skippable, anonymous) and reports it to your hub. - New: Developer extension points are stable —
noticepilot_campaign_data,noticepilot_api_content_item,noticepilot_test_site_hashesfilters and thenoticepilot_campaign_modal_fieldsaction — so add-ons plug in without core changes. - Improvement: An A/B testing upsell appears in the campaign editor when Pro is not active.
- New: Campaign templates — one-click starting points for review requests, BFCM sales, update prompts, deprecation warnings, and feature announcements.
- New: Live notice preview — see exactly how a campaign renders as a WordPress admin notice before publishing.
- New: Notice styles — choose Info, Success, Warning, or Error styling per campaign.
- New: Placement control — restrict a campaign to the integrating plugin's own admin screens (via the SDK
screen_idsoption) instead of site-wide, following WordPress.org guideline 11. - New: "Remind me later" snooze — an optional gentler alternative to permanent dismissal.
- New: Import/export campaigns as JSON, and duplicate any campaign in one click.
- New: Test sites — exclude your own development/staging URLs from analytics so test traffic never skews campaign numbers.
- New (SDK 1.2.0): Analytics consent mode (
require_consent) withgrant_consent()/revoke_consent()helpers — keeps beacons off until the user opts in, for WordPress.org guideline 7 compliance. - New (SDK 1.2.0): Frequency cap (
max_notices) and configurablesnooze_duration. - Fix (SDK 1.2.0):
dismiss_durationis now honored — dismissed notices reappear after the configured window (previously dismissals were effectively permanent). - Improvement: Analytics schema now records per-variant events and conversion goals, laying the groundwork for A/B testing (NoticePilot Pro). Existing data is migrated automatically on update.
- Developer: New extension filters —
noticepilot_campaign_data,noticepilot_api_content_item,noticepilot_test_site_hashes— and thenoticepilot_campaign_modal_fieldsaction for add-ons.
- Security: Sanitized nonce input in the admin form handler.
- Security: Replaced inline
<style>output in the SDK with the properwp_add_inline_style()API. - Security: Replaced inline
<script>output in the SDK with the properwp_add_inline_script()API. - Improvement: Added an explicit
__return_truepermission callback to the public analytics REST API route to comply with WP REST API guidelines. - Improvement: Added plugin owner to the contributors list.
- Improvement: Updated readme tags and short description to better reflect the plugin's developer-focused, remote-distribution use case.
- Initial public release.
- Multi-product management with support for unlimited campaigns per product.
- Rich HTML campaign editor with full CSS and custom layout support.
- Campaign scheduling with automatic expiration handling via WP-Cron.
- Built-in analytics tracking for impressions, clicks, and dismissals.
- Analytics dashboard with both product-level and campaign-level breakdowns.
- Lightweight single-file PHP SDK for remote site integration, with auto-fetch, transient caching, and dismissal handling.
- Privacy-first analytics — remote site URLs are MD5-hashed before storage; no personal data is collected.