How to Set Up Auto-Submit for Silent Lead Delivery
What Is Auto-Submit
Auto-submit is a background process that runs immediately after a lead capture form is completed. It takes the collected data, formats it according to your configuration, and sends it as an HTTP POST request to one or more destination URLs. The visitor never sees this process. From their perspective, they submitted a form and saw a confirmation message. Behind the scenes, the lead data was delivered to your CRM, emailed to your sales team, or posted to a lead buyer's intake system.
Auto-submit is essential for two scenarios. First, businesses that need leads in their existing CRM or workflow tools use auto-submit to sync captured data without manual imports. Second, lead generation businesses that sell leads to buyers use auto-submit to deliver leads to multiple buyer endpoints simultaneously, often combined with offer path routing.
Step-by-Step Setup
Before configuring auto-submit, you need to know where the data should go. This is typically a webhook URL from your CRM (HubSpot, Salesforce, Zoho, etc.), a custom API endpoint on your own server, or a buyer's lead intake URL. Most CRMs provide a webhook URL in their integrations or automation settings. If you are posting to your own system, set up an endpoint that accepts POST requests with JSON data.
In the Lead Generation app, open your capture form's settings and enable auto-submit. Enter the destination URL and configure which fields should be included in the POST data. You can send all collected fields or select specific ones.
Different systems expect different field names. Your form might collect "phone" but your CRM expects "phone_number." Configure field mapping to rename your form fields to match what the destination system expects. This prevents integration errors and ensures data lands in the correct CRM fields.
Some destinations require additional fields that the visitor does not fill out, such as a campaign ID, source tag, or API key. Configure these as static fields that are included in every auto-submit POST. They are added to the request data alongside the visitor's form responses.
Submit a test lead through your form and verify the data arrives at your destination. Check that field names are correct, values are populated, and the destination system processed the lead successfully. If the delivery fails, check the webhook URL for typos and verify that the destination system is accepting POST requests.
Auto-Submit With Multiple Destinations
You can configure multiple auto-submit destinations on a single form. Each destination receives the lead data independently. This is useful when you need leads in both your CRM and your email marketing platform, or when you distribute leads to multiple buyers through offer paths.
When combined with offer path routing, auto-submit becomes a lead distribution engine. The system evaluates each buyer's criteria against the lead data and only fires auto-submit to matching buyers. Non-matching buyers do not receive the lead. This happens in real time, typically within one to two seconds of form submission.
Handling Auto-Submit Failures
Network errors, server downtime, and incorrect URLs can all cause auto-submit deliveries to fail. The platform logs all delivery attempts so you can see which leads were delivered successfully and which failed. For failed deliveries, you can review the error details and either fix the configuration or manually export the leads.
To prevent data loss, the platform stores the lead record in your database regardless of whether auto-submit succeeds or fails. The lead is always captured. Auto-submit is a delivery mechanism, not the storage mechanism. Even if every destination is down, your leads are safe in the broadcastData table.
Security Considerations
Auto-submit sends lead data over the internet to external URLs. Always use HTTPS destination URLs to encrypt the data in transit. If your destination supports API key authentication, include the key as a static field or header so unauthorized systems cannot impersonate your lead submissions.
Be selective about which fields you send. If you collect sensitive information like social security numbers or health data, make sure the destination system is authorized to receive it and compliant with relevant regulations. Only include the fields the destination actually needs.
Deliver leads to any CRM, API, or buyer endpoint automatically. No manual exports, no delays.
Get Started Free