How to capture Google Ads data in Wufoo forms
A Wufoo form can collect a name and email without telling you which ad produced the lead. This guide shows how to attach Google Ads campaign data to every submission, so you can compare campaigns by leads, customers and revenue rather than by clicks alone.
Why leads alone can point you to the wrong campaign
Imagine a pool equipment business running two Google Ads campaigns: one for pool pumps and one for pool cleaners. A click-and-form report can make the pump campaign look stronger because it produces more visitors and more form completions. But form completions are not the same as customers.
Once customer count and revenue are attached to each lead, the picture can reverse. A campaign with fewer leads may still produce more customers, a higher average customer value and a lower cost per customer. That is the decision this setup supports: not simply counting form fills, but connecting each form fill to the campaign, ad group, ad and landing page behind it.
The two reference tables below show the same fictional pool business at two levels of detail. The first table contains spend, visitors and goal completions. The second adds leads, customers and revenue. Read them together to see why a lead-only view can misallocate budget.
Reference example: clicks and form completions vs. customers and revenue
The tables below are the supplied reference figures for a fictional pool equipment business. They are illustrative, not a benchmark for your own campaigns. Use them to compare what a click-level report shows with what a revenue-level report shows.
Table 1: spend, visitors and goal completions by campaign.
Table 2: the same campaigns with leads, customers and revenue added.
When you read the second table, check three derived measures rather than only the lead count: lead-to-customer conversion, average customer value and cost per customer. In the supplied example, the pool cleaners campaign has more customers, a higher lead-to-customer rate, a higher average customer value and a lower cost per customer. That is the kind of comparison the Wufoo setup is meant to make possible.
Step 1: Tag your Google Ads URLs with UTM parameters
UTM parameters are short text tags appended to the destination URL. They travel with the click and give the form a way to identify the source. A typical tagged URL looks like this:
https://roipaths.com/integrations/salesforce?utm_medium=paidsearch&utm_source=google&utm_campaign=brand-campaign
The exact values are yours to choose, but a consistent Google Ads convention makes reporting easier. A common pattern is:
- UTM Medium: paid search
- UTM Source: Google
- UTM Campaign: the Google Ads campaign name
- UTM Term: the ad group name
- UTM Content: the specific ad
You can build these URLs by hand or with a free UTM builder. The important part is consistency: use the same spelling and capitalization across campaigns so the same source is not split into several variants.
Step 3: Let the attribution script fill the hidden fields
Once the hidden fields exist, the attribution script reads the visitor's source and writes the matching values into the form. The script does not require the visitor to submit the form on the same page where they first landed.
Here is an illustrative mapping. Suppose a visitor arrives from a paid search brand campaign and later submits a form. The hidden fields could be populated as follows:
- Channel = Paid search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Brand campaign
- Channel Drilldown 3 = Free account ad
- Landing Page = the first page the visitor landed on
- Landing Page Group = the section of the site that page belongs to
The exact values depend on the UTM tags on the ad URL. If the tags are missing or inconsistent, the script has less to work with.
Step 4: Use the captured data in Wufoo and beyond
Each Wufoo submission now contains the visitor's form answers plus the attribution fields. You can use that data in several ways:
- Include the attribution fields in new-lead notification emails so the source is visible immediately.
- Send the fields to a CRM such as Salesforce, HubSpot or Dynamics so sales can see where each lead came from.
- Build reports that group leads, customers and revenue by campaign, ad group, ad or landing page.
The value comes from joining the form submission to later customer and revenue data. A lead source field on its own is useful; a lead source field connected to closed revenue is what supports budget decisions.
Field and control map
Use this map to check that each hidden field is receiving the value you expect.
- Channel: the high-level traffic type, such as paid search or organic search.
- Channel Drilldown 1: the source within that channel, such as Google.
- Channel Drilldown 2: the campaign name.
- Channel Drilldown 3: the ad group or specific ad, depending on how you tag UTM Term and UTM Content.
- Landing Page: the first page the visitor saw.
- Landing Page Group: the section or category of that first page.
Before launching, submit a test form from a tagged ad URL and confirm that all six fields arrive in Wufoo with the expected values. Then confirm that the same fields reach your CRM or reporting tool.
What a dedicated attribution layer adds
A raw UTM capture setup can work, but it has two common failure points.
First, many capture methods only read the UTM parameters on the page where the form is submitted. Consider a SaaS visitor who clicks a Google Ad for a pricing page, reads the plans, then clicks a "Book a demo" button that opens a separate demo-request form. The form page has no UTM parameters in its URL, so a same-page capture method records nothing. A script that writes the values to a cookie in the visitor's browser keeps them available across pages, so the demo form still receives the original campaign data regardless of how many pages the visitor viewed first.
Second, raw UTM values can be messy. One campaign may use UTM_Source=Google.com, another may use UTM_Source=google and a third may use UTM_Source=adwords. A report built on raw values would show three separate sources. A normalization layer groups those variants into one channel so the report reflects the actual source.
Capturing both Landing Page and Landing Page Group adds a second dimension to the same data. Landing Page records the specific page a visitor first saw, while Landing Page Group records the section that page belongs to. That pairing lets you compare a whole section, such as a blog, against paid campaigns, and also see which individual pages within that section produce the most leads, customers and revenue.
Pre-launch checklist
Before you rely on the data, run through these checks:
- Every Google Ads URL uses the same UTM naming convention.
- The Wufoo form contains all six hidden fields with the expected names.
- A test submission from a tagged URL populates every field.
- A test submission after navigating from the landing page still carries the original source.
- The CRM or reporting tool receives the fields and maps them to the correct properties.
- Reports group by campaign, ad group, ad and landing page, not only by lead count.
- Customer and revenue data can be joined back to the original lead source.
Frequently asked questions
Do I need to put UTM parameters on every Google Ads URL?
Yes, if you want the form to identify the campaign, ad group or ad. Without UTM tags, the form can still record that a visitor submitted it, but it cannot reliably attribute that submission to a specific Google Ads campaign. Use a consistent convention so the same source is not split into several variants.
What happens if a visitor lands on one page and submits the form on another?
A raw UTM capture setup may lose the parameters when the visitor navigates away from the landing page. A script that stores the values in a cookie keeps the original source available across pages, so the form submission still carries the campaign data.
Why do my reports show Google, Google.com and adwords as separate sources?
Those are different raw UTM values for what is effectively the same source. A normalization layer groups capitalization and domain variants into a single channel. Without that layer, you would need to merge the variants manually before reporting.
Can I capture landing page data as well as campaign data?
Yes. The supplied field set includes Landing Page and Landing Page Group. The first records the page the visitor initially landed on; the second records the section or category that page belongs to. Together they let you compare a blog section against paid campaigns.
| Pool Pumps Campaign | Pool Cleaners Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
Illustrative reference figures for a fictional pool equipment business. They are not a benchmark and do not represent current campaign performance.
| 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 |
Illustrative reference figures for a fictional pool equipment business. Derived measures such as lead-to-customer rate, average customer value and cost per customer are calculated from these rows, not separately supplied.