説明

Run your entire audience — email, push, and social — from one WordPress dashboard, with AI drafting built in.

Beacon Campaign Sender brings campaign management that usually takes three or four separate tools into a single plugin. Write once, let AI help you polish it in your own brand voice, and reach subscribers by email, mobile push, and social media — without copy-pasting between services or wiring up glue code.

Key features

Email campaigns through Brevo — compose, preview, schedule, and send, with deliverability handled by Brevo’s API.
Audience management & segmentation — organize contacts, sync Brevo lists, and target the right people.
Mobile push notifications — deliver to devices through Firebase Cloud Messaging.
Social publishing with Zernio — post to 12+ platforms from the same composer.
AI-assisted drafting — generate and refine campaign content with the latest Claude (Opus 5, Sonnet 5, Fable 5) and OpenAI (GPT-5.6) models, running as reliable background jobs.
Brand voice control — keep every AI draft sounding like you.
Newsletter signup forms — drop a form on any page with a shortcode, or build your own with custom HTML.
WordPress email routing (optional) — route all of your site’s wp_mail() traffic through Brevo, replacing a separate SMTP plugin.
Privacy-friendly — subscriber, email-log, AI-job, and push-device data is stored locally on your own site. Subscriber, email-log, and push-device records integrate with WordPress personal-data exporters and erasers; AI-job records expire automatically within 30 days.

One dashboard, every channel, no glue code — so you can spend your time on the message, not the plumbing.

Uses External Services

Brevo

Beacon Campaign Sender sends email delivery requests and contact/list operations to Brevo when Brevo features are enabled.

If the optional WordPress Email Routing feature is enabled, Beacon Campaign Sender can also route global wp_mail() traffic from WordPress core and other plugins through Brevo.

Data sent:
– sender and recipient email addresses
– campaign subject and message content
– contact attributes and list identifiers

Service provider: Brevo
Service URL: https://www.brevo.com/
Privacy policy: https://www.brevo.com/legal/privacypolicy/
Terms: https://www.brevo.com/legal/termsofuse/

OpenAI

Beacon Campaign Sender sends prompts and selected campaign context to OpenAI when the OpenAI content-generation option is enabled.

Data sent:
– prompts entered by administrators
– selected post, product, image, or campaign context included in the generation request

Data stored by the service: generations run in OpenAI’s background mode, which stores the request and response on OpenAI’s servers (normally for at least 30 days; Zero Data Retention accounts store background responses for roughly ten minutes to enable polling) so interrupted results can be recovered.

Service provider: OpenAI
Service URL: https://openai.com/
Privacy policy: https://openai.com/policies/privacy-policy/
Terms: https://openai.com/policies/terms-of-use/

Anthropic

Beacon Campaign Sender sends prompts and selected campaign context to Anthropic when the Anthropic content-generation option is enabled.

Data sent:
– prompts entered by administrators
– selected post, product, image, or campaign context included in the generation request

Service provider: Anthropic
Service URL: https://www.anthropic.com/
Privacy policy: https://www.anthropic.com/privacy
Terms: https://www.anthropic.com/legal/consumer-terms

Firebase Cloud Messaging

Beacon Campaign Sender sends push notification requests to Firebase Cloud Messaging when manual Firebase push delivery is enabled.

Data sent:
– push notification title and message
– recipient device tokens
– optional deep link URLs

Service provider: Google Firebase
Service URL: https://firebase.google.com/
Privacy policy: https://policies.google.com/privacy
Terms: https://policies.google.com/terms

Zernio

Beacon Campaign Sender sends social-post publishing requests and webhook configuration data to Zernio when social publishing is enabled.

Data sent:
– social post content
– selected social account identifiers
– scheduling timestamps
– webhook endpoint URL and webhook status configuration

Service provider: Zernio
Service URL: https://zernio.com/
Privacy policy: https://zernio.com/privacy-policy
Terms: https://zernio.com/tos

BuddyBoss App

One-click integration with the BuddyBoss App, no configuration needed.

Privacy

Beacon Campaign Sender stores the following data locally in your WordPress database:

