Track SEO Leads in Tally Forms
Organic traffic totals do not tell you which visitors became leads. This guide shows how to attach search-attribution data to every Tally Forms submission so you can count SEO leads, compare channels and see which content earns the most enquiries.
Why analytics alone is not enough
A platform such as Google Analytics can report that people arrived through organic search, but it does not by itself show how many of those visitors submitted a form or became paying customers. The gap is the hand-off between the visit and the form submission. Filling that gap means recording the visit context in the form itself, so the lead record and the acquisition source travel together.
The four-step setup
- Install the attribution script on your website. The script is normally placed in the site's settings area or loaded through a tag manager, depending on the website builder.
- Add six hidden fields to each lead-capture form in Tally Forms: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Use the field keys specified for Tally Forms so the script can find them.
- Let the script classify each visit. It examines signals similar to those used by analytics tools, sorts the visitor into a channel such as Organic Search, Paid Search or Paid Social, and stores that context in the browser.
- On submission, Tally Forms records the hidden-field values alongside the lead's name, email and other answers. The attribution data is then visible in the Submissions area, can be included in notification emails, and can be forwarded to a CRM.
Field map: what lands in each hidden field
The six hidden fields split into two families. The Channel family describes how the visitor arrived; the Landing Page family describes what content received them.
- Channel: the top-level grouping, for example Organic Search.
- Channel Drilldown 1: the named source, for example Google.
- Channel Drilldown 2: the referring host, for example www.google.com.
- Channel Drilldown 3: the search term when it is available.
- Landing Page: the full URL of the first page viewed.
- Landing Page Group: the section of the site that page belongs to, for example /blog.
A useful way to read the map is by question. 'Where did they come from?' is answered by the first four fields. 'What did they read first?' is answered by the last two. Reports that mix the two families without deciding which question they answer tend to become noisy.
Worked example: a blog visit from search
Suppose a project-management software company publishes a blog post aimed at small teams. A visitor searches Google, lands on that post and later completes a quote request. The hidden fields would carry values in this pattern:
- Channel: Organic Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: www.google.com
- Channel Drilldown 3: best project management software for small teams
- Landing Page: perfectprojects.com/blog/project-management-tools-small-teams
- Landing Page Group: /blog
The value of this record is that it survives the visit. Months later, when the lead becomes a customer, the original search context is still attached, so revenue can be traced back to the content that started the relationship.
Pre-flight checklist before you trust the data
Run this check on a staging form before relying on the numbers.
- The script loads on every page that hosts a form, not only the homepage.
- All six hidden fields exist on the form and use the exact field keys expected by the script.
- A test submission from an organic-search visit shows Organic Search in the Channel field.
- A test submission from a direct visit shows the expected direct or non-organic value rather than a blank field.
- Notification emails include the hidden fields if the team needs source context in the inbox.
- The CRM mapping, if used, carries all six fields rather than only the channel.
If Channel is blank, the usual causes are a missing hidden field, a mismatched field key or a script that did not load on the page where the form was submitted. Checking those three items in order separates a form-configuration problem from a tracking-script problem.
Three reports worth building
Leads by Channel gives a monthly count grouped by acquisition channel. Use it to compare organic search with paid search and paid social, and to check whether budget allocation matches where leads actually come from.
Leads from Organic Search by Landing Page Group groups organic leads by site section such as the homepage, blog or service pages. Use it to decide which part of the site deserves more content investment.
Leads from Organic Search by Landing Page breaks the same data down to individual URLs. Use it when you need to judge specific articles or landing pages rather than whole sections.
A practical rule: start with the channel report to confirm SEO is contributing at all, move to the group report to choose a section, then use the page report to choose individual pieces to expand or replicate.
Where the captured data can go
The attribution values are not confined to the Tally Forms submission list. They can be added to email notifications so the team sees the source immediately, passed into a CRM such as Salesforce, Pipedrive or HubSpot, or exported to a spreadsheet and connected to a reporting tool for dashboards. Each destination keeps the same six values, which is what makes cross-tool comparison possible.
A customer story to confirm only with owner input
Customer example worksheet
Record a customer example you can verify. Leave unknown fields blank until you have supporting evidence.
| Field | Your details |
|---|---|
| Customer and permission to use the example | ________ |
| Problem and starting point | ________ |
| Configuration or actions | ________ |
| Measurement period | ________ |
| Outcome and supporting evidence | ________ |
| Approval to publish | ________ |
Getting started
The setup is short: install the script, add the six hidden fields with the correct keys, submit a test form from an organic-search visit, and confirm the values appear in Tally Forms. Once that loop works, the reports above become reliable enough to guide content and budget decisions. Before committing to a plan, check the current signup page for the trial period, pricing tiers and any setup-time expectations, since those commercial terms can change and are not stated here.
Frequently asked questions
Do I need Google Analytics to track SEO leads in Tally Forms?
No. The attribution script classifies the visit independently and writes the result into the form's hidden fields. Analytics can still be useful for traffic volume, but the lead-level source data comes from the form submission itself.
Why is the Channel field empty on some submissions?
Check three things in order: whether the hidden field exists on that specific form, whether its field key matches the one the script expects, and whether the script loaded on the page where the form was submitted. A direct visit may also produce a non-organic value rather than a search value.
Can I see the search keyword for every organic visit?
Not always. The keyword is captured when it is available; many search visits do not expose it. The channel, source, referring host and landing page are the more consistently populated fields.
What is the difference between Landing Page and Landing Page Group?
Landing Page is the full URL of the first page viewed. Landing Page Group is the section that URL belongs to, such as /blog. Use the group for section-level decisions and the page for content-level decisions.
Can the attribution data reach my CRM?
Yes. The hidden-field values can be included in notification emails and forwarded to a CRM integration such as Salesforce, Pipedrive or HubSpot, or exported for reporting. The exact mapping depends on the integration you configure.