Skip to content

How to capture UTM parameters in Nimble CRM

If you cannot see which campaigns create leads, opportunities and revenue in Nimble CRM, campaign decisions become guesswork. The fix is to tag every inbound link, store the arrival details in the visitor's browser, and pass cleaned channel and landing-page data into the CRM when a form is submitted.

Why arrival data matters in the CRM

Leads and sales are the usual yardsticks for marketing return, but incomplete or inconsistent arrival data makes that comparison unreliable. Recording the origin of each contact and opportunity in the CRM lets you report by campaign, content and channel, then shift effort toward sources that convert.

Four-step setup checklist

Work through these four steps in order:

  • Tag every inbound link to the site, including paid advertising, influencer activity, social posts and profile links, guest articles, trade publications and email. Consistent tagging is what allows the later capture step to work.
  • Add hidden fields to each form. Visitors do not see them, so a form asking only for name and email can still carry extra data behind the scenes. Six fields are needed: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Common form builders support hidden fields.
  • Let the capture tool fill those fields automatically. It reads UTM values, referrer information and device details, groups the visit into a channel such as Paid Search, Organic Search or Paid Social, and stores the result in a browser cookie.
  • Submit the form as normal. The visitor's details arrive in Nimble CRM together with the stored channel and landing-page values, ready for reporting by channel and campaign.

Worked example: from ad click to CRM record

Consider a visitor who finds a paid search ad for a file-sharing service, clicks through to a features page, and later requests a demo. The stored values might read: Channel = Paid Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Brand Campaign; Channel Drilldown 3 = Dropbox; Landing Page = www.dropbox.com/features/share; Landing Page Group = Features. That combination shows both the advertising source and the exact page that first brought the visitor in, which raw UTM values alone would not reveal as clearly.

Failure distinctions to check before reporting

A basic capture approach often fails in four situations, and each one is worth checking before you trust a report:

  • Traffic without UTM tags: visits from organic search, organic social, direct and referral links carry no UTM values, so a UTM-only setup misses them. A fuller approach still records a channel for those visits, giving a complete picture of lead origins.
  • Movement between pages: if someone lands from an ad, then moves to a separate contact page to submit a form, the UTM values are no longer in the URL. Storing them in a browser cookie preserves them until submission, regardless of which page the form sits on.
  • Messy tagging: the same source may be written as Twitter.com, twitter or tw. A CRM treats those as three sources, fragmenting reports. Normalising values so variants map to one channel, such as Paid Social, keeps reporting consistent.
  • Missing landing-page context: knowing only the channel hides which article or page earned the lead. Capturing the full landing URL plus its group, for example a blog article URL and its /blog section, shows how individual content performs.

Using the data in Nimble CRM reports

Once the six fields are populated, build Nimble CRM reports around Channel and the drilldown fields to compare campaigns, and around Landing Page and Landing Page Group to compare content. Cleaned, categorised data makes it easier to keep funding what works and stop spending on what does not.