Webhook
Not every system has a ready connector, which is why webhooks exist on both sides. On the way in, you post JSON with an event, identity fields and a free-form data block. On the way out, the platform delivers the resolved event to the URL you specify, already filtered and shaped the way your system expects.
Data collected
Data collected
- Inbound: event name, email, phone, session identifier and a free-form block
- Outbound: the resolved event, with the identified lead and the fields you map
- HMAC signature so your side can verify the origin
What it is for
What you can do with it
- Bring a homegrown CRM into the lead timeline
- Trigger automation when an opportunity changes stage
- Feed an internal system with the already-enriched event
How to connect
Step by step
- Step 1
Create the Webhook source and copy the URL and key.
- Step 2
Configure your system to post the contract JSON.
- Step 3
Watch the payload arrive in the debugger and build the filter on top of real data.
Frequently asked questions
What is the JSON format?
An object with the event name, whatever identity fields you have (email, phone, session identifier) and a free-form `data` block. Whatever lands in that block becomes available for filtering and field mapping.
Other integrations
CrazyLeads Pixel
Source
First-party tracking for your site, on your own domain, with identity that survives ad blockers.
View integration
Hotmart
Source
Sales, subscriptions, abandoned carts and member area activity — in real time by webhook plus a history sync.
View integration
Meta Conversions API
Destination
Server-side conversions to Meta, with identity already resolved and no dependency on the browser.
View integrationStart measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.