Guide
Plugin Notices
Author, schedule and measure independent in-plugin messages.
Reach customers inside the plugin
Plugin Notices delivers branded announcements, product promotions, plugin-release links and content/download notices in integrated plugin editors. Choose products, audience, schedule, trigger, priority and frequency. It is a separate channel from marketing email and from license enforcement.
Brand Manager supplies the developer name and highlight color. A public notice channel must be enabled explicitly. Customer notices use verified account or native activation proof and remain subject to current product and recipient eligibility.
SoundSync
Publish a notice deliberately
-
Integrate the client
Use the current JUCE source package or independent notice-companion source. Register supported editor controls and navigation IDs in the host.
-
Enable the product channel
Configure product notice delivery and, if needed, its public audience. Licensing settings and offline grace are separate.
-
Prepare content
Select announcement, content, plugin update, download or promotion. Create a versioned resource for a release/content/download reference and select only compatible products.
-
Set timing and limits
Choose an IANA time zone, UTC start/end window, trigger, delay, priority, maximum displays and cooldown.
-
Review and publish
Save a draft, preview it, then publish the reviewed version. Future starts stay scheduled. Edits create a new draft version and cancel outstanding work for the replaced version.
-
Read actual outcomes
Inspect fetched, shown, clicked, dismissed and action outcomes separately. Pause or archive a campaign to stop outstanding delivery.
SoundSync
Timing and recipient behavior
| Setting or outcome | Meaning |
|---|---|
| Selected products | One campaign can target permitted compatible products. All integrated snapshots the current enabled products, not products added in the future. |
| Public and customer audiences | Public uses anonymous notice identity; customer delivery requires current account/native ownership proof. Neither establishes email subscription. |
| Editor events | Editor opened, editor available, or a registered control click. Send a stable event UUID when retrying the same event. |
| Delivery lease | One editor instance owns a delivery while current. Recheck before display/actions and release on editor destruction. |
| Actual shown | Recorded after the full card is painted, not after a fetch or collapsed badge. A crash can prevent a final receipt; counts are not an exactly-once display guarantee. |
| Dismissed | Suppresses this campaign for that recipient across its selected products and later versions. A new campaign is separate. |
| Offline or revoked | Do not fetch fresh notices offline. Eligibility is rechecked online; a disconnected client cannot instantly retract pixels already shown. |
A message cannot unlock or install a product
Notice tokens are independent, short-lived capabilities. A notice response does not activate a device, refresh offline grace, authorize audio or create a paid entitlement. Licensing controls, serial fields, passwords and payment controls cannot be registered as notice triggers.
Content downloads use current ownership checks and private expiring links. The maintained companion saves the selected file and checks its available size/checksum; it never automatically installs, extracts, imports or executes it. Import remains a deliberate customer action. A selected Windows or macOS instruction set is shown, otherwise General; the sets are not concatenated.
SoundSync
Reference and integration
SoundSync
Compose a real in-plugin notice
Current notice editor and card preview, shown with example product and campaign data.