Your First Connection Test

A connection test confirms that SignalPress can reach a service with the credentials you saved. Every integration that supports testing exposes a Send test signal button on its Settings tab.

This guide walks through running a test, reading the result, and fixing common failures. Complete Setup & Activating SignalPress and skim Integrations Overview first.

Before you test

Confirm these basics on the integration Settings tab:

1. The integration is active on SignalPress → Integrations.
2. Enable service is checked.
3. Required credentials or destination fields are filled in and saved.

Remote services also need your site to make outbound HTTPS requests. Local hosting firewalls or security plugins occasionally block these — if tests fail with connection errors, check with your host.

Send a test signal

1. Open the integration (for example SignalPress → Local or SignalPress → PostHog).
2. Stay on the Settings tab.
3. Click Send test signal.

SignalPress sends a signalpress_test event with a short message identifying the service and project. The request is blocking during a test so SignalPress can record success or failure immediately. Normal signal delivery is non-blocking where supported, or queued on Tier 2 — see Reliable Delivery and Event IDs.

Read the result on Settings

After the page reloads, look for the connection status near the test button:

• Connected — the last test succeeded
• Failed — the last test returned an error (message shown on screen)

The status reflects the most recent test for that service only.

Read the delivery log

Open the integration Logs tab (or SignalPress → Recent Activity for a cross-service view).

Retention depends on license tier — free sites keep roughly 24 hours and the latest 10 entries per service; Plus retains 90 days; Pro retains until cleared. See Free vs SignalPress Pro.

Each row includes:

Column	Meaning
Date / Time	When the event was recorded
Status	dispatched, failed, filtered, queued (Tier 2 background queue), connected (successful tests), or similar
Project	Project label from site or event context
Event	Event name (signalpress test for connection tests; signalpress_test for programmatic captures)
Actor	Email (logged-in user) or IP (anonymous visitor) — clickable in the table
Origin	Where the capture was initiated — when Capture origin is enabled under SignalPress → Settings
Message	Human-readable result
HTTP Status	Response code for tests; Async for normal non-blocking deliveries
Payload	Expandable redacted preview (when permitted)

On SignalPress → Recent Activity, rows also include a Service column identifying which integration handled the delivery.

Use Auto refresh on log tables to poll every 10 seconds. On Plus and Pro, use Download CSV to export the current view.

Click the expandable Payload preview to inspect a redacted copy of what was sent. Users without the View payloads permission (Tier 2 roles) may see rows without payload expansion. See Permissions and Access.

For a deeper reference on columns, retention, and permissions, see Connection Tests and Delivery Log.

Successful test

You should see:

• Status connected
• Event signalpress test
• A numeric HTTP Status (for example 200 or 202)

For Local, the event appears in the Local Logs tab as a stored record rather than a remote HTTP result.

Failed test

Failed rows include an error message from the remote service or from SignalPress validation. Common causes:

• Invalid or expired API key, token, or webhook URL
• Wrong region or host (for example EU vs US PostHog)
• Service disabled or misconfigured on the provider side
• Outbound HTTP blocked on the server
• Event blocked by routing rules (for non-test captures)

Open that service’s Help tab Troubleshooting section for provider-specific fixes.

Test with code (optional)

After a connection test succeeds, send a real signal from PHP:

PHP

sp_capture(
	'my_first_event',
	[
		'message' => 'Hello from SignalPress',
	],
	[
		'source'   => 'getting-started',
		'services' => [ 'local' ],
	]
);

Replace local with the service ID you configured (for example posthog, slack, or email). Full API details: Capturing Events with sp_capture() and Service Targeting.

Use SignalPress → sp_capture Builder to compose sample calls with a live PHP or JavaScript preview — sp_capture Builder.

You can also add the September 18, 2026 12:00 am shortcode to any page to send a test signal when the page is rendered — Test Shortcode. The shortcode broadcasts to every enabled service (no services filter) and sets context source to shortcode:signalpress_test. Cached pages may not run the shortcode on every view.

Test one service at a time

Connection tests always target the service whose Settings page you are on. To verify multiple destinations, repeat the test on each integration separately, or use services in sp_capture() once each individual test passes.

What to read next

• Setup & Activating SignalPress — install and enable services
• Integrations Overview — activation vs delivery
• sp_capture Builder — compose calls in wp-admin with copy/paste preview
• Capturing Events with sp_capture() — programmatic capture
• Connection Tests and Delivery Log — full log reference
• Event Context and Options — what appears in payload previews