Tracking Lead Sources in Webflow Forms: A Practical Setup Guide
When a Webflow form arrives with only a name and email, the marketing channel behind it disappears. This guide shows how to attach source context to every submission so you can see whether a lead arrived through organic search, paid search, paid social or another route, and then use that context in Webflow, notification emails, a CRM or a spreadsheet.
Step 1: Install the tracking script
Before any hidden field can receive a value, the tracking script has to be running on the site. Sign up for the trial, then place the supplied code snippet on every page that hosts a lead form. The install instructions for the owner's platform should be followed exactly, because a script that loads on only some pages will leave gaps in the source data.
Once the snippet is live, move on to the form itself. The script and the form fields are two halves of the same mechanism: the script detects the visit, and the fields give it somewhere to write.
Step 2: Add the hidden fields to each form
Add these hidden fields to every Webflow form that should record a lead source:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Channel Drilldown 4
The channel field holds the broad category, while the four drilldown fields hold progressively finer detail such as the network, campaign, keyword or referring domain. Field names must match what the tracking script writes; a mismatch means the value has nowhere to land. Step-by-step instructions for adding hidden fields in Webflow are available in the owner's help documentation.
Step 3: How the source data reaches the submission
With the script installed and the fields in place, the script watches how each visitor arrives and writes the matching values into the hidden inputs. Those inputs are not rendered in the visible form, so the layout a visitor fills in is unchanged and the conversion path is not interrupted.
On submit, Webflow stores the hidden values together with whatever the lead typed into the visible fields. The result is a single submission record that pairs contact details with the channel and campaign that produced the visit.
Worked example: paid search versus organic search
Suppose a visitor clicks a paid ad and lands on the site. The hidden fields might receive:
- Channel: Paid search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Brand campaign
- Channel Drilldown 3: Example Software
Now suppose a different visitor arrives from an unpaid Google result. The same fields might receive:
- Channel: Organic search
- Channel Drilldown 1: Google
- Channel Drilldown 2: www.google.com
- Channel Drilldown 3: Example Software
Both submissions look identical in the visible form, but the stored source values let you separate paid from organic traffic later. The drilldown values depend on what the tracking script can read from the visit, so a missing UTM parameter can leave a drilldown field blank even when the channel is correct.
Landing page context
Channel data answers where a lead came from; landing page data answers what content brought them in. The tracking script records the first landing page, such as a specific blog post URL, and the landing page group, such as the /blog section. That pairing lets you compare lead volume across site sections and then drill into individual pages to see which posts or product pages produce leads.
Where the captured source data can go
Once the hidden fields are populated, you have four practical destinations:
- Webflow entries: open the form submissions table to read the source values next to each lead.
- Notification emails: include the source fields in the emails Webflow sends on each submission so the team sees the channel immediately.
- CRM: use Webflow's built-in integration or a connector such as Zapier to create or update the CRM record with the source values.
- Spreadsheet: forward submissions to a spreadsheet through an add-on or connector, then build reports from the rows.
Three reports worth building
Leads by channel gives a monthly view of how many leads came from paid search, paid social, organic search and other channels. It shows which channels are producing leads and which need attention.
Leads by Google Ads campaign breaks the paid search total down by campaign, so you can tell campaigns that generate leads from campaigns that generate clicks but no conversions.
Leads by social network compares the social platforms you post or advertise on, helping you see which network actually produces leads rather than just engagement.
Setup checklist and failure distinctions
Before you call the setup finished, confirm each item below:
- The tracking script is present on every page that hosts a lead form.
- Every lead form contains all five hidden fields with names that match the script exactly.
- A test submission from a paid link shows a channel and at least one drilldown value.
- A test submission from an organic search shows the organic channel rather than a blank.
- The CRM or spreadsheet connector maps the hidden fields to the correct destination properties.
If the channel field is blank, the usual cause is a missing or misnamed hidden field. If the channel is correct but a drilldown is blank, the usual cause is a missing UTM parameter on the incoming link. Those are different problems and need different fixes.
Frequently asked questions
Do hidden fields change what visitors see on the form?
No. The fields are hidden, so the visible form and the conversion experience stay the same while the source values are stored with the submission.
Can the source data reach a CRM without manual copying?
Yes. Webflow's built-in integration or a connector such as Zapier can send the stored source values to the CRM along with the lead's other details.
Why is a drilldown field empty when the channel is filled in?
The channel can be identified from the visit itself, but drilldown values often depend on UTM parameters. If a link lacks the relevant parameter, that drilldown can be blank while the channel remains correct.