Main Header

Capture toasts

Updated on July 30, 2026

Tier 1 (Plus) and above can show short, self-dismissing frontend notices when a service successfully sends an event while you browse the public site. Capture toasts are off by default and configured per integration on that service's Settings tab.

They complement Connection Tests and Delivery Log and Developer diagnostics — useful when you want immediate confirmation during checkout flows, form submissions, or theme testing without opening wp-admin.

Enable capture toasts

  1. Confirm Tier 1+ is active — Free vs SignalPress Pro.
  2. Open an integration (for example SignalPress → PostHog → Settings).
  3. Under Toast, check Show while browsing the site.
  4. Save changes.

Repeat for each service that should show toasts. Other integrations stay silent unless you enable them separately.

Who sees toasts

TierDefault audienceCustom audience
1 (Plus)Site administrators (manage_options)Locked — upgrade prompt shown
2 (Pro)Site administrators when Toast audience rules are emptyOptional user/role rule groups

Toast audience uses the same AND/OR rule builder as Request rules, but only User and Role conditions are available. Leave the rules empty to keep the Tier 1 default (administrators only).

Capture toasts never appear to logged-out visitors.

What the toast shows

Each toast includes:

  • The integration name (for example PostHog or Slack)
  • The event name that was sent (for example order_completed)

Toasts auto-dismiss after a few seconds. They do not include payload data, credentials, or delivery error details.

When toasts appear

SignalPress queues a toast after a successful server-side delivery on the signalpress/after_delivery hook when the delivery status is dispatched, queued, or success.

On the frontend, logged-in eligible viewers receive toasts through:

  • A bootstrap payload on the current page load
  • A lightweight REST poll at /wp-json/signalpress/v1/capture-notices
  • The X-SignalPress-Capture-Notices response header on same-origin AJAX and fetch requests
  • Immediate feedback when SignalPress.capture() returns capture toasts in its REST response
  • Immediate feedback when SignalPress.analytics() sends through a service with toasts enabled

Cross-page navigation

When a capture triggers during AJAX (for example add-to-cart), notices are stored in sessionStorage and replayed on the next full page load (for example the thank-you page). At most five recent notices are kept per browser tab session.

Limitations

  • Requires a logged-in user who passes the audience rules.
  • Server-side captures during WP-Cron, WP-CLI, or other requests without a logged-in user do not queue frontend toasts for later.
  • Toasts confirm delivery initiation, not downstream processing inside the third-party service.
  • Keep toasts disabled on production unless your team wants the extra UI noise.
SettingLocation
Capture toasts toggleIntegration Settings → Developer diagnostics
Toast audience rulesIntegration Settings → Toast audience (Tier 2)
Browser console loggingSame Developer diagnostics section
PHP error log diagnosticsSame Developer diagnostics section

See Pro debugging for the full Developer diagnostics reference.