Web Referral Leads
Web Referral Leads in Salesforce are leads that arrive through your Web-to-Lead form but originated on a third-party website that linked back to your form.
Definition
Web Referral Leads in Salesforce are leads that arrive through your Web-to-Lead form but originated on a third-party website that linked back to your form. The Lead Source field is set to Web, and additional fields capture the referring URL, the campaign code, or the partner identifier so attribution can distinguish a lead that came in through a partner blog from one that came in through a direct visit to your own site.
Salesforce does not ship a dedicated Web Referral Lead record type. The category is a reporting convention built on top of the standard Lead object, the Web-to-Lead form, and the referrer headers and tracking parameters captured during form submission. Marketing teams use it to credit partner sites, content syndication, affiliate programs, and SEO-driven traffic for the leads they produce.
How Web Referral Leads get captured, attributed, and reported
How the referrer makes it from the browser to the Lead record
When a visitor clicks a link from an external site to your Web-to-Lead landing page, the browser sends a Referer header along with the request. The standard Web-to-Lead form captures that header in a hidden input named retURL or in a custom Lead field your form template populates. The form post then writes the value to the Lead record alongside the standard Name, Email, and Company fields. Most orgs also capture UTM parameters from the URL (utm_source, utm_medium, utm_campaign) as separate Lead fields. The referrer header is the raw browser-supplied source; UTM parameters are the campaign-specific labels marketing controls. Both together give you the full picture of where the lead came from.
Lead Source, Lead Source Detail, and the picklist hierarchy
Most orgs configure Lead Source as a picklist with values like Web, Email Campaign, Partner Referral, Paid Search, and Organic Search. Lead Source Detail (or a similar custom field) holds the granular source: the specific partner site, the specific campaign code, or the specific ad creative. Web Referral Leads usually land with Lead Source equal to Web and Lead Source Detail populated with the referring domain or the campaign identifier. Reports filter on the combined value, so consistency matters. If half the Web Referral Leads have Lead Source equal to Web and the other half have it equal to Web Referral, the attribution dashboard misses half the credit.
Web-to-Lead vs API intake vs Pardot form handler
Web-to-Lead is the simplest path: a hidden HTML form posts to a Salesforce endpoint that creates a Lead record. It is rate-limited (500 submissions per day by default) and does not authenticate the submitter, which makes it spam-prone. Larger orgs replace Web-to-Lead with a server-side Apex REST endpoint or with the Marketing Cloud Account Engagement (Pardot) form handler, both of which authenticate, validate, and capture more metadata than the standard form. For Web Referral attribution to work consistently, whichever intake path you use has to capture the referrer and campaign parameters at the same point in the funnel. Mixing methods without a shared capture rule guarantees gaps in attribution.
Campaign attribution and the multi-touch problem
A lead rarely converts on first touch. A visitor reads a partner blog, clicks through to your site, leaves without filling the form, returns three days later through a Google search, and then fills the form. Standard Web-to-Lead captures only the last referrer. If you need multi-touch attribution, you have to capture earlier touches in a browser cookie and pass them along with the final form submission. Marketing Cloud Account Engagement does this natively through the Pardot tracking cookie. Custom implementations on Web-to-Lead rely on a small JavaScript snippet that reads or writes the cookie and pushes prior touches into hidden form fields. Decide upfront whether your reporting needs first touch, last touch, or full path attribution; the data model has to match.
Partner referral programs and the revenue-share angle
Web Referral Leads are the data backbone of partner referral programs. Each partner gets a unique URL with a partner identifier in the query string. When a lead arrives through that URL, the partner identifier writes to a Partner field on the Lead record. Downstream automation links the Lead, and any converted Opportunity, back to a Partner Account so finance can calculate referral revenue or share commission. Without consistent capture, partners argue about credit, and the program loses trust. Build a quarterly partner attribution report that each partner can self-serve, and you avoid most of the disputes. Capture the partner identifier on every page of the funnel, not just the form, since referrals often browse before converting.
Spam, validation, and the cost of dirty referral data
Web-to-Lead with no validation is a spam magnet. Bots will submit forms with junk data, sometimes thousands of times a day, and every junk submission becomes a Lead record that pollutes your reporting. The fix is twofold: add a reCAPTCHA or hCaptcha to the form to block bot traffic, and add server-side validation rules that reject submissions with obviously fake data (numeric-only names, free-email addresses for B2B forms, geographically impossible combinations). Even with validation, expect 5 to 10 percent of Web Referral Leads to need manual cleanup. Schedule a weekly review with a queue owner so spam does not silently inflate your top-of-funnel numbers and damage marketing leadership credibility.
Capturing and attributing Web Referral Leads cleanly
Capturing Web Referral Leads cleanly is a configuration job in three layers: the Web-to-Lead form itself, the Lead object fields that store the referral metadata, and the reports that summarize the data. None of the work is hard, but the layers have to line up. If the form captures a field that does not exist on the Lead object, the submission silently fails. If the field exists but reports filter on a different one, the dashboard reads zero. Test the chain end to end after every change to the form template, the field set, or the assignment rules.
- Add the referral capture fields to the Lead object
From Setup, go to Object Manager, Lead, and add fields for the data your form will capture. The standard set is Lead Source (picklist), Lead Source Detail (text), Referring URL (URL or long text), UTM Source, UTM Medium, and UTM Campaign (all text). Keep the field API names short and consistent across objects so they can be mapped to the same fields on Account, Contact, and Opportunity after lead conversion. Add a field validation rule that flags blank Lead Source when Source Detail is populated, since that combination is almost always an integration bug rather than a real lead.
- Configure the Web-to-Lead form template
In Setup, generate a Web-to-Lead HTML form that includes every field you added in step 1. Set Return URL to a thank-you page that does not leak the org instance. Add a reCAPTCHA or hCaptcha block in the form template to filter bots. Add a JavaScript snippet that reads document.referrer and writes it into the Referring URL hidden field on page load. Add a snippet that parses the page URL for utm_ parameters and populates the matching UTM fields. Save the form template in source control so changes are reviewable.
- Set Assignment Rules to route referral leads to the right queue
Open Setup, Lead Assignment Rules, and add a rule that routes leads with Lead Source equal to Web Referral or Partner Referral to the partner sales queue (or wherever your partner-aware sellers live). Without this, referral leads land in the generic web-leads queue and get treated the same as cold inbound, which loses the partner context. Test the assignment rule by submitting test forms with each Lead Source value and confirming the routing lands as expected. Document the rule in the partner playbook so account managers know where to find the leads.
- Build the referral attribution report and dashboard
Create a Lead report grouped by Lead Source and Lead Source Detail with summary columns for lead count, qualified lead count, converted opportunity count, and converted opportunity amount. Add it to a Marketing Attribution dashboard. Schedule the report to run weekly and email to the partner program owner. For multi-touch attribution, build a separate Campaign Influence report that joins Lead, Campaign Member, and Opportunity records, since Lead Source by itself only captures the last touch and undercounts partner contribution to multi-step deals.
- Web-to-Lead is rate-limited to 500 submissions per day at the org level. High-volume forms (or bot floods) hit the limit and silently drop subsequent leads. Monitor the daily count.
- document.referrer is blank when the user navigates from an HTTPS site to your HTTP form, or when a strict referrer policy is set. Capture UTM parameters as a backup so attribution does not break.
- Lead Source picklist values must match across forms, Pardot, and Apex. Inconsistent spellings split the same population across multiple report rows and undercount real performance.
- Spam bots submit Web-to-Lead forms automatically. Without CAPTCHA, expect hundreds of junk leads per week. Each junk lead pollutes attribution dashboards and trains your scoring model on noise.
- Lead Source does not propagate to Account or Contact on conversion unless you map it explicitly. Set the field mapping in Setup so partner attribution survives the lead-to-opportunity handoff.
Trust & references
Straight from the source - Salesforce's reference material on Web Referral 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 Referral Leads?
Q2. What's captured for tracking?
Q3. Why track referral sources?
Discussion
Loading discussion…