Salesforce Lead Capture Audit Checklist
Use this worksheet to check whether every genuine website enquiry reaches a usable Salesforce destination. It works for native Web-to-Lead and for connected form or marketing tools. Review settings in production if you need to, but make test submissions and rule changes in a sandbox.
1. Scope
Enquiry form or forms reviewed .................................
Connected tools between the form and Salesforce .................................
Review window (dates and time zone) .................................
Person who receives capture failure alerts .................................
2. Settings and rules
☐ The capture route is confirmed for each form: Web-to-Lead, connected tool, or custom integration.
☐ The form sends every field Salesforce requires on Lead, including fields that validation rules make required.
☐ Each Lead validation rule has been read from a web visitor's point of view. For each rule that could reject a web enquiry, the form requires the same field or the exception has a place to land.
☐ Mapped picklist values in connected tools exist and are active in Salesforce.
☐ Duplicate rules and unique fields have been checked: a repeat enquiry is blocked, allowed with an alert, or merged later, by deliberate choice.
☐ Spam protection (reCAPTCHA or the tool's own control) is on, and old or unused capture forms are offline.
☐ Daily volume is comfortably below the Web-to-Lead limit of 500 requests per day, including campaign peaks.
☐ The Default Lead Creator, or the connected tool's error log, is monitored by a named person.
3. Reconciliation
Submissions recorded by the form or tool in the window .................................
New Leads matched to those enquiries .................................
Enquiries linked to existing Leads, converted Leads or Contacts .................................
Pending deliveries within the agreed sync delay .................................
Unexplained genuine enquiries (do not double count categories) .................................
Unmatched submissions .................................
Unmatched Leads (possible spam, imports or manual entries) .................................
☐ Matching uses a shared submission ID where available; email/time comparisons allow for repeat enquiries, time zones and the agreed sync delay.
☐ Existing-record matches and converted Leads were checked before calling an enquiry missing.
☐ Every unmatched submission is classified: spam, pending, rejected or unexplained. Each unresolved genuine enquiry has an owner, next action and due date.
☐ A sample of matched destination records carries the request details, source and contact fields sellers need.
☐ Any manual copying of enquiries into Salesforce has been noted, with the reason.
4. Test and follow-up
☐ In a sandbox, one valid test enquiry created a Lead with the expected fields.
☐ In a sandbox, one test enquiry that breaks a rule produced a visible alert or log entry.
☐ Test records include the valid result, rejection reason, recovery outcome and configuration-restoration receipt.
☐ Fixes are assigned, and the reconciliation is booked again for the following week.
Biggest open question for a capture review .................................
Example enquiry to trace (date, form, what was missing) .................................
Prepared by Logic Conduit. Bring this worksheet and one missing or incomplete enquiry to a scoped capture and integration review: https://logicconduit.com/#contact