Web Direct Leads
Web Direct Leads in Salesforce are leads that arrive through a Web-to-Lead form submitted directly on the company own website, as opposed to leads referred from a third-party site or sourced through paid advertising.
Definition
Web Direct Leads in Salesforce are leads that arrive through a Web-to-Lead form submitted directly on the company own website, as opposed to leads referred from a third-party site or sourced through paid advertising. The Lead Source field is set to Web (or a finer-grained Web Direct value), with no referring URL or partner identifier captured, since the prospect started on the company own pages and converted there.
The category is a reporting convention rather than a separate record type. Marketing teams use Web Direct as the baseline lead source against which paid, referral, and content-syndication channels are measured. A healthy demand-generation funnel almost always has Web Direct as one of the largest sources, since it captures organic search visits, direct URL traffic, and brand-driven returns to the site.
How Web Direct Leads get captured, attributed, and routed
How Web Direct Leads are captured and recorded
Web Direct Leads come through the same Web-to-Lead form path as referral leads. The visitor lands on a public-facing page on the company website, fills the form, and submits it. The HTML form posts to a Salesforce endpoint that creates a Lead record using the field values in the submission. What distinguishes Web Direct from Web Referral is the absence of a referring URL header (or the presence of a referrer matching the company own domain) and the absence of UTM parameters indicating a paid or partner-driven channel. The Lead Source field is set to Web (or a finer-grained value the org has configured), the Lead Source Detail is left blank or set to Web Direct, and any UTM fields are left empty.
Lead Source taxonomy and the role of Web Direct
Most Salesforce orgs configure a small picklist of Lead Source values: Web (or Web Direct), Web Referral, Email Campaign, Paid Search, Organic Search, Partner Referral, Trade Show, and Customer Referral. Web Direct is one of these and serves as the bucket for leads that cannot be attributed to any other channel. The bucket is large by default because attribution data leaks: UTM parameters get stripped by aggressive privacy tools, referrer headers disappear on HTTPS-to-HTTP transitions, and prospects often visit the site multiple times before converting. Treat Web Direct as the unattributed bucket rather than a precise channel; it is closer to other in survey terms than to a real demand channel.
Why Web Direct typically over-counts in attribution
Web Direct counts tend to be inflated relative to the actual channel performance. The reasons are three. First, modern browsers and privacy tools strip referrer headers in many cases, so a paid-search visit can show up as Web Direct if the UTM parameters got lost. Second, prospects often discover a brand through one channel and convert later through a direct URL visit, so the first-touch channel does not get credit. Third, internal links and bookmarks count as direct visits. Mature attribution models compensate by tracking prior touches in browser cookies, applying multi-touch attribution rules, and looking at downstream pipeline metrics by first-touch channel rather than form-submission channel. Standard Salesforce Web-to-Lead does not solve this; it requires additional tooling such as Marketing Cloud Account Engagement or Bizible.
Web Direct as a baseline against paid and referral channels
Demand generation teams use Web Direct as the baseline against which paid and referral channels are measured. If a paid search campaign generates twice the conversion rate of Web Direct, the campaign earns its budget; if it underperforms Web Direct, the campaign is questionable. The same comparison applies to referral programs (do partner-attributed leads outperform organic Web Direct leads on quality and pipeline conversion?) and to content syndication (does syndicated content drive higher-quality leads than organic Web Direct?). The comparison only works if Web Direct is measured consistently with the other channels: same Lead Source taxonomy, same field set on the form, same downstream qualification process. Inconsistent measurement makes every channel look better or worse than reality.
Common Web Direct form patterns and where they sit on the site
Web Direct Leads usually come from one of three form patterns. First, a Contact Us form that captures basic name, company, email, and message; this is the lowest-intent submission. Second, a Get a Demo or Talk to Sales form on a product landing page; this is the highest-intent submission and typically the most qualified. Third, a content gate that asks for an email in exchange for a whitepaper, webinar registration, or pricing guide; this captures mid-funnel intent and feeds nurture campaigns. Each pattern has different conversion characteristics, lead quality, and downstream qualification rates. Mature funnels track these patterns separately by setting the Lead Source Detail or a custom Form Source field; treating them all as one Web Direct bucket loses signal.
Routing, qualification, and the handoff to sales
Web Direct Leads need a routing rule that gets them to the right rep quickly. Standard practice is a Lead Assignment Rule that routes by company size (heuristically from the company name or a lookup), region (from the form country field), and sometimes product interest (from a checkbox on the form). High-intent forms (Demo Request) should route to sales within minutes; low-intent forms (Contact Us with a vague message) can route to a Marketing Development Rep for triage first. Add a service-level commitment: every demo-request Lead is contacted within one business hour, every contact-us Lead within four hours. Track the actual handoff time on each Lead with a custom timestamp field, and report on it monthly so leadership can see whether the SLA is being met.
Capturing, attributing, and routing Web Direct Leads
Configuring Web Direct Lead capture is a routine that overlaps heavily with general Web-to-Lead setup, but with attention to the distinct attribution and routing needs of direct-traffic leads. The work splits into four layers: the form template on the website, the Salesforce Lead object fields that store the metadata, the assignment rules that route the lead, and the dashboards that report on funnel performance. Get all four right and the funnel runs itself; get one wrong and the leads get lost or mis-attributed.
- Configure Lead object fields for Web Direct attribution
From Setup, Object Manager, Lead, add or confirm the fields that drive Web Direct attribution. Lead Source (picklist with Web, Web Referral, Email Campaign, Paid Search, etc.). Lead Source Detail (text field for granular source). Form Source (text or picklist that captures which form on the site was submitted: Contact Us, Demo Request, Whitepaper Download). UTM Source, Medium, Campaign (text fields populated from URL parameters when present). Country, Region (drive routing). Keep field API names short and consistent across the lead-to-opportunity flow so they survive lead conversion to the Account and Opportunity records.
- Build the Web-to-Lead form template with the right fields
In Setup, generate the Web-to-Lead HTML form template and include every field you set up in step 1. Set the Return URL to a branded thank-you page that does not expose the org instance. Add reCAPTCHA or hCaptcha to the form to block bot submissions. Add a small JavaScript snippet that sets Lead Source to Web Direct by default, overrideable if UTM parameters are present. Add another snippet that sets Form Source to the form name so downstream reports can split by form. Test the form by submitting through every variant and confirming the right Lead Source values arrive.
- Configure Lead Assignment Rules for direct-traffic leads
From Setup, Lead Assignment Rules, create or edit the active rule. Add an entry for Web Direct leads that routes by company size (from a custom field populated by lead enrichment) and region (from the country field on the form). High-intent forms (Demo Request) should route directly to a sales queue; low-intent forms (Contact Us) should route to a Marketing Development Rep queue for qualification first. Set a service-level commitment per route: demo requests answered within one business hour, contact-us within four hours. Add custom timestamp fields that capture handoff time so reports can measure SLA compliance.
- Build the Web Direct attribution dashboard
Create a Lead report grouped by Lead Source and Form Source with summary columns for lead count, qualified lead count, converted opportunity count, and converted opportunity amount. Add the report to a Demand Generation dashboard and schedule it to email weekly to the marketing leadership team. Add a separate widget showing Web Direct conversion rate as a baseline next to paid and referral channels. For multi-touch attribution, add a second dashboard built on Campaign Influence or external attribution tool data; Lead Source alone undercounts the paid and referral contribution to Web Direct converts.
- Web Direct counts are inflated by attribution leakage. Modern browsers strip referrer headers and UTM parameters often disappear in HTTPS-to-HTTP transitions. Use Web Direct as the unattributed bucket, not a precise channel.
- Form Source needs to be populated by the form template, not by a default value. Without per-form distinction, Demo Requests and Contact Us submissions look the same in reports and routing rules cannot differentiate intent.
- Spam bots submit Web-to-Lead forms automatically. Without CAPTCHA, expect hundreds of junk leads per week, each polluting Web Direct counts and training your scoring model on noise rather than signal.
- Lead Assignment Rules execute synchronously during Lead creation. Complex rules with many entries slow down form submission perceptibly. Optimize for the most common routes and put exotic edge cases at the end.
- Lead Source does not propagate to Account or Contact on conversion unless you map it explicitly. Without the mapping, partner attribution and Web Direct attribution both vanish at the lead-to-opportunity handoff.
Trust & references
Straight from the source - Salesforce's reference material on Web Direct Leads.
- Set Up Web-to-LeadSalesforce Help
- Lead Object OverviewSalesforce Help
- Configure Lead Assignment RulesSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What are Web Direct Leads?
Q2. How are they captured?
Q3. Why track them separately?
Discussion
Loading discussion…