Skip to main content

​
Overview

Webhooks let you send Leadpipe events to your own endpoints when visitors are identified or updated. Webhooks Each webhook can be configured around:
  • A destination URL
  • A segment
  • A pixel
  • A trigger
  • Delivery status and success rate
Select Create Webhook, enter an HTTPS destination, then choose the segment, pixel, and send frequency. Create Webhook dialog The table also shows delivery volume, success rate, and whether a webhook has been marked Inactive or Auto-disabled.

​
Trigger types

Use this when you want one delivery for each qualifying visitor. Existing webhook cards label this trigger First Match.
Use this when the downstream system should receive qualifying visitor updates after the first delivery.
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. If a webhook shows Auto-disabled, review its failed deliveries and fix the receiving endpoint before enabling it again.

​
Verify your receiver

  1. Send a test from Leadpipe and save the redacted request body and response status in your own test logs.
  2. Check the event envelope and visitor fields in that payload. The Identification API uses different response wrappers, so an API response is not a substitute webhook fixture.
  3. Confirm the receiver accepts the payload and the destination record contains the expected fields.
  4. Test how your own receiver handles the same payload twice. Use an upsert or deduplication policy appropriate to the destination.
  5. Inspect one live delivery to verify segment, pixel, and trigger behavior. A successful synthetic test does not prove a visitor qualifies for live delivery.
Before relying on unattended delivery, confirm the webhook’s authentication or signature mechanism, retry schedule, timeout, and replay controls through your Leadpipe support channel. This guide does not establish those guarantees. Orbit destination signing and delivery operations have a separate contract.

​
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

​
How to read webhook status