How to capture UTM parameters in Agile CRM
If you want Agile CRM reports to show which campaigns create leads, opportunities and customers, the attribution data has to travel with the form submission. This guide explains a four-step setup: tag campaigns consistently, add hidden form fields, let tracking code complete them, and send the results into Agile CRM.
1. Tag every campaign link
Start with the links themselves. Add UTM parameters to paid advertising, guest posts, social profiles, email campaigns and any other link that leads to your website or sales funnel. Consistent tagging is the foundation: without it, there is nothing reliable to pass into the CRM. Use the same naming approach across platforms so later reporting does not fragment one campaign into several.
2. Add six hidden fields to your forms
Next, prepare the form to receive attribution data without showing it to visitors. Create six hidden fields: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. In Agile CRM's own form builder, drag in a Hidden Input field for each one. Third-party builders such as Gravity Forms, WPForms and Typeform also support hidden fields, though the exact control name varies by builder.
3. Let the tracking code complete the fields
Once the fields exist, the tracking code on the site completes them automatically when a visitor submits a form. The code collects UTM parameters, referrer information and device data, groups the visit into a channel such as Organic Search, Paid Search or Paid Social, and stores the result in a browser cookie. That cookie matters when the conversion page is not the landing page: a visitor who clicks an ad, browses, then completes a contact form elsewhere still carries the original campaign values into the submission. The code also tidies inconsistent UTM naming — for example, variants of a social platform name that differ only in capitalisation or abbreviation — so they roll up into one channel instead of appearing as separate sources.
4. Report on leads and revenue in Agile CRM
On submission, the hidden-field values travel alongside the contact's name, email and phone number into Agile CRM. From there you can build reports by channel and drilldown — for example, how many leads came from Organic Search, or how much revenue a paid social campaign produced compared with its cost. Because landing page and landing page group are captured too, you can also compare which pages and site sections, such as a blog or podcast area, generate the most leads, and shift budget toward what performs.
Pre-launch checklist
Use this checklist before you trust the reports: every campaign link is tagged; all six hidden fields are present on every lead form; a test submission produces values in Agile CRM; a visit that starts on one page and converts on another still retains its original campaign data; and channel names are consistent across campaigns. If any check fails, fix the tagging or the form first — CRM reporting cannot recover attribution that was never captured.
| Hidden field | What it stores | Example value |
|---|---|---|
| Channel | Broad channel grouping | Paid Search |
| Channel Drilldown 1 | Platform or network | |
| Channel Drilldown 2 | Campaign grouping | Brand Campaign |
| Channel Drilldown 3 | Specific campaign or brand | Dropbox |
| Landing Page | Page the visitor arrived on | www.dropbox.com/features/share |
| Landing Page Group | Site section of the landing page | Features |
Example values are illustrative, based on the worked example in the source material.
| Situation | Raw UTM capture | Cookie-based attribution |
|---|---|---|
| Visitor arrives without UTM tags | No campaign data captured | Channel still assigned from referrer and other signals |
| Form completed on a different page from landing page | Original UTM parameters can be lost | Stored values are passed through the form |
| Inconsistent UTM naming across campaigns | One source can appear as several CRM values | Variants are normalised into a consistent channel |
Comparison summarises the distinctions described in the source material.
Frequently asked questions
What are the four steps to get UTM data into Agile CRM?
Add UTM parameters to every campaign link, place six hidden fields on the form, let the tracking code fill those fields from the visitor's stored attribution data, and submit the form so the values arrive in Agile CRM with the contact details.
Which hidden fields are needed on the form?
Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Visitors do not see these fields; they carry attribution values through the submission.
What if the form is on a different page from the landing page?
Yes. The attribution values are stored in a browser cookie, so a visitor who lands on a campaign page and later completes a form on a different page can still have the original campaign values passed through.
Why normalise UTM values instead of storing them raw?
Raw UTM values can vary in capitalisation and naming, which can split one source into several CRM values. Normalising those variants into a consistent channel grouping makes lead and revenue reporting easier to compare.