Skip to content

Capture UTM Data in Webflow Forms: A Four-Step Setup

Webflow forms record what a visitor types, but not reliably where that visitor came from. If the tracking parameters disappear from the address bar before submission, the lead arrives without campaign context. The setup below preserves channel, drilldown, and landing-page information through hidden fields, so it can be reviewed in Webflow, sent to a CRM or spreadsheet, or included in notifications.

Why parameters alone are not enough

A raw-parameter approach only works when the parameters remain in the page address at the moment of submission. That fails in a common journey: a visitor arrives from an advertisement on the homepage, browses, then opens a separate contact page. The form page no longer carries the original parameters, so the submission loses its origin.

A cookie-based attribution approach solves the timing problem. When the visitor first arrives, the tool examines technical signals similar to those used by analytics platforms, classifies the visit into a channel, and stores that classification in the browser. When a form is later completed, the stored values are written into hidden fields and submitted alongside the name, email, and other details the visitor entered.

This also widens coverage beyond paid campaigns. Organic search, organic social, direct, and referral visits can be classified too, rather than leaving every non-UTM lead unlabelled.

The four-step setup

Complete these four steps in order:

  1. Add the attribution snippet. Sign up for the tool, copy the unique snippet provided, and add it through the site Settings under Custom Code, in the Head Code section. A tag manager can be used instead where that is the preferred deployment method.
  2. Add hidden fields to each relevant form. Hidden fields sit on the form but are not visible to visitors. They give the tool a destination for the stored attribution values.
  3. Let the tool populate the fields automatically. On arrival, it captures and stores the visit data. On submission, it fills the hidden fields before the form is sent.
  4. Check the captured submission. The attribution values travel with the submission and can be viewed in the form submissions area, included in email notifications, or forwarded through native integrations or an automation service to a CRM, spreadsheet, email platform, or other tool.

Before going live, submit a test form from a tagged link and confirm that every hidden field arrived with the expected value. Then submit from a different page on the same site to confirm the stored data still carries through.

Hidden fields to add

Add six hidden fields, using these exact names so the stored values have a matching destination:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Landing Page
  • Landing Page Group

Channel gives the broad source, such as Paid Search or Organic Search. The three drilldowns add progressively more specific detail, such as the network, campaign, and ad or keyword context. Landing Page records the full page where the visitor first arrived, while Landing Page Group records its section, such as the blog or features area. Together they let you report on both the campaign and the content that attracted the lead.

Checklist for each form:

  • All six hidden fields are present and named exactly as listed
  • The snippet is present in the head code or tag manager
  • A tagged test submission populates every field
  • A second test from a different page still populates every field
  • The destination CRM, spreadsheet, or notification shows the new fields

Worked example: from ad click to form submission

Consider a visitor who finds a file-sharing service through a paid search advertisement, lands on a features page, and then requests a product demonstration. The stored attribution data could be written into the form as follows:

  • Channel: Paid Search
  • Channel Drilldown 1: Google
  • Channel Drilldown 2: Brand Campaign
  • Channel Drilldown 3: Dropbox
  • Landing Page: www.dropbox.com/features/share
  • Landing Page Group: Features

The important distinction is that the values describe the first arrival, not merely the page where the demonstration form happened to be submitted. That makes the record useful for judging which campaign and which page produced the lead.

Click IDs and landing pages add the missing context

Beyond UTM values, the same setup can preserve advertising click identifiers, including the Google Click ID, Microsoft Click ID, and Facebook Click ID. Passing those identifiers to a CRM allows a lead that later becomes a customer to be matched back to the originating click. That supports offline conversion reporting based on real customers rather than only thank-you-page visits.

Landing-page capture adds a second reporting axis. Reporting by individual page shows which article or product page attracted leads, while reporting by page group shows whether a whole section, such as a blog, is performing. Combining channel, campaign, click ID, and landing page in one submission gives a fuller picture than any single field alone.

Four reports worth building first

Once the fields are flowing into a CRM or spreadsheet, four reports are practical:

  • Leads by Channel: compare paid, organic, social, direct, and referral lead volume to see where demand actually originates and where budget may be over- or under-weighted.
  • Leads by Facebook Ads Network: separate results across networks such as Facebook, Instagram, and Messenger to identify which placement produces leads most efficiently.
  • Customers by Google Ads Campaign: join campaign data to closed customers, not just clicks or form fills, so spending follows campaigns that produce paying clients.
  • Revenue by Keyword: include keyword values in campaign tracking templates, then compare keyword-level revenue to guide bids, search optimisation, and messaging language.

Start with leads by channel, because it validates the whole pipeline. Add customer and revenue joins only after the lead records are flowing reliably.

Summary

The core workflow is short: install the snippet, add six hidden fields, let the tool store arrival data in a cookie, and allow it to fill those fields at submission. The payoff is a lead record that explains its own origin, survives navigation between pages, and covers organic as well as paid traffic.

{{OWNER_CUSTOMER_EXAMPLE}}

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.