[WordPress] 外掛分享: NoticePilot – Remote Campaign Hub for WordPress Plugin & Theme Authors

首頁外掛目錄 › NoticePilot – Remote Campaign Hub for WordPress Plugin & Theme Authors
WordPress 外掛 NoticePilot – Remote Campaign Hub for WordPress Plugin & Theme Authors 的封面圖片
全新外掛
安裝啟用
尚無評分
25 天前
最後更新
問題解決
WordPress 5.8+ PHP 7.4+ v1.5.0 上架:2026-05-11

內容簡介

NoticePilot 是一個專為 WordPress 外掛和佈景主題作者設計的遠端活動分發平台,讓開發者能夠集中管理多個遠端網站的公告、更新提示和銷售橫幅,無需發佈新版本。此外掛提供簡單的操作介面,提升用戶溝通效率。

【主要功能】
• 集中式管理:從單一控制台管理活動並分發至無限遠端網站
• 輕量級 PHP SDK:只需一行程式碼初始化,便可輕鬆整合
• 隱私優先分析:追蹤展示次數、點擊率及關閉情況
• 受眾定位:依計畫類型及用戶角色精準鎖定活動
• 活動排程:設定活動的開始與結束日期,自動停用過期活動
• 自訂樣式:使用標準 HTML 和 CSS 創建自訂佈局

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.5.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「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

Create a Product — Add your plugin/theme in the hub to generate a unique API endpoint.
Add Campaigns — Write the HTML notice content, define targeting and scheduling rules, and publish.
Integrate the SDK — Download the single-file SDK, bundle it with your extension, and initialize it with one line of code.
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:
require_once __DIR__ . '/includes/class-remote-notice-client.php';

add_action( 'plugins_loaded', function() {
Noticepilot_Remote_Notice_Client::init( 'your-product-slug', [
'api_url' => 'https://your-hub-site.com/wp-json/noticepilot/v1/content/your-product-slug',
'schedule' => 'daily',
'capability' => 'manage_options',
'dismiss_duration' => WEEK_IN_SECONDS,
] );
} );

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

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.
Check Database: Verify campaigns are cached in wp_options under the key noticepilot_rnc_your-product-slug_contents.
Verify Render: Navigate to the admin dashboard on your test site to see the notice and test its dismissal.
Verify Analytics: Check NoticePilot → Analytics on your hub site to see impression and click tracking roll up (typically hourly).

延伸相關外掛

文章
Filter
Mastodon