Capture Google Ads Data in Wix Forms
You can connect paid-search activity to the leads it creates by carrying campaign details from the ad click through to form submission. The workflow below uses UTM parameters, hidden form fields, and stored attribution data so each submission arrives with its channel, campaign, ad group, ad, landing page, and landing-page group alongside the visitor's contact details.
Why downstream results matter
Spend, visits, and form completions alone can point budget in the wrong direction. Consider two campaigns that each cost $2,000. One brings 200 visitors and 20 leads; the other brings 100 visitors and 10 leads. On those early metrics, the first campaign looks stronger. The fuller picture changes the decision: the first produces 2 customers and $8,000 in revenue, while the second produces 5 customers and $25,000. The second campaign also has a higher lead-to-customer rate, higher average customer value, lower acquisition cost, and stronger return on ad spend. Tracking source through to customers and revenue prevents a campaign that looks efficient at the click stage from hiding weaker downstream results.
Step 1: Tag each ad destination
UTM parameters are additional text appended to a destination URL. A consistent Google Ads convention is: medium set to paid search, source set to Google, campaign set to the campaign name, term set to the ad group name, and content set to the specific ad. Free URL builders can help assemble these values, but consistency matters more than the builder used. Keep naming stable across campaigns so later reporting does not split one source into several variants.
Step 2: Add hidden fields to the form
Add hidden fields for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. In Wix, drag a Hidden field type into the form. These fields stay out of the visitor's way while giving the submission a place to store attribution values.
Step 3: Let attribution fill the fields at submission
When a visitor submits a form, the attribution tool reads the stored UTM values and fills the hidden fields. In a paid-search example, the channel becomes Paid search, the first drilldown becomes Google, the second becomes the brand campaign, and the third becomes the specific ad. It also records the first landing page and the group that page belongs to, such as a features page within a features section. Because the values are stored in a browser cookie, they survive browsing to a different page before the form is completed.
Step 4: Use the captured record
The submitted record then combines contact details with campaign context. That combined record can be included in a lead notification, sent to a CRM for the sales team, or used in reports that compare campaigns by leads, customers, and revenue. A useful pre-launch checklist is: confirm every ad URL carries the five UTM values, confirm all six hidden fields are present, submit a test form from a tagged URL, submit another after navigating to a different page, and check that the channel values are normalized rather than split by capitalization or naming variants.
What to check beyond Google Ads
A Google Ads-only view misses other lead sources. Capturing all traffic lets reports include organic search, paid social, organic social, and other channels, which is essential when search or social activity drives more leads than paid search. Landing-page capture adds another dimension: compare a whole section, such as a blog, and also compare individual pages within it. Together, channel and landing-page data show both where demand came from and which content first received the visitor.
| Campaign | Spend | Visitors | Leads | Customers | Revenue |
|---|---|---|---|---|---|
| Pool Pumps Campaign | $2,000 | 200 | 20 | 2 | $8,000 |
| Pool Cleaners Campaign | $2,000 | 100 | 10 | 5 | $25,000 |
Illustrative comparison showing why early metrics alone can mislead budget decisions.
Frequently asked questions
What if someone lands from an ad but submits a form on another page?
No. The parameters can be stored in a browser cookie, so they remain available when the visitor completes a form on a later page. That preserves the link back to the original ad even if navigation separates the landing page from the form page.
Why not report directly from raw UTM values?
Raw values can create duplicate sources when capitalization or naming varies, such as Google.com, google, and adwords. A normalization step can group those variants under one paid-search channel, making reporting cleaner than stitching raw values together manually.
What does landing-page capture add beyond channel data?
Capturing the first landing page and its group lets you compare both individual pages and broader site sections. For example, a single article can be reviewed separately from the blog section as a whole.
| Pool Pumps Campaign | Pool Cleaners Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
| Pool Pumps Campaign | Pool Cleaners Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |