Webhooks — send us your own events

If a tool is not in the catalog — an internal system, a niche CRM, a booking platform — it can still feed Prooflytics: send its events to your webhook endpoint as plain JSON.

Setting up

1. In Settings → Data sources, create a webhook source. You get a unique endpoint URL and a signing secret.
2. Point your system at the URL — every event is a simple POST with a JSON body and Content-Type: application/json. The setup panel shows ready-to-copy snippets, including the signature header.
3. Send a few real events, then map their fields — Prooflytics shows you what arrived and you say which field is the event name, which is revenue, and so on. The mapping screen works from your actual payloads, so you are never mapping blind.
4. Activate the source. Until you do, arriving events are held as drafts so you can experiment safely.

Signatures

Each request carries a signature header computed from your signing secret, so we can verify events really came from you. You can reveal or rotate the secret from the source's settings at any time — rotate it immediately if you suspect it leaked.

What to send

Anything that marks a business moment: a lead created, a demo booked, a deal won, a payment received. Include a way to tie the event to a person or session where you can — that is what lets attribution connect the event back to the channel that caused it.

Each webhook is its own source

Webhooks are treated as separate business domains — a bookings webhook and a payments webhook stay distinct in filtering and reporting rather than being merged into one anonymous stream, and each counts as one connected data source.