Capture UTM parameters in Ninja Forms in four steps
If you run a WordPress site and collect leads through Ninja Forms, the submissions themselves tell you who filled out the form but not how they found you. Adding UTM parameters to your campaign links and wiring those values into hidden form fields closes that gap. This guide walks through the four-step setup, explains the six hidden fields the tracking tool expects, and shows what the captured data looks like once it reaches your CRM.
Why capture UTM parameters at all
A form submission without a source label is a dead end for analysis. You know someone converted, but you cannot connect that conversion back to a campaign, a channel, or a piece of content. Once source data is attached to every lead record, a different set of questions becomes answerable: which paid campaigns produce pipeline rather than just clicks, whether organic search or paid social deserves the next budget increase, and which landing pages are pulling their weight. The practical decision this unlocks is reallocation — moving time and money toward the channels that demonstrably convert, instead of spreading spend evenly and hoping. Capturing UTM parameters at the moment of submission is the simplest way to make that source data permanent rather than something you have to reconstruct later.
Step 1: Tag every inbound link with UTM parameters
Before any form can capture source data, the links that bring visitors to your site need UTM parameters attached. That includes paid ads on Google, Bing, Facebook, and Pinterest, social media posts and profile bios, guest blog mentions, influencer campaigns, and any other channel you want to measure. If a link arrives without a UTM tag, the tracking tool has less to work with and the resulting record will be less specific. Treat UTM tagging as a habit rather than a one-off task: every new campaign link should be built with the same parameter set so that reports stay comparable over time.
The six hidden fields and what each captures
The tracking tool expects a specific set of field labels. The table below maps each label to the kind of data it holds so you can verify your setup before going live.
Step 3: Let the tracking tool populate the fields automatically
Once the hidden fields exist and the tracking script is on the page, the tool reads incoming traffic data and writes the appropriate values into each hidden field in the background. Visitors see nothing different; the form looks and behaves exactly as before. To see what this looks like in practice, consider a visitor who searches for a way to share large files, clicks a paid Dropbox ad, and requests a demo. The hidden fields on that submission would carry the channel, the search engine, the campaign name, and the ad group, plus the landing page URL and its top-level section. The next section shows those values concretely.
Worked example: what the captured values look like
Using the Dropbox demo-request scenario, the six hidden fields would be filled as follows: Channel is Paid Search; Channel Drilldown 1 is Google; Channel Drilldown 2 is Brand Campaign; Channel Drilldown 3 is Dropbox; Landing Page is the full URL of the page the visitor first landed on, such as www.dropbox.com/features/share; and Landing Page Group is the top-level section of that URL, in this case Features. The first four fields describe the campaign; the last two describe the content that received the click. Together they let you answer two different questions: which campaign brought the lead, and which page convinced them to convert.
Step 4: Send the completed form data to your CRM
When a visitor submits a form whose hidden fields have been populated, Ninja Forms stores the values alongside the visible answers and forwards the whole submission to whatever destination you have configured. Ninja Forms offers native add-ons for several major CRMs and can also route submissions through automation tools such as Zapier when a direct integration is not available. The important point is that the source data travels with the lead record, so it is available for reporting long after the session ends.
How the tracking layer works under the hood
Think of the tracking script as a small observer that runs on every page load. It reads the signals a browser sends along with a visit — the UTM values in the URL, where the visitor came from, what device they are on — and turns those signals into a single channel label. That label is then parked in a cookie in the visitor's browser so it survives as they move between pages. The cookie is the handoff point: it sits quietly until a form with the right hidden fields is submitted, at which point its stored values are copied into those fields next to the visitor's name, email, and other answers. This is why the fields must exist before the tracking can work: without them, there is nowhere for the data to land.
Why raw UTM strings cause reporting problems
Raw UTM values are only as consistent as the people who create them. One campaign might use UTM_Source=Twitter.com, another UTM_Source=twitter, and a third UTM_Source=tw. A CRM treats each distinct string as its own source, so a report meant to show one Twitter channel ends up split across three lines that each look small and unremarkable. The fix is a normalization layer that recognizes capitalization and abbreviation variants and folds them into a single channel before the data reaches your reports. Without that step, a UTM field can be technically populated and still useless for decisions, because the totals it produces understate the channel's real contribution.
Capturing visitors who arrive without UTM parameters
Plenty of visitors never click a tagged link. They find you through an untagged organic result, a social post nobody parameterized, a referral from another site, or by typing the address directly. If your setup only records UTM values, those leads land in the CRM with empty source fields — and the gap is not random. It clusters around exactly the channels you have the least tagging discipline for, which is often where the most interesting untagged demand hides. A concrete consequence: if you later ask whether organic search is worth investing in, the untagged organic leads are invisible in the answer, so the channel looks weaker than it is. A tracking layer that categorizes every arrival, tagged or not, keeps those records labeled as Organic Search, Referral, or Direct so the comparison stays honest.
Landing page data adds a second dimension
Source data answers where a lead came from. It does not answer what they were reading when they decided to convert. Capturing the full landing page URL alongside its top-level section adds that second dimension, so you can compare pages individually and compare content groups in aggregate. Suppose your /blog section produces steady form fills while /features produces almost none despite similar traffic — that is a signal about where content investment should go, and it is invisible if you only track the campaign. The two data points together give a fuller picture than either one alone.
Pre-launch checklist
Before you rely on the data, confirm each of the following: every active campaign link carries UTM parameters; all six hidden fields exist on every form that should capture source data; field labels match the expected names exactly; the tracking script is present on all pages that host a form; a test submission produces populated hidden fields; and the CRM record shows the source values after the submission is forwarded. If any step fails, the most common causes are a missing hidden field, a label mismatch, or a form that was published before the fields were added.
| Field label | What it captures |
|---|---|
| Channel | High-level traffic category, e.g. Paid Search |
| Channel Drilldown 1 | First-level detail, e.g. the search engine |
| Channel Drilldown 2 | Second-level detail, e.g. the campaign name |
| Channel Drilldown 3 | Third-level detail, e.g. the ad group |
| Landing Page | Full URL of the visitor's first page |
| Landing Page Group | Top-level section of that URL |
Field labels must match exactly for the tracking tool to populate them; the example values shown are illustrative.
Frequently asked questions
Why does the setup need six hidden fields rather than one?
Each field holds a different level of detail. Channel gives the broad category, the three drilldowns narrow it down step by step, and the two landing-page fields describe the content side of the visit. Splitting them this way lets you report at whatever level of granularity you need without parsing a single combined string.
What happens to visitors who arrive without UTM parameters?
A tracking layer that only reads UTM parameters will leave those records blank. A layer that categorizes all traffic will still assign a channel such as Organic Search, Referral, or Direct, so the CRM record is never empty.
Why do my UTM reports show the same channel multiple times?
Inconsistent capitalization and abbreviations in the UTM source value create separate entries in the CRM. Normalizing those variants into a single channel label collapses them into one line in your reports.
Can Ninja Forms send the captured data to any CRM?
Ninja Forms offers native add-ons for several major CRMs and can also forward submissions through automation tools such as Zapier when a direct integration is not available. The hidden field values travel with the submission either way.