NoticePilot – Remote Campaign Hub for WordPress Plugin & Theme Authors

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 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—without shipping new plugin releases. It operates via a hub-to-remote architecture: manage your campaigns centrally on your hub site, while a lightweight PHP SDK bundled in your plugin automatically fetches and renders them.

Who Is This For?

NoticePilot is built for WordPress plugin and theme developers who need to manage user communication across multiple remote installations from a single, self-hosted dashboard. It is not a tool for suppressing or customizing notices on a single site.

Key Features

• Hub-to-Remote Architecture — Manage campaigns from a single dashboard and distribute them to unlimited remote WordPress sites via a REST API. Zero SaaS dependencies.
• Single-File PHP SDK — Bundle a lightweight, self-contained PHP file in your plugin or theme. Initialize it with a single line of code.
• Privacy-First Analytics — Track impressions, clicks, and dismissals. Site URLs are MD5-hashed; no IP addresses, usernames, or cookies are ever saved.
• Audience Targeting — Target campaigns by plan type (free vs. pro), plugin/theme version (supporting <, >, =), and WordPress user roles.
• Campaign Scheduling — Set start/end dates for campaigns. Expired campaigns are automatically deactivated via WP-Cron.
• Rich HTML & Styles — Author custom layouts with standard HTML and CSS. Offers predefined styles (Info, Success, Warning, Error).
• Smart Dismissal & Snooze — Limit notice clutter with automatic dismissal periods (stored locally on remote sites using a FIFO queue) and optional snooze options.
• A/B Testing & Conversions (Pro) — Test campaign variants, set metric-based smart triggers, track conversion goals, and collect deactivation feedback.

How It Works

1. Create a Product — Add your plugin/theme in the hub to generate a unique API endpoint.
2. Add Campaigns — Write the HTML notice content, define targeting and scheduling rules, and publish.
3. Integrate the SDK — Download the single-file SDK, bundle it with your extension, and initialize it with one line of code.
4. Track Performance — Monitor impressions, clicks, and conversion rates from the dashboard.

SDK Integration Guide

Integrating the NoticePilot SDK into your plugin or theme is simple. Follow these steps to get started:

1. Setup the Hub & Product

Install NoticePilot on your central management site. Navigate to NoticePilot, click + Add New Product, enter your plugin/theme name, and toggle Enable this site. This generates your product’s API endpoint.

2. Create a Campaign

On your product card, click + Add Content. Enter your HTML notice content, configure optional targeting or scheduling rules, toggle Enable this offer, and save.

3. Bundle the SDK

Download class-remote-notice-client.php from the product card’s How To Integrate tab (or copy it from the plugin’s sdk/ folder) and place it in your extension (e.g., in an includes/ folder).

4. Initialize the SDK

Add the following code to your plugin’s main file or theme’s functions.php:

Replace your-product-slug and the api_url with the values from your product card.

SDK Configuration Options

The init() method supports several optional parameters: * schedule — Polling frequency: hourly, twicedaily, or daily (default). * capability — Required user capability to see notices. Default is manage_options. * dismiss_duration — Cooldown in seconds before a dismissed notice can reappear. Default is one week. * snooze_duration — Cooldown for « Remind me later » links. Default is one week. * max_notices — Maximum number of notices displayed at once. Default is 3. * screen_ids — Restrict notices to specific admin screen IDs. Default is [] (site-wide). * require_consent — Set to true to block tracking until the user explicitly consents (highly recommended for WordPress.org compliance). * plugin_version — Current version string to enable version targeting on the hub. * is_pro — Set to true when Pro features/plans are active to enable plan targeting.

Advanced SDK Features

• Analytics Consent (WordPress.org Guideline 7 Compliance): If require_consent is set to true, control tracking dynamically using: Noticepilot_Remote_Notice_Client::grant_consent( ‘product-slug’ ); Noticepilot_Remote_Notice_Client::revoke_consent( ‘product-slug’ );

• Conversion Goals (Pro): Track high-value user conversions (e.g., upgrading to Pro): Noticepilot_Remote_Notice_Client::track_goal( ‘product-slug’, ‘goal_key’ );

• Smart Triggers (Pro): Report usage metrics (e.g., forms created) to trigger milestone campaigns: Noticepilot_Remote_Notice_Client::set_metric( ‘product-slug’, ‘metric_key’, $count );

• Deactivation Feedback (Pro): Collect deactivation surveys without blocking deactivation: Noticepilot_Remote_Notice_Client::init( ‘product-slug’, [ ‘api_url’ => ‘…’, ‘deactivation_feedback’ => true, ‘plugin_file’ => ‘plugin-folder/plugin-file.php’, ] );

Verification & Testing

1. Force a Fetch: Run wp cron event run noticepilot_rnc_fetch_content_your-product-slug via WP-CLI on your test site to fetch campaigns immediately.
2. Check Database: Verify campaigns are cached in wp_options under the key noticepilot_rnc_your-product-slug_contents.
3. Verify Render: Navigate to the admin dashboard on your test site to see the notice and test its dismissal.
4. Verify Analytics: Check NoticePilot → Analytics on your hub site to see impression and click tracking roll up (typically hourly).