Skip to content

Track Lead Source in FormAssembly: Setup, Fields and Reports

A submitted form tells you who contacted you, but not necessarily how they found you. By adding a small set of hidden fields and an attribution snippet to your website, you can record the marketing channel, campaign detail and landing page alongside the usual name and email details. That makes it possible to compare lead volume across search, paid media, social and content without asking visitors to self-report their source.

Three-step setup

Install the attribution snippet on the website first. The snippet observes where each visitor arrived from, groups that origin into a channel comparable to the categories used in Google Analytics, and stores the result in a browser cookie so it persists while the visitor browses. When the visitor later submits a FormAssembly form, the tool writes the stored origin details into the form's hidden fields.

Add these hidden fields to each form you want to measure:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Channel Drilldown 4

Checklist before going live:

  • Confirm the snippet is present on every page that can lead to the form, not only the form page itself.
  • Confirm all five hidden fields exist on the form and use the exact names above.
  • Submit a test form from a tagged campaign link and check that the channel and drilldown values appear in the Responses section.
  • Submit a second test from an untagged organic visit and confirm the values change appropriately.
  • Confirm notification emails and any CRM mapping include the hidden fields if you want them downstream.

Once submitted, the source values are stored with the lead's other answers. You can review them in the Responses section, include them in new-lead notification emails, or send them to a CRM such as Salesforce, Microsoft Dynamics or Pipedrive for reporting.

What the fields capture

Channel is the broad origin category. Each drilldown then narrows that origin down, so a single submission can move from a general category to a specific campaign or keyword.

Worked example — paid search: A visitor clicks a Google ad for tax return preparation, browses the site, and submits the form. The captured values could read Channel: Paid Search; Channel Drilldown 1: Google; Channel Drilldown 2: the tax returns campaign name; Channel Drilldown 3: the keyword that was bid on. The exact drilldown values depend on the UTM parameters placed behind the ad.

Worked example — organic search: A visitor arrives from an organic Google search for a tax agent query. The captured values could read Channel: Organic Search; Channel Drilldown 1: Google; Channel Drilldown 2: the Google domain the visitor came from; Channel Drilldown 3: the search keyword, where available.

Landing page data is captured separately. The tool records the first page the visitor landed on and a landing page group derived from its path. For example, a landing page of /blog/best-tax-accountants might sit in the /blog group. That lets you compare lead volume by content type and then drill into individual posts or pages.

Three reports to build from the data

Leads by channel: A time-series view of lead volume split by channel shows which origins are growing or shrinking. If most leads arrive through Organic Search while most budget goes to Paid Search, that mismatch is a prompt to reconsider the allocation.

Leads by Google Ads campaign: Splitting leads by campaign shows which campaigns produce the most enquiries, so budget can be shifted toward the strongest performers and away from campaigns that generate few leads.

Leads by social network: Splitting organic social leads by network shows which platforms actually generate enquiries each month. That helps you keep investing time in the networks that work and deprioritise those that do not.

A useful decision rule across all three reports: compare lead share with spend and effort share. Where a channel produces a high share of leads on a low share of budget, test increasing investment; where it produces few leads despite high spend, investigate targeting, landing pages and offer before continuing to scale it.

Getting started

Before relying on the captured values, complete the setup and validation sequence: install the attribution snippet across the site, add the five hidden fields to each measured form, and run both the tagged-campaign and untagged-organic test submissions described above. Treat the channel, campaign and landing page data as reportable only once those tests show the expected values in the Responses section and, where relevant, in notification emails and CRM records. For current plan options, trial terms and pricing, check the provider's own signup and pricing pages rather than assuming any particular offer.

Frequently asked questions

Which fields should I add to a FormAssembly form to capture lead source?

Add hidden fields named Channel and Channel Drilldown 1 to 4 to the form, install the attribution snippet on the website, and let the tool populate those fields from its browser cookie when the form is submitted.

What is the difference between Channel and the drilldown fields?

Channel gives the broad category, such as Paid Search or Organic Search. The drilldown fields add progressively more specific detail, such as the search engine, campaign name, and keyword or referring domain.

Can the captured lead source data be used outside FormAssembly?

Yes. The captured values can be viewed in the Responses section, included in notification emails, or passed onward to a CRM for reporting.