Skip to content

Capture UTM Parameters in Typeform

Website analytics can show which campaigns send visitors, but not reliably which of those visitors become leads, customers or revenue. Capturing attribution at form submission closes that gap: each Typeform response carries the channel, campaign detail and landing page that preceded it, so results can be compared in a CRM or spreadsheet instead of relying on visits alone.

Why capture attribution at submission

Website analytics can show which campaigns send visitors, but not reliably which of those visitors become leads, customers or revenue. Capturing attribution at form submission closes that gap: each Typeform response carries the channel, campaign detail and landing page that preceded it, so results can be compared in a CRM or spreadsheet instead of relying on visits alone.

The workflow has four parts: install a small website snippet, add hidden fields to the form, let the snippet populate them from stored browser data, and send the completed submission onward.

Checklist before you start:

  • Access to add a snippet to your website, directly through site settings or via Google Tag Manager
  • Ability to edit the Typeform and add hidden fields
  • A destination for results, such as the Typeform Results tab, email notifications, a CRM, or a spreadsheet via an integration or Zapier
  • Consistent UTM tagging on paid links if you want campaign, ad and keyword drill-downs

Four-step setup

Step 1 — Add the website snippet. Sign up to obtain the snippet and install it on your website. Depending on your site builder, add it through the Settings section, or add it through Google Tag Manager.

Step 2 — Add hidden fields to the form. Typeform supports hidden fields natively. Add these six:

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

Step 3 — Let the snippet populate them. On arrival, the snippet examines UTM parameters, HTTP referrer data and device information, assigns a marketing channel similar to how Google Analytics categorises traffic, and stores the result in the visitor's browser. When the visitor submits the form, that stored data is written into the hidden fields.

Step 4 — Capture and route the submission. On submit, Typeform records the attribution values alongside the answers the lead entered, such as name, email and phone number. The combined record can then be viewed in the Results tab, included in email notifications, or sent to a CRM. Native Typeform integrations mentioned include Salesforce, HubSpot and Pipedrive; Zapier can push data to spreadsheets and other sales and marketing tools.

Example: what a completed submission looks like

Worked example — a paid search visit:

  • Channel = Paid Search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Share Files Campaign
  • Channel Drilldown 3 = Blue Ad
  • Landing Page = www.dropbox.com/features/share
  • Landing Page Group = Features

Read this as a chain: the channel says paid search, the drill-downs identify the platform, campaign and ad, and the landing fields show the exact page and its section. That chain is what makes later reporting possible without guessing.

Failure distinction to check: raw UTM capture that only reads parameters on the landing page loses the data if the visitor moves to a separate form page. Storing the attribution in the browser on arrival avoids that loss, because the original values remain available on whichever page the form is completed.

Why this is broader than raw UTM capture

Four differences matter when choosing a method:

  1. All traffic, not only paid. Attribution is recorded for every form submitter, including Organic Search, Organic Social, Referral and Direct Traffic. You therefore see the full mix of lead sources, not just tagged campaigns.
  1. Persistence across browsing. Because values are stored in the browser at arrival, they survive navigation to a different page before submission.
  1. Click IDs included. GCLID, MSCLKID and FBCLID can be captured with the submission. Sending them to a CRM and returning them to the ad platform when a lead becomes a paying customer lets optimisation target real customers rather than thank-you page visits.
  1. Landing page context. The exact landing page and its category are captured too. That supports section-level analysis, for example comparing how a blog as a whole performs and which individual posts generate the most leads, customers and revenue.

Reports you can build from captured data

Once attribution travels with each lead into a CRM or spreadsheet, four practical reports become possible:

  • Leads by Channel: count leads per channel to see where demand originates. If most leads come from Organic Search while most budget goes to paid ads, shifting some budget toward SEO may be worth testing.
  • Leads by Facebook Ads Network: compare Facebook, Instagram, Messenger and other networks to focus targeting and spend on the networks producing leads at lower cost.
  • Customers by Google Ads Campaign: count customers per campaign per month to separate campaigns that merely attract visitors from those that produce paying customers, then focus budget and A/B testing on the latter.
  • Revenue by Keyword: if keywords are included in UTM parameters via tracking templates, revenue can be grouped by keyword. That informs bidding, SEO priorities and the language used in messaging.

Decision rule: move from counting visits to counting leads, customers and revenue per channel, campaign and keyword before reallocating budget.

Wrap up

Capturing attribution at submission gives a complete picture of lead origin, including organic and referral sources that paid-only tagging misses. Combined with click IDs and landing page data, it supports offline conversion measurement and revenue reporting by campaign and keyword.

To get started, confirm the current trial and signup terms with the owner: {{OWNER_TRIAL_TERMS}}.

Frequently asked questions

What fields do I need in Typeform to receive attribution data?

Add six hidden fields to the form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. A website snippet records the visitor's origin when they arrive and stores it in the browser, then fills those fields when the form is submitted.

Does this only work for paid campaigns?

Yes. The approach described covers every submission, including Organic Search, Organic Social, Referral and Direct Traffic, rather than only visits carrying paid-campaign parameters.

What if a visitor lands on one page and submits a form on another?

Storing the origin in the browser on arrival means it is still available if the visitor browses other pages before completing a form on a different page.

Can click IDs be passed through for offline conversions?

Click identifiers such as GCLID, MSCLKID and FBCLID can travel with the submission to a CRM. They can later be returned to an advertising platform when a lead becomes a customer, supporting offline conversion measurement.