Skip to content

Capture Google Ads Data in Webflow Forms

Connect Webflow form submissions to the Google Ads campaign, ad group, and ad that produced each lead, so reporting can follow a lead through to customer and revenue outcomes instead of stopping at clicks and form completions.

Why lead counts alone can mislead

Clicks and form completions alone can point budget in the wrong direction. A campaign may produce more leads while another produces fewer leads but substantially more customers and revenue. Attaching source data to every submission makes that distinction visible.

Consider two campaigns that each spend $2,000. One brings 200 visitors and 20 leads, but only 2 customers and $8,000 in revenue. The other brings 100 visitors and 10 leads, but 5 customers and $25,000 in revenue. The second campaign converts 50% of leads into customers, compared with 10% for the first, costs $400 rather than $1,000 to acquire a customer, and returns three times as much revenue per ad spend. Without customer and revenue data attached to each lead, the first campaign looks stronger; with it, the second is clearly the better investment.

Four steps to capture Google Ads data in Webflow

Work through four steps in order:

  • Tag every Google Ads destination URL with UTM parameters so the campaign, ad group, and ad are encoded in the link.
  • Add hidden fields to each Webflow lead-capture form for channel, three channel drilldowns, landing page, and landing page group.
  • Let the attribution tool read the visitor's UTM values and populate those hidden fields when the form is submitted.
  • Submit the form and confirm that the attribution values arrive together with the visitor's name, company, phone, email, and other entered details.

The resulting record can be added to lead notification emails, sent to a CRM for the sales team, or used in reports that show which campaigns generate leads, customers, and revenue.

Tag ads with UTM parameters

UTM parameters are extra text appended to a destination URL. A consistent Google Ads convention is to set UTM Medium to Paid Search, UTM Source to Google, UTM Campaign to the campaign name, UTM Term to the ad group name, and UTM Content to the specific ad. Free URL builders can help assemble the final link, but consistency across campaigns matters more than the builder used.

Hidden-field map

The six hidden fields map directly onto the UTM structure. Channel carries the broad category, such as Paid Search. Channel Drilldown 1 carries the source, such as Google. Channel Drilldown 2 carries the campaign. Channel Drilldown 3 carries the ad group or ad, depending on how UTM Term and UTM Content are set. Landing Page records the first page the visitor arrived on, and Landing Page Group records its section, such as a blog or features area.

For example, a visitor arriving from a brand campaign in Paid Search might produce Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand campaign, and Channel Drilldown 3 = Free account ad, with the landing page and its group captured alongside those values.

What to check before choosing a method

Three practical differences separate a dedicated attribution tool from simply reading UTM parameters on the submission page.

First, it captures all traffic, not only Google Ads. Leads from Organic Social, Paid Social, and Organic Search receive channel data too, so reports can account for every lead and reveal when search or content work is doing the heavy lifting.

Second, it remembers the data while the visitor browses. Many UTM-capture methods need the parameters to be present on the page where the form is completed. If a visitor lands on a campaign page, clicks a quote button, and submits on a different page, those parameters are lost. Storing them in a browser cookie preserves them until submission, regardless of the visitor's route through the site.

Third, it produces cleaner data. Raw UTM values often vary in capitalisation and naming, with the same source appearing as Google.com, google, or adwords. Reporting those raw values splits one source into several rows that must be stitched together manually. Normalising them into a single channel, such as Paid Search, keeps reports accurate without manual cleanup.

Finally, landing-page capture shows which parts of the site generate leads, customers, and revenue. Recording both the exact landing page and its group lets you compare a whole section, such as a blog, and then zoom into individual posts within it.

Pre-launch checklist

Before publishing the setup, run one test submission from a tagged Google Ads link and verify each field: the channel and drilldowns match the UTM values, the landing page is the first page visited, and the record reaches the CRM or notification email with the lead's own details intact. Then repeat the test after navigating to a different page before submitting, to confirm the values survive the journey. Once both checks pass, campaign reporting can follow each lead through to customer and revenue outcomes.

Example: same spend, different customer and revenue outcomes
CampaignSpendVisitorsLeadsCustomersRevenue
Pool Pumps Campaign$2,000200202$8,000
Pool Cleaners Campaign$2,000100105$25,000

Illustrative example: identical spend, opposite conclusions once customers and revenue are included.

Frequently asked questions

How do I capture Google Ads data in a Webflow form submission?

Tag each Google Ads destination URL with UTM parameters, add the six hidden fields to the Webflow form, and let the attribution tool populate those fields from the visitor's first-touch UTM values before submission. The submitted record then carries channel and landing-page data alongside the lead's own details.

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

Yes, when the tool stores the UTM values in a browser cookie. The values can then be written into the form even if the visitor navigates to a different page before submitting.

Why normalise UTM values instead of reporting them raw?

Raw UTM values can vary in capitalisation and naming, such as Google.com, google, or adwords for the same source. Normalising them into a single channel, such as Paid Search, prevents one source from being split across several report rows.

Pool Pumps CampaignPool Cleaners Campaign
Spend$2,000$2,000
Visitors200100
Goal Completions2010
Pool Pumps CampaignPool Cleaners Campaign
Spend$2,000$2,000
Visitors200100
Leads2010
Customers25
Revenue$8,000$25,000