Capture UTM Parameters on a Sitecore Website and Send Them to Your CRM
Marketing spend is easier to defend when you can see which channels and campaigns produce leads, customers, and revenue. The hard part is usually not reading a UTM string; it is making that context survive the journey from an ad click, through several Sitecore pages, into a form submission, and finally into a CRM record. This guide explains a four-step implementation, maps the hidden fields to the reporting questions they answer, and shows where raw UTM capture commonly breaks down.
Why capture UTM parameters at all?
A business grows faster when it can identify the channels and campaigns that produce customers at a positive return and then invest more there. Without lead-source data, that decision becomes guesswork. UTM parameters are the labels you attach to ad and campaign URLs so the destination site can recognize where a visitor came from. Capturing them in Sitecore and forwarding them to a CRM turns anonymous clicks into attributable records. The goal is not to collect strings for their own sake; it is to answer questions such as which Facebook ads generated leads, how many customers came from Google Ads, and how much revenue the SEO program contributed.
The four-step implementation
The workflow below assumes a tracking layer is installed on the Sitecore site. The same sequence applies if you build equivalent logic yourself: tag the campaign URLs, expose hidden fields on the form, populate those fields from stored attribution data, and pass the submitted values into the CRM.
Step 1: Tag your ads with UTM parameters
Add your chosen UTM parameters to every ad you run on social networks, search engines, industry sites, and other placements. These parameters tell the tracking layer where the visitor originated. When the visitor reaches the Sitecore site, the layer can read the parameters and keep them available for later form submissions. Use a consistent naming convention from the start; inconsistent source values are the root of most messy attribution reports.
Step 2: Add hidden fields to your Sitecore forms
Add a set of hidden fields to the forms that collect visitor information. Hidden fields are present in the form but not shown to visitors, so a tracking tool can write into them without changing the visible experience. If you use Sitecore's built-in Forms module, one approach is to add a text field and then adjust the field's Rules so that it is hidden. The field set to add is: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group.
Step 3: Populate the hidden fields automatically
Once the fields exist, the tracking layer captures incoming visitor data, including UTM parameters, and writes the appropriate values into the hidden fields. The values are normalized into channel categories rather than left as raw strings. For example, a visitor who arrived through a Google Ads campaign might produce Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand Campaign, and Channel Drilldown 3 = Dropbox. A visitor who arrived from an organic search result might produce Channel = Organic Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = www.google.co.uk, and Channel Drilldown 3 = Dropbox or the keyword searched. The landing-page fields add context such as Landing Page = www.dropbox.com/features/share and Landing Page Group = Features.
Step 4: Send the values into your CRM
When the form is submitted, the hidden-field values are captured alongside the lead's name, email, or phone number. You can then use Sitecore's native integrations or a third-party connector such as Zapier to send the record to a CRM. The original article named Salesforce, Microsoft Dynamics, and Zoho CRM as destinations; confirm which CRM connections your own setup actually supports before you build reports on them. Once the data arrives, you can report on lead volume by channel, customer counts by campaign, and revenue by marketing source.
Field map: what each hidden field is for
Use this checklist to confirm your form exposes the right fields before you connect the CRM. Channel answers the broad question of paid versus organic versus direct. Channel Drilldown 1 typically identifies the platform or network. Channel Drilldown 2 narrows to the campaign. Channel Drilldown 3 holds the most specific label, such as an ad group, keyword, or creative reference. Landing Page records the first page the visitor saw, and Landing Page Group rolls that page into a content category so you can compare sections of the site rather than only individual URLs.
Decision checklist: raw UTM capture versus a normalizing layer
Before choosing an approach, answer these questions. Does every lead need a source, including visitors who never clicked a tagged ad? Will the form always appear on the same page as the ad landing page? Can your reports tolerate values such as Google and Adwords appearing as separate sources? Do you need landing-page and content-group reporting in addition to channel reporting? If any answer exposes a gap, a layer that stores attribution in a cookie and normalizes channel names will save substantial cleanup later. Raw UTM capture is simpler to start but tends to shift the cost into report maintenance.
A useful failure distinction
Two failures look similar in a CRM but have different causes. If the UTM parameters are present on the landing page but absent from the submitted form, the likely problem is that the form lives on a different page and the values were never persisted. If the UTM parameters are absent from the landing page itself, the ad URL was probably not tagged correctly or the click came through an untagged path. Check the landing-page URL first, then check whether the values survive navigation to the form page. A cookie-based layer addresses the first failure; consistent ad tagging addresses the second.
How a cookie-based tracking layer works
A tracking layer is a script you add to a site much like an analytics tag. On each visit it reads available signals — the UTM parameters on the URL, the referring page, and device details — and uses them to work out an arrival path. That path is then bucketed into a named channel, such as Paid Search, Organic Search, or Paid Social, and the result is kept in a browser cookie rather than only in the current URL. When the visitor later reaches a form that contains the hidden fields, the script reads the cookie and fills those fields with the stored values. On submission, the attribution data travels with the lead's name, email, and phone number into the CRM and other tools. The design is intended to cover all traffic, remember the original source across page views, normalize inconsistent capitalization, and capture landing-page context. If you are evaluating a specific vendor product, confirm its current name, capabilities, and commercial terms with that provider.
Wrap-up
Capturing UTM parameters in Sitecore is mostly a plumbing problem: tag the ads, expose hidden fields, persist the attribution across pages, and forward the submitted values into the CRM. Once that path works, you can report on which channels and campaigns produce leads, customers, and revenue, and make better decisions about where to invest. If you are considering a ready-made tracking layer, check the provider's current trial terms and duration directly before relying on them.
Frequently asked questions
Do I need to add UTM parameters to every ad?
Yes, if you want paid campaigns attributed correctly. Untagged ads may still be classified through referrer or other signals, but the campaign and drilldown detail will be weaker. Tag every paid placement with a consistent convention.
Can I use Sitecore's built-in Forms module for this?
Yes. Add text fields for Channel, Channel Drilldown 1 through 3, Landing Page, and Landing Page Group, then use the field Rules to make them hidden. The tracking layer writes into those fields at runtime.
What happens if the form is on a different page from the landing page?
Raw UTM parameters in the URL are lost when the visitor navigates away. A cookie-based tracking layer preserves the original values so the form submission still carries the correct source.
Why do my reports show Google and Adwords as separate sources?
That usually means the raw UTM source values were inconsistent. A normalizing layer groups capitalization and naming variants into one channel, which reduces manual stitching in the CRM.
Can I report on landing pages and content groups?
Yes, if you capture Landing Page and Landing Page Group alongside the channel fields. That lets you compare individual pages and broader content categories such as a blog section.