Main Header

Browser Events

Updated on July 27, 2026

Some integrations– notably PostHog with client-side capture enabled– can receive events directly from the browser. SignalPress exposes a small JavaScript API that mirrors the PHP capture pattern.

Server-side capture is covered in Capturing Events with sp_capture(). PHP destination lists use Service Targeting.

Client API

When a browser-capable service registers an adapter, use:

JavaScript

SignalPress.capture(
	'cta clicked',
	{
		location: 'homepage',
		buttonText: 'Get Started'
	},
	{
		source: 'marketing-site'
	}
);

signalpressCapture() is a shorthand alias for the same function.

Context options mirror PHP where applicable — see Event Context and Options.

Behavior

The browser API:

  • Normalizes event names
  • Rejects recursive or non-JSON payloads
  • Enforces a 1 MB encoded payload limit
  • Places application data under payload in the outgoing envelope
  • Sends through every registered browser adapter for enabled services

Client-side events go directly to the browser service. They do not create rows in the WordPress delivery ledger or Recent Activity view. Admin-side PHP tests still use Your First Connection Test.

Enable client-side capture

  1. Activate the integration (for example PostHog) on Integrations Overview
  2. Open the service Settings tab
  3. Enable client-side event capture (wording varies by service)
  4. Save credentials and confirm browser scripts load on the front end or admin as documented in that service’s Help tab

Premium destinations require Free vs SignalPress Pro.

Server vs browser routing

Advanced Event Routing and request rules apply to PHP captures. They do not gate browser adapters the same way. Treat browser events as a separate channel tied to the visitor’s session.

For server-only verification, use Test Shortcode or sp_capture() from Loading SignalPress Safely.

What to read next