Subscriber records — email address, name, consent text, source, IP address, browser user agent, and referrer metadata for newsletter sign-ups.
Email logs — recipient addresses, subject, message body, headers, attachment metadata, sender details, delivery status, and error details for transactional email troubleshooting.
Push-device tokens — one token per subscribed browser or app, with its platform, subscription date, and (when the subscriber was logged in) the owning WordPress account. Tokens are deleted when a subscriber unsubscribes, on logout release, or automatically once Firebase reports them dead.
AI generation jobs — the prompt, selected campaign context, generated result, and job status for each AI generation. These records are retained for a maximum of 30 days and then deleted automatically.

WordPress personal-data export and erasure requests cover the subscriber, email-log, and push-device records. AI-job records are not included in the exporters/erasers; they expire automatically on the 30-day schedule instead.

Data sent to external services (Brevo, OpenAI, Anthropic, Firebase, Zernio) is described service-by-service in the Uses External Services section above.

Third-Party Libraries

Firebase JavaScript SDK 10.12.2

Beacon Campaign Sender bundles the Firebase JavaScript SDK (compat builds) for web push notifications, so no executable code is loaded from external servers at runtime.

Files: assets/js/vendor/firebase/firebase-app-compat.js, assets/js/vendor/firebase/firebase-messaging-compat.js
Official source: https://www.gstatic.com/firebasejs/10.12.2/firebase-app-compat.js and https://www.gstatic.com/firebasejs/10.12.2/firebase-messaging-compat.js
Project: https://github.com/firebase/firebase-js-sdk
License: Apache License 2.0 (Copyright Google LLC); a complete copy is bundled at assets/js/vendor/firebase/LICENSE

インストール

Upload the plugin to /wp-content/plugins/ or install it through the WordPress plugins screen.
Activate the plugin through the Plugins screen in WordPress.
Open Beacon Campaign Sender in the WordPress admin.
Configure the integrations you plan to use.

FAQ

Does this plugin use external services?

Yes. Beacon Campaign Sender can connect to external services depending on which features you enable.

Which external services can Beacon Campaign Sender use?

Beacon Campaign Sender can integrate with:

Brevo for email delivery, contact lists, and campaign data
OpenAI for AI content generation
Anthropic for AI content generation
Firebase Cloud Messaging for push notification delivery
Zernio for social publishing and webhook status updates

Does this plugin override `wp_mail()`?

It can, but only when an administrator enables the WordPress Email Routing setting. When that setting is active, WordPress core emails and emails sent by other plugins can be routed through Brevo instead of the site’s default mail transport.

Will my SMTP plugin conflict?

No. Campaign emails are always sent directly to Brevo’s API and do not pass through wp_mail(), so your SMTP plugin is never involved in campaign delivery. If you do not enable WordPress Email Routing, your SMTP plugin will continue to handle all other site email normally. If you do enable WordPress Email Routing, Beacon Campaign Sender will route wp_mail() traffic from WordPress core and other plugins through Brevo, in which case a separate SMTP plugin is no longer needed — please deactivate it to avoid conflicts.

How do I add an email signup form to my site?

Add the shortcode [bcsend_subscribe_form] to any page, post, or text/shortcode widget. The form collects an email address and consent, plus optional first and last name. New subscribers are added to the list(s) set in Beacon Campaign Sender > Settings > Default Subscriber Lists.

If enabled (the default), the form works on any page via the shortcode or your own custom HTML. You can turn the entire signup feature off under Beacon Campaign Sender > Settings > Signup Forms, which also stops the submit script and form CSS from loading.

Optional shortcode attributes:

style — “card” (default) or “inline”
show_names — “true” (default) or “false”
button_text — custom submit button label
list_ids — comma-separated Brevo list IDs that override the default list
class — extra CSS class(es) added to the form wrapper for styling

How do I change the look of the signup form?

You have three options, from easiest to most flexible:

Add CSS in Beacon Campaign Sender > Settings > Subscribe Form CSS. It applies to every subscribe form on the site, whether added by the shortcode or built as custom HTML, and is loaded after the built-in styles so your rules win. Scope rules to .bcsend-subscribe-form (or a class you add with the shortcode’s class attribute) so they do not affect the rest of the page.
Target the form’s class hooks from your theme stylesheet: .bcsend-subscribe-form, .bcsend-subscribe-form-row, .bcsend-subscribe-form-consent, .bcsend-subscribe-form-fine-print, and .bcsend-subscribe-form-message.
Use the [bcsend_subscribe_form style="inline" class="my-form"] attributes to drop most default styling and target your own class.

