Capture UTM Parameters in Kentico and Send Them to Your CRM
Knowing which campaigns create leads — not just visits — helps you invest more in what works. This guide explains how to collect UTM and related attribution data on a Kentico site, store it in hidden form fields, and pass it to a CRM or other tool for reporting.
The four-step approach
The aim is straightforward: attach source information to every lead in your CRM, then report on leads, customers and revenue by channel and campaign. Four steps achieve that result.
How it works in practice
Step 1 — Tag your campaigns. Add UTM parameters to paid social placements such as Instagram, LinkedIn, Facebook and Twitter, to search advertising on Google and Bing, and to other activities including trade-publication ads, email campaigns and newsletter sponsorships. Tagging at the source is what lets the later steps identify where a visitor came from.
Step 2 — Prepare your forms. Add hidden fields to lead-capture forms such as Contact Us and Request A Quote. In Kentico, add a standard Text Input field, then on the Visibility tab choose Never so visitors do not see it. Create fields for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group.
Step 3 — Let the attribution data fill the fields. A small piece of code on the site reads visitor information, classifies the visit into a channel such as Paid Search, Paid Social or Organic Search, and stores it in a browser cookie. When a hidden-field form is submitted, that stored information is written into the fields.
Step 4 — Send the submission onward. The hidden-field values travel with the name, email and phone number. Kentico's native integrations can pass them to systems such as Salesforce, Microsoft Dynamics, Pipedrive or HubSpot, or a tool such as Zapier can send them to Google Sheets, Excel and many other destinations.
Worked example
Consider a visitor who searches for a CRM product, clicks a paid search ad and lands on a product page, then later completes a demo-request form. The hidden fields might be completed as follows: Channel = Paid Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = CRM Campaign; Channel Drilldown 3 = Best CRM ad; Landing Page = www.salesforce.com/products/crm; Landing Page Group = Products. That combination shows both the campaign that drove the visit and the content that received it.
Decision checklist and reporting questions
Use this checklist before relying on the data:
- Every paid campaign and bespoke promotion carries consistent UTM parameters.
- Each lead form has all six hidden fields, set to never display.
- A test submission from a tagged ad populates Channel and the three drilldowns correctly.
- A test submission from organic or direct traffic is still classified, rather than left blank.
- A visitor who lands on one page and submits on another still carries the original attribution.
- Landing Page and Landing Page Group match the first page viewed.
- The CRM or spreadsheet receives the fields alongside contact details.
Once those checks pass, reports can answer practical questions such as how many leads Facebook ads generated, how many customers came from Google ads, and how much new business revenue SEO produced.
Why classified attribution beats raw UTM values
Capturing raw UTM values alone has three common weaknesses. First, it misses untagged traffic, so reports understate organic search, organic social, referral and direct sources. Second, it loses data when the form page differs from the landing page, because the parameters are no longer in the URL. Third, inconsistent tagging — for example Google in one campaign and Adwords in another — splits what should be one source into two report rows.
Storing classified attribution in a cookie addresses all three: all traffic is categorised, the data survives navigation between pages, and variant spellings are normalised into a single channel such as Paid Search. Landing-page capture adds a further dimension, so you can also report which blog posts or other content generated leads and customers, and estimate the return on that content investment.
Frequently asked questions
Will UTM data still be captured if the form is on a different page from the landing page?
No. The cookie retains the attribution data, so it can be written into the form even when the submission happens on a later page than the landing page.
Does this only work for traffic with UTM parameters?
Yes. In addition to paid traffic carrying UTM parameters, the approach also classifies organic search, organic social, referral and direct visits, so reporting is not limited to tagged campaigns.
Can landing-page information be reported alongside channel data?
Yes. The first page viewed and its grouping are also passed through, which makes it possible to see which content, such as blog posts, produced leads and customers.