LeadByte Integration
The LeadByte integration sends your leads directly to your LeadByte instance through its REST API. This is a native integration, so LeadCapture connects directly to LeadByte without requiring a generic webhook. All deliveries are handled in the background with automatic retries and full delivery logging.
Setting Up LeadByte
- Open your funnel in the builder.
- Go to the Lead Delivery tab.
- Click Add LeadByte.
- Enter your LeadByte credentials:
- Endpoint URL: Your LeadByte REST API endpoint (e.g.,
https://your-instance.leadbyte.co.uk/restapi/v1.3/leads). - X_KEY: Your LeadByte API authentication key.
- Campaign ID: The campaign identifier for this funnel.
- Endpoint URL: Your LeadByte REST API endpoint (e.g.,
- Optionally enable Test Mode to send leads as test data (useful for initial setup).
- Click Test Connection to verify your credentials.
- Click Save.
What Data Is Sent
LeadByte receives all form field data along with these system fields that are automatically included:
| Payload Field | Description |
|---|---|
campid |
Your campaign identifier |
ipaddress |
Visitor's IP address |
source |
The page URL where the funnel was displayed |
user_agent |
Browser and device information |
trustedform_cert_url |
TrustedForm certificate (if enabled) |
optinurl |
The opt-in URL (same as source) |
optindate |
Date of opt-in (YYYY-MM-DD format) |
Field Mapping
LeadByte uses the webhook field names you configure on each form field. Common LeadByte field names include:
firstname,lastname,email,phone1address1,city,county,postcodedob(date of birth)
Set these in the Field Mapping section of the Lead Delivery panel for each field.
Test Mode
When Test Mode is enabled, every payload sent to LeadByte includes "testmode": "yes". This tells LeadByte to treat the lead as a test rather than a live submission. When you click "Test Connection", test mode is always used regardless of the toggle setting.
Remember to disable Test Mode before going live with real traffic.
Delivery and Retries
All LeadByte deliveries are asynchronous (processed in the background). If a delivery fails, LeadCapture retries automatically with the same schedule as webhooks: immediate, then 1 minute, 5 minutes, 30 minutes, and 2 hours.
LeadByte has a unique behavior where the API can return an HTTP 200 status code with an error in the response body. LeadCapture detects this and marks the delivery as failed so it is retried.
Partial Lead Support
Partial leads are delivered to LeadByte when captured. The payload includes is_partial_lead: true. When a partial lead later completes the form, an updated payload is sent with all fields.
Viewing Delivery Logs
To check the status of a LeadByte delivery:
- Go to Leads in your dashboard.
- Click on the lead.
- Look for the LeadByte Deliveries card showing delivery status, payload, and response.
Failed deliveries can be manually resent using the Resend button.
Key Differences from LeadProsper
| Feature | LeadProsper | LeadByte |
|---|---|---|
| Endpoint | Fixed (hardcoded) | User-configurable URL |
| Authentication | Credentials in payload | X_KEY HTTP header |
| Test Mode | Not available | Available (adds testmode flag) |
| Redirect from response | Supported | Not supported |
| Delivery mode | Async or sync | Always async |
Pro Tips
- Only one LeadByte integration can be added per funnel.
- The endpoint URL must use HTTPS for security.
- LeadByte has its own delivery queue, separate from webhooks, Zapier, and LeadProsper. Each integration retries independently.
- Always start with Test Mode enabled to verify your field mapping before sending live leads.
- If you see successful deliveries in LeadCapture but leads are not appearing in LeadByte, check your campaign configuration and field name requirements in LeadByte.