Can I use my own HTML for the signup form?

Yes. The plugin’s submit script loads on every front-end page and handles any form that uses the expected markup, so you can build the form however you like. The required pieces are:

The wrapper element has the class bcsend-subscribe-form.
The wrapper has a data-bcsend-rest-url attribute pointing at the subscribe REST endpoint (/wp-json/beacon-campaign-sender/v1/subscribe).
An email input and a consent checkbox.

Optional fields are first_name, last_name, list_ids (a hidden input; falls back to the default lists when empty), a honeypot anti-spam field, and a .bcsend-subscribe-form-message element for status messages. A ready-to-copy snippet is shown under Beacon Campaign Sender > Settings > Embed in Custom HTML.

評価

このプラグインにはレビューがありません。

貢献者と開発者

Beacon Campaign Sender はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献しています。

El Proximus

“Beacon Campaign Sender” をあなたの言語に翻訳しましょう。

開発に興味がありますか ?

コードを閲覧するか、SVN リポジトリをチェックするか、開発ログを RSS で購読してみてください。

変更履歴

1.1.0

AI generation
– Generation now runs as a tracked background job instead of one long browser request: a live status with elapsed time, survives page reloads and closed tabs (results finished while you were away are offered as Apply/Discard), never runs the same job twice, and protects newer edits from being overwritten by a late result.
– The campaign composer now pauses editing and delivery controls while an AI result is expected to apply automatically. If OpenAI recovery or a fallback decision takes over, editing unlocks and the eventual result requires Apply/Discard.
– New AI models: Claude Opus 5 (recommended), Sonnet 5 (fast and economical), and Fable 5 (premium, opt-in) with previous Claude models under Legacy; OpenAI GPT-5.6 Terra (recommended), Sol, and Luna running in OpenAI’s server-side background mode. Existing installs keep their saved model.
– If Fable 5’s stricter safety system declines an ordinary request, Beacon retries once on Opus 5 and labels the result honestly (on by default, refusals only – never errors or timeouts).
– Interrupted OpenAI generations are recovered from OpenAI’s servers instead of abandoning an already-billed result; gateway timeouts (HTTP 408/504/524) are never retried automatically, so a slow generation can no longer be billed twice.
– A generation can no longer be started for a deleted or already-sent campaign, and a dead background job can no longer block a campaign for other users.

Composer & social
– Save/schedule results (including validation errors) appear right next to the buttons and stay until addressed, instead of a vanishing top-of-page notice.
– Flat one-click social account checkboxes replace the platform-toggle + dropdown flow; “Include Social Posts” only changes when you change it and round-trips faithfully.
– Settings > Social composer defaults: mark accounts as defaults (one per platform, enforced) and optionally start new campaigns with social on; syncing accounts preserves your defaults.
– Character counters actually work (280 X/Twitter, 3,000 LinkedIn, 2,200 Instagram).

Templates
– The Templates screen shows each whole email scaled to its card; click a design to start a campaign from it.
– A real default template (pinned first with a star) replaces the old Base Template setting, with automatic migration; deleting the default promotes another. Every new campaign opens with the default loaded.
– Template preview is a proper centered modal (Esc, x, or click-outside to close).

Push notifications
– Push works without any companion app: web push via Firebase (service worker, subscribe button or floating bell), Firebase Topics for existing apps, token import, and an open registration endpoint for custom apps with an app-key path.
– Custom-app device ownership now requires per-user WordPress REST authentication; the shared app key alone can register only an anonymous All Subscribers device. Anonymous browser token refreshes no longer erase a known owner, and browser logout explicitly releases the association on shared devices.
– Device registry with per-IP throttling and a capacity cap that counts only active devices; dead tokens are cleaned up automatically after 30 days, and a Remove Stale Devices button frees capacity immediately.
– Test Push is implemented for Firebase-only sites; pushes stuck mid-send recover automatically and can be deleted; Firebase topic names are no longer silently lowercased.

