Track leads and customers from SEO in Insightly
Analytics tools tell you how much traffic arrives from organic search. They are much weaker at telling you which of those visitors became a named lead, which became a paying customer, and how much revenue the channel produced. Closing that gap means writing the search source onto the lead record itself, at the moment the form is submitted.
This guide walks through a four-step setup that does exactly that for Insightly: install a tracking script, add hidden fields to your forms, let the script populate them, and pass the values into Insightly. It then shows three reports worth running and a field map so you can check your configuration before trusting the numbers.
Why traffic data alone is not enough
A visitor count from organic search answers a volume question. It does not answer whether those visitors convert, which pages produce customers rather than downloads, or what revenue the channel returns. Those answers live in the CRM, attached to the person, not in an aggregate traffic chart.
The setup below bridges the two: the browser is classified once, on arrival, and the classification travels with the form submission into Insightly. From there, ordinary CRM reporting takes over.
Step 1: Install the script and add hidden fields
Sign up for the tracking tool and place its code snippet on your website; the vendor's installation guide covers where the snippet goes. Then edit each lead capture form so it contains six hidden fields:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
Most form tools let you drag in a hidden field type, or mark a normal field as hidden in its settings. The exact menu differs between builders, so use the vendor's form-specific instructions when the option is not obvious.
Step 2: The script classifies the visit and fills the fields
On arrival, the script inspects technical signals about the referral, in the same general way web analytics platforms do, and sorts the visitor into a channel such as Organic Search, Paid Search or Paid Social. That classification is stored in the visitor's browser rather than on your server.
When the visitor submits a form, the stored values are written into the hidden fields: the channel, the search engine used, and the search term where it is available.
Step 3: The submission carries the SEO data
The form tool captures the hidden field values alongside the name, email and anything else the visitor typed. The tracking tool is built to work with a wide range of form builders, scheduling tools and chat products, including Gravity Forms, Contact Form 7, Wix Forms, Webflow Forms, Typeform, Jotform and Zoho Forms, so the same pattern applies across most stacks.
Step 4: Move the record into Insightly
Pass the submission from your form tool into Insightly. An automation service such as Zapier or Make can do this, and a native form-to-Insightly integration works if your builder offers one. Map each hidden field to a matching field on the Insightly record so the values survive the transfer.
Once the data sits in Insightly, you can report on it with the CRM's own reporting, or connect a BI tool such as Tableau, Looker Studio or Microsoft Power BI for richer dashboards.
What each hidden field holds
The six fields answer two separate questions. Channel and the three Channel Drilldown fields describe the traffic source that brought the visitor in; Landing Page and Landing Page Group describe the first page they saw. Because the two families are stored separately, later reporting can filter on either one alone or on both together.
A worked example makes the split concrete. Suppose someone searches Google for a law firm in Sydney and lands on a blog post before requesting a quote. The origin fields would record Organic Search, Google, the Google domain (for example google.com.au or google.co.uk), and the search term where the browser exposes it. The destination fields would record the full URL of the post and its group, such as /blog.
That grouping is what lets you compare content types rather than individual URLs, and it is the field to check first if your reports look empty or mislabelled.
Three reports worth running
Leads by Channel. Count the leads that arrive in each month and split that count by channel. The month-over-month line tells you whether organic search is adding volume, and setting it next to paid channels shows where acquisition spend is earning its keep. When organic search consistently delivers more leads than paid search, it is worth reviewing how much of the paid budget should stay where it is.
Customers from Organic Search by Landing Page Group. Here the metric switches from leads to customers, grouped by content type (Home, Blog, Services and so on). The result distinguishes pages that draw traffic from pages that draw buyers, giving your content plan a customer-based signal rather than a visit-based one.
Revenue from Organic Search by Landing Page. The most granular view: new customers and revenue attributed to the exact URL that started the visit. Use it to decide which content to expand next.
Configuration checklist before you trust the numbers
Run through these checks after the first few submissions arrive:
- Submit a test form from an organic search result and confirm all six hidden fields are populated, not blank.
- Confirm the Channel value reads Organic Search, not Paid Search, for a non-ad click. A mismatch here usually means the classification rule or a leftover ad parameter is misfiring.
- Confirm Channel Drilldown 3 holds a search term only when the referrer exposes one; expect blanks from privacy-restricted searches.
- Confirm Landing Page Group collapses URLs into the buckets you expect (for example /blog), since a wrong rule makes the content report meaningless.
- Confirm the mapped Insightly fields are the same ones your reports read from.
- Confirm a lead that later becomes a customer keeps its original channel values, so customer and revenue reports can use them.
A customer story to verify before publishing
A useful way to judge whether this setup is paying off is to imagine a company that publishes a library of downloadable templates as a lead magnet. Each template gets its own landing page, and the tracking fields record which template page a visitor arrived on before submitting a demo request. Over time, the CRM can then show which templates produce leads, how many of those leads become customers, and what revenue they bring in. That kind of before-and-after comparison is the real test of an SEO content programme: not how many visits a template page attracts, but whether the people who arrive there turn into pipeline and closed business. If you want to feature a real customer example on this page, it should be supplied with a verified story and verified metrics, along with permission to publish the company name and any quotation.
Getting started
The workflow is the same whether you run a small site or a large one: classify the visit, store the classification, write it into hidden fields, and pass it into Insightly. The value shows up once you can answer, per lead, which search engine and which page produced it. Before committing to a tool, check the commercial terms that matter to you: how long any trial runs, what the free tier includes, and how long setup is likely to take for your form stack. Those details vary by provider and plan, so confirm them directly with the vendor rather than relying on a general guide.
| Field | Family | What it records | Example value |
|---|---|---|---|
| Channel | Channel | Broad source category | Organic Search |
| Channel Drilldown 1 | Channel | Search engine or platform name | |
| Channel Drilldown 2 | Channel | Referring domain | www.google.com (or google.com.au / google.co.uk) |
| Channel Drilldown 3 | Channel | Search term, when the referrer exposes it | law firm company in Sydney |
| Landing Page | Landing Page | Full URL of the first page visited | abbottlaw.com/blog/best-lawyers-sydney |
| Landing Page Group | Landing Page | URL grouped by section | /blog |
Example values are illustrative and follow the pattern described in the original article; actual values depend on your tracking configuration and on what the referring browser exposes.
| Report | Question it answers | Grouping |
|---|---|---|
| Leads by Channel | Is organic search growing, and how does it compare with paid channels? | Channel, by month |
| Customers from Organic Search by Landing Page Group | Which content types produce customers rather than just visitors? | Landing Page Group |
| Revenue from Organic Search by Landing Page | Which exact pages produce the most revenue? | Landing Page URL |
Report names and groupings follow the original article's examples; the exact report builder and available dimensions depend on your Insightly plan and connected tools.
Frequently asked questions
Do I need Google Analytics to do this?
No. The tracking script classifies the visit in the browser and writes the result into your form's hidden fields, so the source data reaches Insightly independently of any analytics platform. Analytics remains useful for traffic context, but it is not the mechanism that attaches the source to a lead.
Why is a search term sometimes blank?
Search engines do not always pass the query through to the destination site. When the term is unavailable, the drilldown field is left empty while the channel, engine and landing page values are still recorded.
What is the difference between Landing Page and Landing Page Group?
Landing Page is the full URL of the first page the visitor saw. Landing Page Group is that URL reduced to a section, such as /blog, so you can compare content types instead of individual pages.
Can I use my form tool's native Insightly integration?
Yes, if your form builder has one. Otherwise an automation service such as Zapier or Make can pass the submission and its hidden field values into Insightly. Either way, map the fields so the values land in the fields your reports read.
Why does my organic visit show as Paid Search?
Check for leftover advertising parameters on the URL, and check the classification rules in your tracking setup. A click that carries paid parameters will be categorised as paid even if it arrived from a search engine results page.