Track SEO Leads in WPForms With Hidden Attribution Fields
Organic search can bring visitors, but a standard form submission usually records only what the visitor typed. Adding attribution context to each entry closes that gap: you can see which channel, search engine, keyword where available, and landing page preceded a lead, then compare SEO against other channels and decide which content to produce more of.
Why form submissions need attribution context
Analytics tools commonly show organic sessions, yet connecting those sessions to enquiries, quote requests and demo bookings is harder. Hidden fields solve the handoff. They stay invisible to visitors, receive values automatically in the browser, and travel with the submission so each lead carries its origin.
Four-step setup
Install the attribution snippet on the site using the platform's settings area or a tag manager, following the platform-specific guide for WordPress, Wix, Webflow or Squarespace. Then add hidden fields to each lead form and configure their default values. In WPForms this is done by dragging Hidden fields into the form. On a visit, the tool examines signals such as referring domain and UTM parameters, assigns a channel such as Organic Search, Paid Search or Paid Social, and stores it in the browser. When the visitor submits a form, those stored values populate the hidden fields and are saved with the name, email and other answers.
What each field tells you
Channel: the broad source, for example Organic Search. Channel Drilldown 1: the search engine, for example Google. Channel Drilldown 2: the specific domain, such as www.google.com or a regional Google domain. Channel Drilldown 3: the keyword where available. Landing Page: the exact page the visitor arrived on. Landing Page Group: the section of the site, such as /blog or /templates. A worked example: a visitor arriving from Google on a blog article would be recorded with Organic Search, Google, the Google domain, the keyword if available, the full article URL, and /blog as the group. That combination shows both the search context and the content that earned the lead.
Ways to use the data after capture
View entries in the WPForms Entries area of the WordPress dashboard. Add the fields to notification emails so each alert shows its source. Pass them to a CRM such as Salesforce, Pipedrive or HubSpot to follow leads through to customers and revenue. Or export to Google Sheets and chart the results, optionally connecting a tool such as Google Data Studio for deeper analysis.
Three reports worth running
Leads by Channel: monthly leads split by Organic Search, Paid Search, Paid Social and other channels. Use it to judge whether SEO is producing leads and whether budget should shift between paid and organic. Leads from Organic Search by Landing Page Group: monthly organic leads grouped by site section such as Home, Blog or Services, revealing which content types perform best. Leads from Organic Search by Landing Page: leads per individual page or post, showing exactly which pieces of content generate enquiries and guiding future topics.
Customer example
A useful way to evaluate this workflow is to sketch a hypothetical content-led SEO programme and ask what the captured fields would reveal. Suppose a team publishes a library of downloadable templates, each with its own landing page, and routes demo requests through a WPForms form containing the six hidden fields. After a few months, the Landing Page Group field would separate template pages from blog posts, the Landing Page field would rank individual templates by lead volume, and the Channel field would show how much of that demand arrived through organic search rather than paid or social. The team could then compare cost per lead across channels and decide whether to expand the template library or invest elsewhere. Before relying on any such conclusion, confirm that the snippet loads on every page, that each form carries all six hidden fields with the correct default values, and that a test submission from an organic search visit records channel, engine, landing page and group as expected. Treat any reported lift as a hypothesis to verify against your own baseline rather than an established result.
Pre-launch checklist
Before launch, confirm the snippet is installed on every page, each form contains all six hidden fields with correct default values, and a test submission from an organic search visit records channel, engine, landing page and group correctly. Then run the three reports after enough submissions accumulate to compare channels and content fairly.
| Field | What it records | Decision it supports |
|---|---|---|
| Channel | Broad source such as Organic Search | Compare SEO with paid and social |
| Channel Drilldown 1 | Search engine such as Google | See which engines drive leads |
| Channel Drilldown 2 | Specific search domain | Separate regional or domain variants |
| Channel Drilldown 3 | Keyword where available | Link leads to search demand |
| Landing Page | Exact arrival page | Identify high-performing content |
| Landing Page Group | Site section such as /blog | Plan content by section |
Keyword values are recorded only where available.
Frequently asked questions
How does a form know a lead came from organic search?
Add the attribution snippet to your site, place hidden fields in the form, and let the tool write channel and landing-page values into those fields before submission. The submitted entry then carries that context alongside the visitor's own answers.
Which hidden fields are needed?
Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Together they separate the broad channel from the search engine, domain, keyword where available, exact page, and page section.
Where can the captured data be used after submission?
Check the form's Entries view in WordPress, add the fields to email notifications, send them to a CRM, or export submissions to a spreadsheet for charts and deeper analysis.