Capture UTM Parameters in Kali Forms: A Practical Setup Guide
If you can see how many visitors each campaign sends but not how many leads it produces, your reporting has a gap. This guide shows how to make a Kali Forms submission carry the visitor's source, channel, and first landing page into your CRM so you can report on leads and customers by campaign.
What you need before you start
You need three things in place: UTM-tagged ad URLs, a Kali Forms form with hidden fields, and a tool that reads the visitor's source and writes it into those fields. The tagging step covers paid placements on social networks and search engines; the hidden-field step is where the form stores the values; the attribution step is what fills them in at submission time.
A quick way to decide whether your current setup is enough: if your form only reads UTM values from the page URL at the moment of submission, a visitor who lands on your homepage and later opens a quote page will lose the campaign data. That is the failure mode this setup is designed to avoid.
Step 1: Tag your ads with UTM parameters
Add UTM parameters to every paid campaign URL before you launch it. This applies to social ads on LinkedIn, Instagram, Twitter, and Facebook, and to search ads on Bing and Google. Consistent tagging is what makes the later channel grouping possible; if some campaigns are tagged and others are not, the untagged ones will not carry campaign detail into the form.
Step 2: Add the hidden fields to your Kali Forms form
Hidden fields sit on the form but are not shown to visitors. Kali Forms lets you drag a Hidden field onto the form, so you can add each one at the bottom of the form without editing templates.
Add these six fields, using the exact names below so the attribution tool can match them:
The six hidden fields and what each one holds
Use this map when you build the form and when you map fields into your CRM. The left column is the field name to create in Kali Forms; the right column describes the value that will be written into it.
Step 3: Let the attribution tool fill the fields
Once the hidden fields exist, the attribution snippet watches how visitors arrive and writes the matching values into the fields when someone submits the form. It classifies each visitor into a channel such as Paid Search, Paid Social, or Organic Search, and keeps that classification in a cookie in the visitor's browser so it survives navigation across your site.
A worked example makes this concrete. Imagine a marketing team at a fictional software company, Olmo Software. A visitor searches for the brand on Google, clicks a paid ad, browses several pages, and then submits a demo request. The hidden fields would receive values like these:
Step 4: Confirm the values arrive with the submission
When the form is submitted, Kali Forms stores the hidden-field values alongside the details the lead typed in, such as name, email, and company. From there you can pass the record to a CRM such as Salesforce, Pipedrive, or ActiveCampaign and report on which campaigns and channels produced leads and customers.
Before you rely on the reports, run one test submission from a tagged URL and check that all six fields are populated. If the channel fields are empty, the usual causes are a missing hidden field, a field name that does not match, or a form that was submitted on a page reached without the attribution snippet loaded.
URL-only capture vs. cookie-persisted capture: a decision check
Two capture models behave very differently once a visitor moves between pages. Use this comparison to decide which one your form can rely on.
- URL-only capture reads the query string on the page where the form is submitted. It is accurate only when the form page is also the entry page. Any click to an internal page before submission drops the campaign values, and the lead is recorded as if it had no campaign behind it.
- Cookie-persisted capture records the source on arrival and reads it back at submission. The form page can be several clicks away from the entry page and the campaign values still arrive intact.
A practical test: open a tagged ad URL, click through to a second internal page, and submit the form there. If the channel fields are empty, you are on URL-only capture and your paid-campaign lead counts are lower than reality. If they are populated, the source survived the navigation. Run this test once per form template, because a form embedded on a page that never receives the snippet will fail even when the rest of the site is configured correctly.
Normalizing inconsistent UTM source values
Campaign naming drifts. When several people or agencies have touched the same ad account over time, the source parameter for one platform can end up written several different ways. Reporting on the raw string then splits one channel into multiple lines, and the totals look smaller and messier than they are.
A normalization layer fixes this by mapping known variants to a single channel before the value reaches your report. The rule set below shows the idea; the exact variant list depends on your own account history.
- Treat casing as irrelevant, so a capitalized and a lowercase spelling of the same source resolve to one value.
- Map common historical aliases for the same platform to one canonical channel.
- Group the canonical channel under a single reporting label, such as Paid Search, rather than reporting each raw string separately.
When you evaluate a capture tool, ask how it handles variant spellings and casing. That single answer decides whether your channel report is readable or needs manual cleanup every month.
Beyond paid campaigns: organic sources and landing pages
Paid ads are only part of the picture. Leads also arrive from organic search, organic social, direct visits, and referrals, and a complete attribution setup records those too. That gives you a basis for comparing, for example, SEO-driven leads against Google Ads leads and shifting budget accordingly.
The same data can answer content questions. If the tool records the visitor's first landing page and a landing page group, you can see how many leads and customers originated from your blog or a specific article, not just from campaign URLs.
A short pre-launch checklist
Before you send traffic to the form, confirm each of these:
- Every paid campaign URL carries UTM parameters.
- All six hidden fields exist in the Kali Forms form with matching names.
- The attribution snippet loads on every page, not only the landing page.
- A test submission from a tagged URL fills all six fields.
- Your CRM field mapping includes the channel and landing page fields.
- Your channel report groups variant source spellings under one channel.
| Field name | What it records |
|---|---|
| Channel | The grouped channel, such as Paid Search or Organic Search |
| Channel Drilldown 1 | The first level of detail, such as the platform (Google) |
| Channel Drilldown 2 | The second level, such as the campaign name |
| Channel Drilldown 3 | The third level, such as the keyword or ad variant |
| Landing Page | The first page the visitor landed on |
| Landing Page Group | The category of that page, such as Landing Pages or Blog |
Field names must match exactly for the attribution tool to populate them.
| Field | Example value |
|---|---|
| Channel | Paid Search |
| Channel Drilldown 1 | |
| Channel Drilldown 2 | Brand Campaign |
| Channel Drilldown 3 | Olmo Software |
| Landing Page | www.olmosoftware.com/landing-pages/brand |
| Landing Page Group | Landing Pages |
Olmo Software is a fictional example used to show how values map to fields.
Frequently asked questions
Do I need to add UTM parameters to organic links too?
No. The attribution tool classifies organic arrivals such as Organic Search, Organic Social, Direct, and Referral without UTM tags. UTM parameters are needed for paid campaigns so the campaign detail can be recorded.
What happens if a visitor submits the form on a different page from the one they landed on?
With a cookie-based attribution tool, the source is stored when the visitor arrives and read back at submission, so the campaign data is still captured. A URL-only method would lose it in that case.
Why do my Google Ads leads show up under several different sources?
Raw UTM source values often vary in spelling and casing, such as "google ads," "google," and "adwords." A grouping layer that normalizes those variants rolls them up under one channel, such as Paid Search.