Salesforce Lead Generation: Turn Website Enquiries into Usable CRM Leads

A prospect fills in your quote form on a Tuesday afternoon. The page thanks them and promises a reply. Marketing counts a conversion, and sales assumes someone will be assigned. If that enquiry never becomes a Lead in Salesforce, nobody waits for it. The prospect hears nothing, and the gap may only show up weeks later, when someone asks why the pipeline looks thin next to the campaign results.

Salesforce lead generation is usually discussed as demand: ads, content, events and outreach. This article covers the step straight after it, for sales, marketing and business leaders who pay for enquiries: making sure each one becomes a Salesforce Lead a seller can act on.

How Salesforce supports lead generation, and where its role ends

For this website-capture workflow, Salesforce's role starts when an enquiry needs to become a record: a Lead with an owner, a source, contact details and enough context for someone to follow up.

There are three common ways a website enquiry gets there:

What happens after the Lead exists is a different problem. Ownership and speed are covered in Salesforce lead routing. Prioritization is covered in Salesforce lead scoring, and channel credit in lead source tracking. None of those can help with an enquiry that never became a record.

Four stages of website lead capture: retain the enquiry, trace the delivery path, inspect the Salesforce outcome, and reconcile every genuine enquiry including existing-record matches

Conceptual diagram: the capture path this article focuses on. Your own tools and settings decide which of these checks apply. Select any image in this article to inspect it at full size.

Choosing between Web-to-Lead, a connected tool and a custom integration

The right route depends on volume, how many sources you have, and how much checking or enrichment an enquiry needs before it lands:

Native Web-to-Lead

Connected form or marketing platform

Custom integration

A custom integration makes sense when you're combining several sources, need to enrich or deduplicate before creating the record, or need retries and alerts you control. It costs more to build and needs an owner. If one website form works through Web-to-Lead and someone watches the exceptions, that's often enough.

Why a thank-you page doesn't prove a Lead exists

What the visitor sees and what Salesforce keeps are separate results. Salesforce documents several reasons a submission may not create a Lead:

That article says the failure email goes to the Default Lead Creator and cannot be customized. Treat it as a useful alert, with a named owner and a process for recovering genuine enquiries. Compare the source submissions with Salesforce outcomes rather than relying only on an inbox.

A small Web-to-Lead example: a stored Lead and a rejected enquiry

The October 26, 2026 example uses two fictional quote enquiries for a cold-storage business. Enquiry A includes a phone number; Enquiry B leaves it blank. The retained Salesforce record and failure email let us distinguish a stored enquiry from a rejected one.

Two quote request forms, one above the other: Enquiry A from Maya Okafor at Northfield Provisions with phone 555-0142, and Enquiry B from Daniel Reyes at Copperleaf Bakery Supply with the phone field blank

Two supplied form captures, stacked for comparison. Both show Lead Source set to Web; Enquiry B has no phone number.

The form's configured return URL is visible in the retained failure email. That setting does not establish what either browser displayed after submission; no return-page capture is retained.

Salesforce All Open Leads list searched for maya.okafor@example.com, showing two Leads with that email: one at Harborview Dental and the new Northfield Provisions Lead created on October 26, 2026

The All Open Leads search shows two records for Enquiry A's email, including Northfield Provisions. This is a filtered list, not an org-wide duplicate audit.

Salesforce Lead record for Maya Okafor at Northfield Provisions showing phone 555-0142, Lead Source Web, status Open - Not Contacted, address Hamilton Ontario, created 2026-10-26 at 3:04 p.m., and the quote request in the Description field

The record screenshot shows the matching phone number, Lead Source, city, province and request details. It was captured after creation, so it does not establish when each field was populated. Two parts of the same record page are joined at the grey line.

Salesforce All Open Leads list searched for d.reyes@example.net, showing 0 items

The All Open Leads search returns zero items for Enquiry B's email. That filtered search alone does not establish org-wide absence.

