Diagnostics and Delivery Logs
Diagnostics help buyers troubleshoot delivery issues without waiting for manual investigation.
These tools are especially useful for buyers receiving leads through webhook, Google Sheets, CRM, or other automated delivery methods.
What diagnostics may include
Depending on account access, the Diagnostics page may show:
Recent delivery attempts.
Delivery method.
Delivery timestamp.
Response status.
Response code.
Response snippet.
Delivery latency.
Attempt number.
Final delivery outcome.
Test delivery results.
Delivery status examples
Status | Meaning |
|---|---|
Successful | The delivery destination accepted the lead. |
Failed | The delivery destination rejected the request or returned an error. |
Timed Out | The destination did not respond in time. |
Retried | The platform attempted delivery again. |
Pending Review | The delivery may require manual review or support follow-up. |
Common webhook problems
Problem | What to check |
|---|---|
401 or 403 response | Authentication, tokens, IP allowlist, or authorization rules. |
400 response | Required fields, payload schema, or validation rules. |
404 response | Webhook URL path or route configuration. |
500 response | Receiving system error or CRM/API outage. |
Timeout | Endpoint speed, firewall rules, server availability, or long processing time. |
Missing CRM record | Field mapping, duplicate handling, or CRM-side validation. |
Best practices
Respond quickly to webhook requests.
Return a clear success response when a lead is accepted.
Avoid long-running processing before returning a response.
Log the delivery ID in your receiving system.
Use test deliveries before changing production endpoints.
Contact support if failures continue after validating your endpoint.
Diagnostics are intended to help buyers and technical teams identify delivery problems faster.