Skip to content

Track SEO Leads and Customers in Freshsales

Organic traffic totals in an analytics tool do not answer the question most marketing teams actually care about: which search visitors became leads, which became customers, and how much revenue they produced. This guide shows how to connect those dots in Freshsales by passing organic-search attribution data through your website forms and into the CRM, then building reports that separate SEO performance from every other channel.

Why organic search is hard to attribute in a CRM

Web analytics can tell you how many sessions arrived from organic search. It cannot, on its own, tell your sales team which contact record originated from a Google query, which landing page introduced them, or whether that person eventually became a paying customer. The gap exists because the search referral information lives in the browser session, while the lead record lives in Freshsales.

Closing that gap requires three things working in sequence: a script that classifies each visit, form fields that carry the classification into your form tool, and a sync that writes those values onto the Freshsales contact or lead. When any one of those links is missing, the CRM record arrives with no source context and reporting collapses back to guesswork.

The four-step setup

The workflow below follows the sequence used by the tracking tool and Freshsales integration. Each step has a distinct failure mode, so it is worth confirming one stage before moving to the next.

  1. Install the tracking snippet and add hidden fields. The snippet is placed on every page of the site. The form then needs six hidden fields so the captured values have somewhere to land: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Most form builders let you add a hidden field by drag-and-drop or by toggling a standard field to hidden in its settings.
  1. Let the script classify the visit. On page load, the snippet inspects referral and query information and sorts the visitor into a channel such as Organic Search, Paid Search, or Paid Social. The classification is stored in the visitor's browser so it survives navigation between pages.
  1. Capture the values at form submission. When the visitor completes a contact or quote-request form, the stored values are written into the hidden fields alongside the name, email, and other entered details. The form tool now holds both the lead's identity and the source context.
  1. Send the record to Freshsales. Use the form tool's native Freshsales integration if one exists, or a connector such as Zapier or Make. Once the values are on the CRM record, they become available to Freshsales reporting or to an external BI tool.

What each captured field tells you

The six hidden fields split into two families. The Channel group describes how the visitor arrived; the Landing Page group describes what content received them.

  • Channel is the top-level bucket, for example Organic Search, Paid Search, or Paid Social.
  • Channel Drilldown 1 narrows the channel, for example the search engine name such as Google.
  • Channel Drilldown 2 holds the referring domain, such as google.com, google.com.au, or google.co.uk.
  • Channel Drilldown 3 holds the search keyword when it is available.
  • Landing Page records the full URL of the first page the visitor viewed, for example a blog post URL.
  • Landing Page Group condenses that URL to a section, for example /blog.

The landing-page pair is what lets you compare content types rather than individual URLs. If one section consistently produces customers and another produces only traffic, the group-level view makes that visible without manually tagging every page.

Worked example: a catering business

Suppose a catering company's ideal client searches for a caterer in Sydney and clicks through to a blog article. The captured record would carry the following values:

  • Channel: the channel bucket assigned by the script.
  • Channel Drilldown 1: Google.
  • Channel Drilldown 2: the Google domain for the visitor's region, such as google.com.au.
  • Channel Drilldown 3: the search phrase, when the engine exposes it.
  • Landing Page: the full article URL.
  • Landing Page Group: /blog.

One detail in the original walkthrough needs care. The narrative describes a visitor finding the business through a Google search, yet the sample values label the channel as Paid Search. Those two statements cannot both be true for the same visit. Treat the channel label in that example as illustrative only, and confirm on your own records whether a given visit is classified as organic or paid before drawing conclusions from a report.

Three reports worth building

Once the fields are populated on Freshsales records, three report shapes cover most SEO reporting needs.

Leads by Channel. Group new leads by month and by Channel. This shows whether organic search is growing, flat, or shrinking relative to paid search and paid social, and whether a budget shift is worth considering.

Customers from Organic Search by Landing Page Group. Filter to the organic channel, then count customers by Landing Page Group. This separates content that attracts browsers from content that attracts buyers.

Revenue from Organic Search by Landing Page. Sum deal revenue and customer counts per landing page. This is the closest view to a return-on-content measure, because it ties individual articles or pages to closed revenue rather than to traffic.

Freshsales' built-in reporting can produce these views. For deeper analysis, the same record data can be exported to Tableau, Looker Studio, or Microsoft Power BI.

Pre-flight checklist before you trust the numbers

Run through these checks in order. Each one isolates a different failure point.

  1. Snippet coverage. Confirm the script loads on every page that hosts a lead form, not only the homepage.
  2. Field names. The six hidden field names must match exactly, including capitalization and spacing, or the values will not map.
  3. Form-tool capture. Submit a test form and confirm the hidden values appear in the form tool's submission record before any CRM sync is involved.
  4. CRM mapping. Confirm each hidden field is mapped to a Freshsales field, and that the field type accepts the value (text fields for channel names, URL fields for landing pages).
  5. Report sanity check. Compare a week of Freshsales organic leads against your analytics organic sessions. They will not match exactly, but a total absence of organic leads alongside healthy organic traffic points to a broken link in the chain.

Two failure modes look similar but need different fixes. If the form submission itself has empty hidden fields, the problem is upstream: the snippet or the field names. If the form submission has correct values but the Freshsales record is blank, the problem is downstream: the integration mapping or the sync trigger.

What a template-led SEO strategy can look like

A published case study from the original tool describes an HR software company that placed downloadable document templates on its marketing site. Each template received its own landing page, and those pages drew substantial search traffic. The team could see visits but could not tell whether template visitors were becoming software leads.

After the attribution fields were added, the team could report on leads, customers, and revenue by landing page group. According to the published account, the template strategy produced a 2.4x lift in new leads at effectively zero cost per lead, and a later expansion of the template library was reported to produce a 4x increase in monthly new leads.

Those figures are the original publisher's reported outcomes for one company. They are not a forecast for your site, and they are not independently verified here. The transferable lesson is the measurement pattern: give each content type a landing-page group, then compare customer and revenue outcomes across groups rather than comparing raw traffic.

Getting started

The setup is small: one script, six hidden fields, and a mapping into Freshsales. The payoff is a CRM where organic search is a measurable acquisition channel with leads, customers, and revenue attached, rather than a traffic line in an analytics dashboard.

Before committing to a paid plan, confirm the current trial terms, setup time, and pricing directly with the provider, since those commercial details are set by the vendor and can change.

Frequently asked questions

Do I need a separate tool to track SEO leads in Freshsales?

Freshsales stores and reports on records, but it does not classify a website visit as organic search on its own. You need something on the website that reads the referral information and writes it into form fields. The tracking snippet described here is one option; any script that produces the same six field values would serve the same purpose.

Which hidden fields must exist on my form?

Six: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. The names must match exactly so the values map correctly into Freshsales.

Can I see the exact keyword a visitor searched for?

Sometimes. Channel Drilldown 3 holds the search term when the search engine exposes it. Many searches now arrive without keyword data, so treat keyword-level reporting as partial rather than complete.

How does the data get from my form into Freshsales?

Either through the form tool's own Freshsales integration, if it has one, or through a connector such as Zapier or Make. The connector maps each hidden field to a corresponding Freshsales field.

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. Grouping lets you compare content types without listing every URL individually.

Why do my Freshsales organic lead counts differ from my analytics organic session counts?

The two systems count different things. Analytics counts sessions; Freshsales counts form submissions that became records. Visitors who never submit a form, or whose submission fails validation, appear in one and not the other. Use the CRM figure for lead and revenue reporting and the analytics figure for traffic trends.