Wire churn signals into Whisperr

Pick your SDK

Instrument your backend first: payment failures, cancellations, trial expiry and usage drops live there. Add the browser or mobile SDK after, for engagement signal.

WebAny browser app. ~3KB, never loses exit events.ReactProvider + hook over the web SDK.Next.jsApp Router bindings, auto pageviews.Node.jsServer-side, with Express middleware.PythonServer-side, with Django middleware.PHP / LaravelFacade, flushes after the response..NETASP.NET Core DI, net8.0 + netstandard2.0.FlutterDurable offline queue, survives restarts.

Or call the API directly

The ingestion API is three endpoints behind https://api.whisperr.net. Building your own client? Read delivery, retries & idempotency first; a stable $message_id per event is what makes retries safe.

POST/v1/events/batchup to 500 events→POST/v1/events/tracksingle event→POST/v1/identifytraits + channels→

Before you ship

Event designWhat to track, snake_case naming, one user id everywhere.KeysIngestion keys (wrk_…) are publishable. Dashboard → Developer → API Keys.Delivery contractRetain on auth errors, retry transient, drop malformed. Dedup via $message_id.