Track where Fillout form leads came from
A form submission tells you who contacted you, but not which visit, campaign, or page led them there. This guide explains how to attach arrival and landing-page context to each Fillout submission so you can compare channels, campaigns, and content on the same record.
Why form submissions need arrival context
Analytics tools can describe website visits, yet a non-commerce business still needs to connect a later enquiry to the visit that preceded it. The practical fix is to store arrival context in the browser, then copy that context into the form at submission time. That creates one record containing both the visitor's answers and the marketing context behind the visit.
Three-step setup
First, place the attribution snippet on the website, either directly or through a tag manager. Second, add hidden fields to the Fillout form for Channel and Channel Drilldown 1 through Channel Drilldown 4. Third, let the tool populate those fields from its browser-side record when the visitor submits. Finally, test the full journey from a tagged link to the stored submission before relying on the data.
How to read channel and drilldown values
Channel gives the broad category, while each drilldown adds a layer of specificity. A paid-search visit might record Paid Search, then Google, then the campaign name, then the keyword. An organic visit might instead record Organic Search, Google, the referring domain, and the search term when available. Keeping the layers consistent makes later grouping and filtering much easier.
Add landing-page context
Alongside the channel fields, capture the first landing page and its page group. The full page shows which article or product page attracted the visitor, while the group rolls those pages into a section such as the blog. Use the group for budget and content decisions, then drill into individual pages when a section performs unusually well or poorly.
Turn captured data into decisions
Once submissions carry these fields, review them in the form tool, add them to notification emails, or send them to a CRM or spreadsheet. A useful starting checklist is: compare monthly leads by channel, compare Google Ads campaigns by lead volume, and compare social networks by lead volume. Those three views reveal whether to shift effort toward a channel, keep funding a campaign, or change where social content is published.
| Field | What it records | Example use |
|---|---|---|
| Channel | Broad arrival category | Paid Search versus Organic Search |
| Channel Drilldown 1 | Platform or source | |
| Channel Drilldown 2 | Campaign or referring domain | Brand campaign or google domain |
| Channel Drilldown 3 | Keyword or search term | Compare demand across terms |
| Channel Drilldown 4 | Additional campaign detail | Split otherwise similar campaigns |
| Landing page | First page viewed | Identify the attracting article |
| Landing page group | Section containing that page | Compare blog with other site sections |
Examples are illustrative and depend on the UTM values used on each visit.
Frequently asked questions
How can I verify lead source data is flowing into a form?
Add the attribution snippet to your site, create hidden fields on the form for channel and drilldown values, then submit a test form after arriving through a known campaign link. Check the submission record to confirm the values arrived alongside the details the visitor typed.
What is the difference between channel and drilldown fields?
Use the channel field for the broad source, such as Paid Search or Organic Search, and the drilldown fields for progressively finer detail such as the platform, campaign, and keyword or content term.
Can captured lead source data be used outside the form tool?
Yes. Captured values can be viewed with submissions, included in notification emails, or passed onward through native or third-party integrations to a CRM or spreadsheet for reporting.