Skip to content

How to Get UTM Parameters into Freshsales CRM

If your CRM cannot tell you which channel produced a lead, every budget decision becomes a guess. This guide shows a practical way to carry UTM parameters and landing-page context into Freshsales CRM, then turn that data into channel, campaign and page-level reporting.

Why UTM capture belongs in the CRM

Marketing teams usually know how many visits a campaign produced. The harder question is which campaigns produce qualified leads, pipeline and closed revenue. Answering that requires source data on the lead record itself, not only in a web analytics dashboard.

When every lead and opportunity carries a consistent source, you can compare channels on outcomes rather than clicks. That comparison helps you stop funding tactics that never convert and direct more budget toward the channels, content and campaigns that do.

The four-step setup

The workflow has four stages: tag campaign links, add hidden fields to forms, let the attribution layer fill those fields, and confirm the values arrive in Freshsales. Each stage has a distinct failure mode, so check them in order rather than treating the whole setup as one switch.

Step 2: Add hidden fields to your forms

Hidden fields carry attribution values without asking the visitor to fill anything extra. In Freshsales' built-in form builder, a field can be made hidden with the 'Hidden in Form' option. Third-party form builders such as Gravity Forms, Typeform and Jotform also support hidden fields.

The six fields to add are: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Visitors do not see these fields; the attribution layer populates them behind the scenes.

Step 3: Let the attribution layer fill the fields

Once links are tagged and hidden fields exist, the attribution layer completes those fields automatically on each form submission. The values are then sent into Freshsales along with the visitor's submitted details.

Take a fictional company called Northwind Analytics. A user searches Google for "compare usage analytics tools," clicks a paid ad, lands on a pricing page and requests a demo. The hidden fields might then read: Channel = Paid Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Competitor Comparison; Channel Drilldown 3 = Northwind Analytics; Landing Page = www.northwindanalytics.example/pricing/compare; Landing Page Group = Pricing.

That example shows the value of separating channel from campaign and page. A report can group by the broad channel, drill into the specific campaign, or compare landing-page groups without re-tagging every link.

Step 4: Confirm the data reaches Freshsales

On submission, the UTM values and the visitor's form details (email, name, mobile number and so on) are sent to Freshsales. From there, use Freshsales' native reporting or an external reporting tool to answer questions such as which channels drive leads or how much pipeline came from a particular ad campaign.

Before trusting the reports, submit a test form from a tagged link and confirm each hidden field lands on the lead record with the expected value. A missing field is usually a form-configuration problem; a wrong value is usually a tagging or categorisation problem.

How a categorising attribution layer works

A categorising attribution layer is a small script placed on the website. It reads signals such as the HTTP referrer, UTM parameters and device information, sorts each visit into a channel category — for example Organic Search, Paid Social or Paid Search — and stores that classification in the visitor's browser as a cookie.

When the visitor submits a form, the stored values populate the hidden fields, so the source details travel with the contact into the CRM. This browser-side memory is what allows the original source to survive a journey across multiple pages. The description here covers the approach generically; whether you build it, buy it or evaluate a vendor depends on your own stack and requirements.

Three differences from raw UTM capture

Raw UTM capture records whatever string appears in the URL. A categorising layer adds three capabilities that change what you can report on.

All traffic, not only tagged traffic. Visitors who arrive from organic social, organic search, direct or referral sources can still be classified and sent to Freshsales. Leads without UTM tags are not invisible.

Memory across pages. Suppose a visitor clicks a paid social ad, lands on a campaign page, then navigates to a separate demo-request page. The UTM parameters may no longer be in the URL by the time the form is submitted. Storing the data in the browser preserves the original source regardless of which page hosts the form.

Cleaner categories. Tags such as UTM_Source=Twitter.com, UTM_Source=twitter and UTM_Source=tw would otherwise appear as three separate sources. A categorising layer recognises casing and formatting differences and groups them under one channel, such as Paid Social.

Landing-page context. Beyond the UTM values, the layer can record the landing-page URL and its subdirectory. If a visitor lands on a blog post, the page URL and the /blog subdirectory can be captured, letting you compare which pages and sections generate leads.

Decision checklist before you build

  • Do you need to report on leads that arrive without UTM tags, such as organic or referral traffic?
  • Will visitors ever move from a campaign landing page to a different page before submitting a form?
  • Are your UTM values consistent enough to group without manual cleanup?
  • Do you want to compare landing pages or site sections, not just campaigns?
  • Can your form builder create the six hidden fields listed above?
  • Have you tested a real submission and confirmed the values on the Freshsales lead record?

If you answered no to the first four questions, raw UTM capture may be sufficient. If you answered yes to any of them, a categorising layer will save reporting effort.

What good looks like after setup

A working setup lets you open a Freshsales report and see leads grouped by channel, drill into the campaign that produced them, and compare landing-page groups on conversion. That is the difference between knowing a campaign generated clicks and knowing it generated customers.

Frequently asked questions

Will visitors see the hidden attribution fields?

No. Hidden fields are not displayed on the form. The attribution layer fills them in the background when the form is submitted.

Why do UTM parameters sometimes disappear before a form is submitted?

UTM parameters live in the page URL. If a visitor clicks from a campaign landing page to a different page that hosts the form, the original parameters are no longer in the URL. Storing the values in the browser preserves the original source across that journey.

What does a categorising layer do that raw UTM capture does not?

It groups formatting variants such as Twitter.com, twitter and tw into a single channel, classifies untagged visits from organic, direct and referral sources, and can record landing-page and subdirectory context alongside the campaign data.

Can I use hidden fields with a third-party form builder?

Yes. Gravity Forms, Typeform and Jotform all support hidden fields. The field names must match the six fields listed in the setup steps so the attribution layer can populate them.