Skip to content

Capture Google Analytics Data in Webflow Forms in Four Steps

A Webflow form submission normally tells you who contacted you, but not which visit brought them there. Adding attribution data to that same submission connects the lead to the channel, campaign detail, and first page that produced the visit, so later reporting can be based on leads and customers rather than sessions alone.

Why attach arrival data to the form submission?

Google Analytics can show how visits arrived, including categories such as Paid Search, Paid Social, and Organic Search. That view stops at the visit. To judge which activity creates enquiries, the arrival information needs to travel with the form submission itself.

The workflow below uses a small piece of website code that identifies the visitor's arrival channel, stores it while the visitor browses, and writes it into invisible form fields when a form is completed. Webflow then saves those values alongside the details the visitor typed, such as name, email, or phone.

Step 1: Add the hidden fields

Hidden fields are present in the form structure but are not shown to visitors. They provide a place for attribution code to record information without asking the visitor to enter it.

Add these six fields to each form that should carry attribution data:

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

Channel gives the broad arrival category. The three drilldown fields hold progressively more specific detail where available, such as the source, campaign, or ad group. Landing Page records the first page the visitor opened, and Landing Page Group records its section, such as /blog or /features.

Checklist before moving on: every relevant form has all six fields, field names match exactly, and a test submission can be made without the fields becoming visible.

Step 2: Let the code populate the fields at submission

Once the website code is installed, it determines the arrival channel when a visitor lands and keeps that information available during the session. When the visitor submits a form, the code populates the hidden fields before Webflow receives the submission.

A worked example makes the distinction clear. Suppose a visitor arrives from a branded Google Ads campaign for a website builder and then completes a contact form. The captured values could be:

  • Channel: Paid Search
  • Channel Drilldown 1: Google
  • Channel Drilldown 2: Brand Campaign
  • Channel Drilldown 3: Webflow
  • Landing Page: the features/forms page the visitor first opened
  • Landing Page Group: /features

That combination answers two different questions at once: which channel and campaign produced the lead, and which content the visitor first encountered.

Step 3: Webflow captures the values with the lead

On submission, Webflow saves the attribution values together with the visitor's own answers. This is the key difference from viewing analytics separately: the lead record itself now carries its origin, so it can be reviewed later without trying to reconstruct the visit from a different system.

After capture, the same values can be used in several places:

  • The Forms section of Webflow Settings, for reviewing individual submissions
  • New-lead notification emails, so the recipient sees the origin immediately
  • A CRM or spreadsheet, where the values can be grouped and reported over time

Choose the destination based on the decision you need to make. Webflow is enough for checking individual enquiries; a CRM or spreadsheet is better for comparing channels, campaigns, and landing pages across many leads.

What the captured data means

Two kinds of information are captured. Channel data describes how the visitor arrived and may include campaign, ad group, or keyword detail for some channels. Landing-page data describes what content first attracted the visitor, including the exact page and its group.

Keeping those two ideas separate prevents a common reporting error: a channel tells you where to invest, while a landing page tells you which content to improve or expand. A lead can, for example, come through Paid Search and land on a blog article; treating those as the same field would hide both insights.

Three reports to run after capture

Leads by Channel gives a broad comparison of Paid Search, Paid Social, Organic Search, and other categories. Use it to check whether spending matches where enquiries actually originate.

Opportunities by Google Ads campaign goes one level deeper. Instead of judging campaigns by clicks or sessions, compare the sales opportunities each campaign creates, then decide which campaigns merit more investment and which should be paused.

Customers by Facebook Ads network separates results across the networks where Facebook ads may appear, such as Facebook, Instagram, Messenger, and WhatsApp. That view shows which network produces customers, not merely which network produces traffic.

Together, these reports move budget decisions from visit volume to lead, opportunity, and customer outcomes.

Final check

Before relying on the data, submit a test form from a known campaign link, confirm all six hidden fields are populated in Webflow, and check that the values also appear correctly in any email, CRM, or spreadsheet destination. Repeat the test for each form that uses the fields, because a field added to one form does not automatically appear on another. Also verify that the attribution code is loaded on every page where a tracked form can be reached, not only on the page that hosts the form.