Reliability & security
– Settings saves are side-effect free while cleaning input: remote syncs (Zernio webhook, Brevo domain check) fire exactly once per save and only when their fields changed – a slow third party no longer freezes saving unrelated settings.
– Users granted the plugin’s own manage capability can actually save Settings (previously blocked by a WordPress core capability check).
– Destructive template actions (delete, duplicate, change default) require the manager capability; delegated campaign editors keep their full visible workflow.
– Rejected webhook requests can no longer flood the database or bury legitimate diagnostics; schema checks run once per upgrade instead of ~25 queries on every page view; background workers no longer leak the campaign author’s identity into later tasks.
– If stored API keys can no longer be decrypted (e.g. security keys rotated during a host migration), Beacon says so and asks for re-entry instead of sending unusable values to providers.
– Multisite: network activation sets up every site, new sites are provisioned automatically, and uninstall cleans the whole network.
– Removed a hardcoded fallback subscriber list; an empty Default Subscriber Lists setting now honestly means no default lists.

1.0.6 (unreleased)

Composer save and schedule results (including validation errors) now appear right next to the Save/Schedule buttons and stay visible until addressed, instead of a top-of-page notice that disappears after five seconds.
Replaced the social platform toggle + account dropdown flow with flat one-click account checkboxes: every connected account is listed visibly and picking one is a single click.
Generated content no longer switches on “Include Social Posts” by itself; the checkbox only changes when you change it, and its saved state is restored faithfully when reopening a campaign.
New Settings > Social composer defaults: mark connected accounts as defaults and optionally start every new campaign with social posting on and those accounts pre-selected.

1.0.5

Added a Settings > Access tab to grant campaign access (Dashboard, Composer, and Campaign Queue) to existing Author-or-higher users without making them administrators.
Assigned non-admin users get a streamlined, mobile-friendly campaign workspace with the WordPress admin sidebar, toolbar, and footer hidden on those screens, plus quick links back to WP Admin, their profile, and log out.
Made the Composer mobile-responsive so campaigns can be created and sent from a phone.
Hardened API key handling: saved secrets (Brevo, Zernio, Anthropic, OpenAI, and the Firebase service account) are no longer printed back into the settings form and are only overwritten when you explicitly choose to replace them, ignoring browser autofill.
Retired the separate Campaign Manager role in favor of the per-user Access settings.

1.0.4

Added an “Enable signup forms” setting (on by default). When unchecked, the [bcsend_subscribe_form] shortcode renders nothing, the submit script and form CSS no longer load, and the subscribe endpoint rejects submissions.

1.0.3

Documented the public subscribe form: added the [bcsend_subscribe_form] shortcode usage to the readme and the Settings screen.
Added a “class” shortcode attribute for adding custom CSS classes to the form wrapper.
Added a “Subscribe Form CSS” setting that is applied after the default styles for easy restyling.
The subscribe submit handler now loads on all front-end pages, so custom HTML forms using the documented markup work without the shortcode. Added an “Embed in Custom HTML” reference snippet to Settings.
Updated the selectable Anthropic models to the current lineup: added Claude Opus 4.8 and Opus 4.7, kept Sonnet 4.6 (recommended) and Haiku 4.5, and marked Opus 4.6 as legacy.
Subscribe Form CSS now also loads on pages that use only custom HTML forms, not just shortcode pages.
The subscribe form status message no longer clears custom classes on submit; only the is-success and is-error state classes are toggled.
Added GPT-5.5 to the OpenAI model choices and removed GPT-4.1 mini.

1.0.2

Reply-To moved from the campaign composer to plugin Settings, with optional per-campaign override available to automations.
Added “Sync Brevo Lists” button to the Audiences screen and “Regenerate HTML” button to the campaign composer.
Scheduled sends now create or update the Brevo campaign at send time; composer preview emails use the same direct Brevo path for accurate Reply-To handling.
Shortened the readme short description to meet the WordPress.org 150-character limit.

1.0.1

Keeps the Abilities Bridge integration card visible for discoverability and populates abilities only after the Bridge integration setting is enabled.
Campaign composer Reply-To field now suggests addresses derived from the site’s admin email and domain instead of hardcoded defaults.

1.0.0

Initial public release on WordPress.org.