Skip to content

Capture UTM parameters in Everest Forms

Connect campaign and landing-page data to every form submission, so you can see which channels are producing leads rather than only website visits.

How the setup works

Website analytics can show which campaigns send traffic, but it does not always show which of those visitors later become leads. Attaching attribution data directly to a form submission closes that gap: the name, email and company supplied by the visitor travel with the channel and landing page that brought them to the site.

The workflow has four parts. First, make sure paid campaigns carry UTM parameters. Second, add invisible fields to the form. Third, let the attribution snippet fill those fields from the visitor's arrival data. Fourth, send the completed submission, including its hidden values, to the tools you already use.

Four-step checklist

  1. Tag paid campaigns. Add UTM parameters to advertising on social platforms and search engines, including LinkedIn, Instagram, Twitter, Facebook, Bing and Google.
  1. Add hidden fields to the Everest Form. Drag a Hidden field to the bottom of the form for each value you want to store: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Visitors do not see these fields, but their values are submitted with the form.
  1. Let the attribution snippet populate the fields. The snippet is added to your website. When a visitor arrives, it examines where they came from, groups them into a channel such as Paid Search, Paid Social or Organic Search, and stores that information in a browser cookie. On submission, it writes the stored values into the hidden fields.
  1. Use the captured values. The submission now contains both the lead's own details and the attribution fields. Those values can be sent to a CRM, included in email alerts, saved to a spreadsheet, or passed on through a workflow tool such as Zapier.

Worked example

Take a visitor who searches for a company name, clicks a branded search ad, browses the site and then requests a demo. The hidden fields could be filled as follows: Channel = Paid search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Brand campaign; Channel Drilldown 3 = Olmo Software; Landing Page = www.olmosoftware.com/landing-pages/brand; Landing Page Group = Landing Pages.

Why this approach gives cleaner reporting

Attribution covers every lead, not only paid clicks. Organic search, organic social, referral and direct visits are also classified, giving a fuller picture for budget decisions. For example, if organic search produces more leads than paid search, shifting some spend toward search optimisation may be worth testing.

Persistence matters too. If a visitor lands on the homepage from an ad and later completes a quote form on a different page, methods that read parameters only from the submission-page URL would miss the campaign. The attribution snippet stores the values in a cookie, preserving them across the visit.

Normalisation keeps reports readable. Campaigns may use inconsistent source spellings such as different variants for the same search engine. Grouping those variants under one channel prevents a single source from appearing as several separate rows that must be added together manually.

Landing-page capture adds another layer. Recording both the exact landing URL and its group lets you compare performance by section, such as a blog, or even by individual article, alongside the channel that sent the visitor there. For example, the snippet captures a landing page URL such as https://roipaths.com/blog/capture-utm-parameters-happyforms and a landing page group such as /blog.

Before you go live

Before publishing, check that every paid campaign uses consistent UTM naming, that all six hidden fields are present on the form, and that a test submission from a tagged link records the expected channel, drilldowns, landing page and landing page group. Then confirm the values appear correctly in your CRM, alert email, spreadsheet or workflow destination.

Hidden-field map
FieldWhat it recordsWhy it helps
ChannelBroad source category, such as Paid SearchCompare major channels in one view
Channel Drilldown 1First level of detail, such as the search engineBreak a channel down by platform
Channel Drilldown 2Second level of detail, such as the campaignCompare campaigns within a platform
Channel Drilldown 3Third level of detail, such as the keyword or ad groupDrill into the specific campaign element
Landing PageExact page where the visitor first arrived, e.g. https://roipaths.com/blog/capture-utm-parameters-happyformsSee which page converted the visit
Landing Page GroupSection containing the landing page, e.g. /blogCompare site sections, such as blog or product pages

Field names are the hidden-field labels used in the workflow; values are populated automatically at submission. Landing page example: https://roipaths.com/blog/capture-utm-parameters-happyforms; landing page group example: /blog.

Frequently asked questions

Does this only work for paid campaigns?

No. Attribution is also recorded for organic search, organic social, referral, direct and other non-paid visits, so reporting is not limited to campaigns that carry UTM tags.

What if the visitor lands on one page and submits on another?

Yes, because the attribution snippet stores the values in a browser cookie when the visitor first arrives. They can still be written into the form even if the visitor browses to a different page before submitting.

Why normalise UTM values instead of storing them raw?

Raw values such as different spellings for the same search engine can split one channel into several apparent sources. Normalising them into a single channel, such as Paid Search, makes totals easier to read and compare.