Overview
Webhooks let you send Leadpipe events to your own endpoints when visitors are identified or updated. Each webhook can be configured around:- A destination URL
- A segment
- A pixel
- A trigger
- Delivery status and success rate
Inactive or Auto-disabled.
Trigger types
Once per visitor / First Match
Once per visitor / First Match
Use this when you want one delivery for each qualifying visitor. Existing webhook cards label this trigger
First Match.Every Update
Every Update
Use this when the downstream system should receive qualifying visitor updates after the first delivery.
Recommended workflow
1
Start with a narrow segment
Limit the first webhook to a clear slice of traffic so you can validate the payloads and delivery behavior.
2
Pick the right trigger
Choose the send frequency that matches how your downstream system handles repeat deliveries.
3
Monitor delivery health
Review deliveries, success rate, and inactive status before scaling the webhook to more traffic.
Testing and delivery history
Once the webhook is configured, you can send a test payload and review delivery history to confirm the endpoint is receiving data correctly. In the demo flow, repeated consecutive failures can cause a webhook to deactivate automatically.Add attribution to webhook payloads
Add custom parameters to your pixel script when your webhook needs to identify the client, campaign, source, or another label associated with a visitor. Leadpipe includes those values in the webhook payload when it identifies the visitor. See Add attribution to a pixel for the format, rules, and examples.When to use webhooks instead of integrations
Use webhooks when:- You need a custom destination
- You want full control over downstream processing
- An existing integration does not fit your workflow