Track Lead Source in Netlify Forms: Hidden Fields, Captured Data, and Reports
If a visitor submits a Netlify form, the submission alone usually tells you who contacted you — not which channel, campaign, or page brought them in. Adding source fields to the form closes that gap, so each lead arrives with its origin attached and can be reviewed in Netlify, added to a notification, or passed onward.
How the setup works
A practical setup has three parts. First, install a small tracking snippet on the site so visitor origin can be detected. Second, add hidden fields to each form that should carry source data. Third, let the tracking tool populate those fields when a visitor submits, so Netlify stores them alongside the contact details the visitor typed.
Checklist before you go live:
- Confirm the snippet is installed on every page that can lead to a form, not only on the form page itself.
- Add the hidden fields to every relevant form, using the exact field names the tracking tool expects.
- Submit a test form from a known campaign link and confirm the hidden values arrive in Netlify.
- Check that the same values appear in the notification email if you plan to include them there.
- Confirm any onward connection to a CRM or spreadsheet receives the fields, not just the visible form answers.
What data is captured
The hidden fields fall into two groups.
Channel fields describe how the visitor arrived:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
Landing page fields describe where the visitor first entered the site:
- Landing Page
- Landing Page Group
A paid example makes the distinction clear. A visitor who clicks a Google ad for a family law campaign might be recorded as Paid search, with Google in the first drilldown, the campaign name in the second, and the keyword in the third. The same visitor arriving from an unpaid Google search would instead be recorded as Organic search, with Google, the Google domain, and the search phrase where available. In both cases, the landing page fields show the exact entry page and the section it belongs to, such as a blog path.
Using the data in Netlify and beyond
Once submissions include source fields, you can use them in four places:
- In Netlify, by reviewing the submissions table in the Forms section.
- In notification emails, by including the fields in the message Netlify sends on each submission.
- In a CRM, through Netlify's built-in integrations or a tool such as Zapier.
- In a spreadsheet, through an add-on or a tool such as Zapier, for reporting.
Three reports are especially useful once the data is in a CRM or spreadsheet:
- Leads by channel, to compare monthly totals across paid search, paid social, and organic search and decide where to invest more effort.
- Leads by Google Ads campaign, to separate campaigns that produce leads from those that only produce clicks or visits.
- Leads by social network, to see which networks produce leads from organic posting and engagement, rather than only likes or follows.
A common failure to watch for is treating a blank source field as proof that a lead had no source. More often it means the snippet was missing, the hidden field was not added to that form, or the test submission did not come through a tracked visit. Re-running the test submission above distinguishes those cases quickly.