Skip to content

Track SEO Leads in Forminator

Forminator captures form entries, but by default it does not know whether a visitor arrived from an organic Google search, a paid ad, or a referral. This guide shows how to add attribution fields to Forminator forms so each submission carries the visitor's channel and landing-page context, and then how to read that data in reports.

Why Forminator entries need attribution fields

Forminator records the name, email, and message a visitor types, but it does not record how that visitor found the site. Analytics tools can count organic visits, yet they do not connect a visit to a specific form submission or to a later customer. Adding attribution fields to the form closes that gap: the submission itself carries the channel and landing-page context, so you can count SEO leads directly from Forminator entries or from the CRM those entries feed.

Four setup steps

The workflow has four parts. First, install the attribution script on the site. Second, add the required hidden fields to each Forminator form. Third, let the script populate those fields when a visitor arrives. Fourth, confirm that the values travel with the submission into entries, notifications, or the CRM.

1. Install the attribution script

After signup, the attribution service provides a small code snippet. Add it through the site's settings area or through a tag manager such as Google Tag Manager, depending on the website builder. Platform-specific installation instructions are available for WordPress, Wix, Webflow, Squarespace, and other builders. The script must be present on every page that hosts a Forminator form; otherwise the hidden fields will stay empty.

2. Add the six hidden fields to Forminator

In the Forminator form builder, drag a Hidden field from the sidebar into the form once for each required field, then name each field exactly as the attribution service requires. The six field names are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. A step-by-step Forminator guide is available for the exact naming and placement.

Field map: what each hidden field records

Use this map to check that each field is present and named correctly before testing a submission.

3. How the hidden fields get filled

When a visitor lands on the site, the script examines referral and search data in the same way an analytics platform does. It classifies the visit into a channel such as Organic Search, Paid Social, or Referral, and stores that classification in the browser. If the visitor later submits a Forminator form, the script writes the channel, source, keyword where available, and landing-page values into the hidden fields at submission time.

4. Confirm the data travels with the lead

When the form is submitted, the hidden-field values are stored alongside the visitor's name, email, and other answers. You can review them in Forminator's Entries section, include them in lead notification emails, forward them to a CRM, or export them to a spreadsheet for reporting. If the fields are present but empty, check that the script loads before the form and that the field names match exactly.

Worked example: an organic Google search

Suppose an online training provider's blog post ranks for a course-related search and a visitor submits a form. The hidden fields should contain values like these: Channel = Organic Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = the Google domain used, such as www.google.com or a regional variant; Channel Drilldown 3 = the search term when it is available; Landing Page = the full URL of the blog post; Landing Page Group = /blog. If any of these are blank, the script or the field naming is the first place to check.

Putting the captured data to work

The captured values can be used in four places: viewed in the WordPress dashboard alongside each submission, included in lead notification emails, pushed to a CRM such as Salesforce, Pipedrive, or HubSpot through an automation tool like Zapier, or exported to Google Sheets and connected to a dashboard tool such as Looker Studio. Each destination supports a different reporting question, so choose based on whether you need a quick check, an alert, a revenue report, or a trend chart.

Three reports to run once data is captured

These reports answer different questions about SEO performance. Start with the channel report to see whether organic search is producing leads at all, then move to the landing-page group report to see which sections of the site contribute, and finally to the individual landing-page report to identify specific pages that convert.

Report 1: Leads by channel

This report counts leads per month grouped by channel, such as Organic Search, Paid Search, and Paid Social. It shows whether SEO is consistently producing leads and allows a direct comparison with paid channels. If organic search produces more leads than paid search while most budget goes to ads, the report gives a factual basis for reconsidering the allocation.

Report 2: Organic search leads by landing-page group

This report breaks monthly organic leads down by landing-page group, such as Home, Blog, or Services. It shows which sections of the site attract the most converting search traffic, so content and SEO effort can be concentrated where it already works.

Report 3: Organic search leads by landing page

This report counts new leads for each page or blog post. It identifies the individual pieces of content doing the most work, so you can expand on the topics and formats that convert and stop investing in pages that do not.

Pre-launch checklist

Before relying on the data, confirm each item: the script loads on every page with a form; all six hidden fields exist and are named exactly; a test submission from an organic search shows a channel value; a test submission from a direct visit shows the expected direct or referral classification; the Entries view displays the values; and any CRM or spreadsheet destination receives the fields. If a test fails, note whether the field is missing, empty, or populated with the wrong channel, because each failure points to a different part of the setup.

Forminator hidden fields and their reporting role
Hidden fieldWhat it recordsTypical report use
ChannelBroad acquisition category such as Organic Search or Paid SocialLeads by channel
Channel Drilldown 1Source within the channel, such as GoogleChannel breakdown
Channel Drilldown 2Domain or platform detail, such as www.google.comSource detail
Channel Drilldown 3Search term when availableKeyword-level analysis
Landing PageFull URL of the first page visitedLeads by landing page
Landing Page GroupSection of the site, such as /blogLeads by landing-page group

Field names must match the attribution service's requirements exactly; values depend on the script being installed and loaded before form submission.

Frequently asked questions

Why are the hidden fields empty in Forminator entries?

The most common causes are a missing or blocked script, a field name that does not match the required name exactly, or a form loaded before the script runs. Check the script installation first, then compare each field name character by character.

What happens when a visitor arrives directly rather than from search?

The script still classifies the visit, but the channel will reflect a direct or referral classification rather than Organic Search. The landing-page fields still record the first page visited, so direct traffic can be separated from search traffic in reports.

Can the captured values be sent to a CRM?

Yes. The hidden-field values can be forwarded to a CRM such as Salesforce, Pipedrive, or HubSpot through an automation tool like Zapier, or exported to Google Sheets for spreadsheet reporting.