The stronger evidence is the Salesforce failure email dated October 26 at 3:07 p.m. It matches Enquiry B's name, email, company and quote request, shows a blank phone field, and states that Salesforce could not create the Lead. Its reason is:

Please provide a phone number so our team can confirm the quote.

The email establishes that this submission was rejected with a phone-required message. The underlying validation-rule definition is not retained. The original email screenshot is kept privately because it includes org identifiers.

The lesson goes beyond phone numbers: a rule that improves data quality for internal users can turn an incomplete web enquiry into a lost one. You may still want the rule, but then the form should require the same field, or the rejected enquiry needs somewhere to land.

Enquiry A's record page also displays a no-potential-duplicates message, while the list shows two records with the same email. That observation does not establish which duplicate rules were active. Check your org's actual matching and duplicate rules before drawing a conclusion. Salesforce duplicate management covers the tradeoffs between blocking duplicates and letting them through.

Evidence scope: one supplied Web-to-Lead example, two fictional enquiries, record/list screenshots and a matching failure email. Connected tools, reCAPTCHA, daily capacity, recovery and production traffic were not tested here. No browser-return, rule-definition or rule-deactivation receipt is retained.

What to check: fields, rules, spam and limits

An admin can review these without changing anything:

Run an end-to-end capture audit

A capture audit answers one question: can you account for every genuine enquiry in a set period, whether it created a new Lead or reached an existing record?

  1. Pick a window. A recent week or month with normal traffic works well.
  2. Export submissions from the source. Use the form tool, the marketing platform, or your website's own records. If the Leads themselves are your only record of submissions, a rejected enquiry leaves nothing to match against. Consider having the website or form tool keep its own copy.
  3. Find the Salesforce destinations. Include newly created Leads, converted Leads and existing Leads or Contacts that the capture process deliberately updated or linked to. Use source, campaign and integration records as appropriate; a returning prospect does not always need another Lead.
  4. Match enquiries to outcomes. Prefer a submission identifier recorded at both ends. Where it is unavailable, use email and time as investigation aids, allowing for repeat enquiries, time-zone differences and the agreed sync delay. Keep pending deliveries separate from unexplained gaps.
  5. Explain and assign every exception. Separate spam, deliberate existing-record matches, pending deliveries, rejected submissions and unexplained gaps. Inspect failure emails or sync errors for the actual reason. Give each unresolved genuine enquiry an owner, next action and due date; do not count categories twice.
  6. Check usefulness, not just existence. Confirm that the destination record carries the request details, source, contact fields and follow-up responsibility sellers need, so nobody has to ask the prospect for the same information again.
  7. Test before changing rules. In a sandbox, submit a valid enquiry and one that breaks a rule. Salesforce's troubleshooting article also suggests temporarily deactivating Lead validation rules and using debug logs for the submitting user (Salesforce Help: Troubleshooting a Non-Functional Web-to-Lead Form). Do that in a sandbox, not production. The generated Web-to-Lead HTML also includes optional debug lines that email you diagnostic details when you submit a test. Retain the valid result, controlled rejection, recovery and configuration-restoration receipts before signing off.

The lead capture audit checklist turns these steps into a worksheet.

When an admin can fix it, and when to review the integration

Many capture problems are admin-sized fixes. Good examples are a form missing a required field, a validation rule that should allow web enquiries, a stale Default Lead Creator, or an inactive picklist value. Once the fix is in, run a test submission and repeat the reconciliation for the following week.

A wider integration review makes sense when:

If enquiries do reach Salesforce but stall after that, see marketing to sales handoff. For how to classify sync failures as retry, fix or escalate, see Salesforce integration error handling.

Bring one missing enquiry to a capture review

If you suspect website enquiries are going missing or arriving incomplete, three things are enough to start: your enquiry form, the tools connected to it, and one example of a lead that went missing or arrived without key details. In a scoped capture and integration review, we'll trace that example through your form, delivery path and Salesforce rules. You'll come away knowing whether an admin fix is enough or the integration needs a closer look.