Skip to content

How to Get UTM Parameters into Keap Contacts

If you cannot tell which campaigns, ads, or keywords produced a lead, your marketing budget is working blind. Passing UTM parameters into Keap alongside each new contact gives you the data to report on channels, campaigns, and revenue. This guide walks through the four setup steps, the exact hidden fields involved, and the reports worth building once the data is flowing.

Why capture UTM parameters in Keap at all

A lead record that says only a name and email tells you nothing about acquisition. When UTM parameters and channel data travel with the contact into Keap, you can build reports showing which channels and campaigns produce leads, customers, and revenue. Without that link, budget decisions rest on guesswork rather than evidence.

Four steps to capture UTM parameters in Keap

The setup follows a fixed sequence: install the tracking code, add hidden fields to your forms, let the tool populate those fields, and confirm the values reach Keap. Each step below covers what to do and what to check before moving on.

Step 1: Add the tracking code to your site

You receive a small snippet of code to place on your website. The exact location depends on your site builder — WordPress, Webflow, Squarespace, and others each expose a settings area where scripts can be added. Detailed per-builder instructions are available in the help documentation if the placement is unclear.

Step 2: Add hidden fields to your lead forms

Add hidden fields to every lead capture form — contact, quote request, consultation, and similar. The six fields you need are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Most form builders such as Contact Form 7, Gravity Forms, Typeform, and Jotform make adding hidden fields straightforward; per-tool instructions are available in the help center.

Step 3: Let the tool fill the hidden fields automatically

Once the fields exist, the tracking code writes UTM and channel values into them as visitors submit forms. Visitors see nothing different. Take a home-services example: a homeowner searches for a plumber, clicks a paid search ad, reads a service page, then books an estimate on a separate contact page. The hidden fields would carry Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Emergency Plumbing Campaign, and Channel Drilldown 3 = Burst Pipe Repair Ad. The first page and its section are recorded too — Landing Page = www.yoursite.com/services/emergency-plumbing and Landing Page Group = Services. Note that the form was submitted on a different page than the ad landing page, yet the original values still travel with the contact.

Step 4: Confirm the values reach Keap

When a form is submitted, the hidden-field values are captured alongside the lead's contact details and can be sent into Keap. With native Keap forms this happens automatically. With third-party form builders such as Gravity Forms or Jotform, the data is passed over using an integration tool like Zapier. Once contacts carry the data, you can report on leads and customers per channel or campaign and estimate ROI.

What the tracking tool actually does

The tool is a small script that runs on your site. On each visit it reads technical signals — UTM parameters, HTTP referrer, device information — and assigns the visitor to a channel such as Paid Search, Organic Search, or Paid Social. That classification is stored in the visitor's browser as a cookie. When the visitor later submits a form, the stored values are written into your hidden fields and travel into Keap with the contact's name, email, phone, and other details.

Why this beats capturing raw UTM parameters alone

Raw UTM capture has four practical gaps that a channel-aware tool closes. The comparison below sets out each one.

Raw UTM capture versus channel-aware capture

The table below is a narrative comparison, not a product specification. Use it to decide which gaps matter for your reporting.

Three reports worth building once the data is in Keap

Three views cover most of the questions a marketer actually asks. Start with a monthly lead count split by channel: the useful signal is the gap between where leads originate and where spend is concentrated, and that gap is where reallocation pays off. Next, break Meta Ads leads down by delivery network — Facebook, Instagram, Messenger, and others — because a single campaign can perform very differently across placements, and the network split tells you where to move budget. Finally, count customers per Google Ads campaign each month rather than counting clicks or form fills; this separates campaigns that close revenue from campaigns that only generate activity, and it is the view that should drive bidding and budget decisions.

Setup checklist

Before you consider the setup complete, confirm each item:

  • The tracking code is present on every page that hosts a lead form.
  • All six hidden fields exist on every lead capture form, with names matching exactly.
  • A test submission from a UTM-tagged URL shows the expected Channel and Drilldown values.
  • A test submission after navigating from the landing page to a second page still carries the original attribution.
  • The Keap contact record shows the hidden-field values after submission.
  • Native Keap forms are confirmed automatic; third-party forms have an integration path tested end to end.

The failure mode to watch for

When a Keap report shows a large block of contacts with no source, the instinct is to audit ad URLs. That is usually the wrong first move. A tag can be perfectly formed and still produce an empty field if the visitor's journey crosses pages before the form is submitted — the parameters existed in the address bar, but nothing preserved them once the visitor moved on. The diagnostic order that saves time: first confirm the tracking code is loading on the form page itself, then confirm the visitor's classification was stored at first arrival, and only then inspect the campaign URLs. Persistence at arrival is the mechanism that keeps a multi-page visit attributable; if it is missing, no amount of URL hygiene will fix the report.

Hidden field map
FieldWhat it holdsExample value
ChannelTop-level traffic categoryPaid Search
Channel Drilldown 1First breakdown levelGoogle
Channel Drilldown 2Second breakdown levelEmergency Plumbing Campaign
Channel Drilldown 3Third breakdown levelBurst Pipe Repair Ad
Landing PageFull URL of first page visitedwww.yoursite.com/services/emergency-plumbing
Landing Page GroupSection of the site the landing page belongs toServices

Example values come from the home-services scenario described in the setup steps; actual values depend on your UTM parameters and site structure.

Raw UTM capture versus channel-aware capture
CapabilityRaw UTM captureChannel-aware capture
Paid traffic with UTM parametersCapturedCaptured
Organic Search, Organic Social, Direct, ReferralNot capturedCaptured
Form submitted on a different page than landing pageData lostOriginal attribution retained
Click IDs (GCLID, MSCLKID, FBCLID)Not capturedCaptured for offline conversion use
Landing page and landing page groupNot capturedBoth captured

Comparison reflects the capabilities described in the source article; verify current feature availability before relying on any single row.

Frequently asked questions

Do I need Zapier if I use Keap's own forms?

No. When you use native Keap forms, the hidden-field values are sent into Keap automatically. A third-party form builder such as Gravity Forms or Jotform requires an integration tool like Zapier to pass the data across.

Can I attribute leads that arrive without UTM parameters?

Yes, with a channel-aware tool. Visitors arriving through Organic Search, Organic Social, Direct traffic, or Referral are classified using referrer and other technical signals, so those leads carry attribution data even though no UTM parameters were present.

What are click IDs used for after they reach Keap?

Click IDs such as GCLID, MSCLKID, and FBCLID can be sent back to the ad platform as offline conversions at key sales milestones, for example when a contact becomes a paying customer. That lets the platform optimise against real customers rather than form submissions.