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.