Skip to content

Track SEO leads in FormAssembly

Analytics platforms can count organic visitors, but they usually stop short of telling you which of those visitors became leads. This guide shows how to connect organic search source data to FormAssembly submissions so you can see which channels and content produce leads, then route that data into reporting tools.

What this setup does

A small tracking script runs on your website and records how each visitor arrived. When that visitor submits a FormAssembly form, the recorded source details are written into hidden fields alongside the lead's name, email, and other answers. The result is a submission record that includes both the lead's identity and the marketing source that brought them in.

Setup steps

The workflow has four stages. Each stage must be completed before the next one produces useful data.

1. Install the tracking script

Add the tracking snippet to your website. Most site builders accept it in their settings area, or you can deploy it through a tag manager. Platform-specific installation instructions are available for common builders such as WordPress, Wix, Webflow, and Squarespace.

2. Add hidden fields to your FormAssembly forms

Open the form in the Form Builder, add a Hidden Field from the Add Content menu, and set its Default Value to the matching placeholder. The fields to create are: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. For example, the Channel field's default value is [channel].

3. Let the script populate the fields

On each visit, the script evaluates referral and campaign signals similar to the way analytics platforms classify traffic. It assigns the visitor to a channel such as Organic Search, Paid Search, or Paid Social, and stores that classification in the browser. When the visitor later submits a form, the stored values are written into the hidden fields automatically.

4. Confirm the data arrives with each submission

After submission, the organic search values appear alongside the lead's name, email, and other answers. You can review them in the My Responses section, include them in notification emails, or pass them to a CRM.

Field map: what each hidden field captures

Use this map to decide which fields to create and how to read them in reports.

Worked example

Suppose a project-management software company receives a visitor from an organic Google search. The captured values would look like this: Channel is Organic Search; Channel Drilldown 1 is Google; Channel Drilldown 2 is the search domain, such as www.google.com or a local variant; Channel Drilldown 3 is the search term when it is available. The landing page fields record the exact page, such as /blog/best-tools-for-remote-teams, and its group, such as /blog. Reading the group first tells you which content area is producing leads; reading the exact page tells you which article is doing the work.

Where to send the data

Choose the destination that matches the question you need to answer. A quick check of individual submissions is enough when you only need to spot-check sources. Notification emails help when the team needs source context at the moment a lead arrives. A CRM is the right place when you need to connect leads to customers and revenue. A spreadsheet is useful for lightweight dashboards and trend tracking over time.

Destination checklist

Use FormAssembly's My Responses view when you want to inspect a single submission. Add the fields to notification emails when the sales team needs source context immediately. Send the fields to a CRM such as Salesforce, Pipedrive, or HubSpot when you need to report on leads, conversions, and revenue together. Export to Google Sheets when you want to build charts or connect to a dashboard tool like Looker Studio.

Three reports worth building

Each of the three reports below answers a different question, and the order matters. Start with the channel view to confirm SEO is producing leads at all. Move to the landing page group view to see which content areas carry that load. Finish with the page-level view to find the individual articles or pages doing the most work. If the channel view shows no organic leads, the deeper reports have nothing to explain yet, so fix capture before building them.

Leads by Channel

Read this as a scoreboard, not a diagnosis. It tallies new leads per month and separates them by channel, so you can compare organic search against paid search, paid social, and the rest. The useful moment is when the scoreboard contradicts the budget: if organic search is delivering more leads than paid search while the ad spend keeps growing, the report gives you a concrete reason to revisit the split. It will not tell you why organic is winning; that is what the next two reports are for.

Leads from Organic Search by Landing Page Group

This view narrows to organic leads only and sorts them by the section of the site they came from, such as Home, Blog, or Services. Treat it as a routing decision: whichever group keeps appearing at the top is where content and SEO effort should concentrate next. A group that draws traffic but few leads is worth a separate look at its pages before you invest further.

Leads from Organic Search by Landing Page

At the finest grain, this report attributes new organic leads to individual pages, whether a single blog post or a product landing page. Use it to name the specific topics that convert, then decide what to commission next based on that evidence rather than on traffic alone. A page with strong traffic and weak lead counts is a signal to review its offer or call to action, not necessarily to retire it.

Troubleshooting: missing data versus misattributed data

If the hidden fields arrive empty, the most likely cause is that the tracking script is not loading on the page where the form appears, or that a field's default value does not match the expected placeholder. Check the script installation first, then confirm each hidden field's default value. If the fields arrive populated but the channel looks wrong, the issue is usually classification rather than capture: the visitor may have arrived through a referral, a campaign parameter, or a direct visit that the script classified differently than expected. Review the drilldown values to see what signal the script used.

Wrap-up

The value of this setup is not the fields themselves but the decision they unlock: knowing which organic content earns leads lets you fund the pages that work and question the ones that only attract visits. Once capture is in place, pick the destination that fits your reporting habit, whether that is a quick look at submissions, a notification email, a CRM report, or a spreadsheet dashboard, and let the data guide where SEO effort goes next.

Frequently asked questions

Do I need a separate tracking tool if I already use Google Analytics?

Analytics platforms can show how many visitors arrived from organic search, but they generally do not show which of those visitors submitted a FormAssembly form. The hidden-field approach connects the source data to the submission record itself.

Which FormAssembly fields do I need to create?

Create six hidden fields: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Each field's default value must match the placeholder the tracking script expects.

Can I see the source data without a CRM?

Yes. The values appear alongside each submission in the My Responses section, and they can also be included in notification emails.

What is the difference between Landing Page and Landing Page Group?

Landing Page records the exact URL the visitor arrived on. Landing Page Group records the broader section, such as /blog, so you can report at either the page level or the content-area level.