Capture Google Ads Data in Formlets
Formlets can collect a name, email and phone number, but on its own it cannot tell you which Google Ads campaign produced that lead. The missing link is a small set of hidden fields that receive campaign values from the page URL and travel with the submission. This guide shows how to tag ads, add those fields in Formlets, verify the values and use the resulting data to compare campaigns by customers and revenue.
Why lead counts can mislead you
A campaign that produces many form completions is not automatically the better campaign. Consider a pool-equipment business running two Google Ads campaigns, one for pool pumps and one for pool cleaners. A visitor-and-lead report shows both campaigns spending $2,000, the pump campaign producing 200 visitors and 20 leads, and the cleaner campaign producing 100 visitors and 10 leads. On that view the pump campaign looks twice as effective. The full picture changes when customer and revenue data are attached to each lead. The pump campaign produced 2 customers and $8,000 in revenue; the cleaner campaign produced 5 customers and $25,000. The cleaner campaign wins on customer count, lead-to-customer conversion (50% versus 10%), average customer value ($5,000 versus $4,000), cost per acquisition ($400 versus $1,000) and return on ad spend. The lesson is simple: judge paid search by the outcomes the business cares about, not by the last step in the form. The two reference tables below show the same campaigns at two levels of detail; treat the figures as an illustrative example, not a benchmark for your own account.
Step 1: Tag every ad URL with UTM parameters
UTM parameters are extra query-string values appended to the destination URL. They do not change the page a visitor sees, but they let a script read where the click came from. A tagged URL looks like the base address followed by a question mark and key-value pairs, for example a medium of paidsearch, a source of google and a campaign name. For Google Ads, a consistent convention is the foundation of clean reporting. Use paid search as the medium, Google as the source, the campaign name as the campaign value, the ad group name as the term and an identifier for the specific ad as the content value. Free URL builders can assemble the string for you. The important discipline is consistency: decide on lowercase values and a naming pattern before you tag dozens of ads.
Step 3: Let the attribution script fill the fields
Once the hidden fields exist, the attribution script reads the visitor's source and writes values into them at submission time. A visitor arriving from a paid-search brand campaign would produce a channel of Paid search, a first drilldown of Google, a second drilldown of the campaign name and a third drilldown of the ad name. The script also records the landing page and its group, so a page such as a cloud-storage feature page yields both the full path and the broader section. This is where a field map helps: check that each hidden field receives the value you expect before you rely on the report.
Step 4: Use the captured data
When a visitor submits the form, the campaign values are stored next to the name, email, phone and company details. From there you can include the source in new-lead notification emails, pass it into your CRM so the sales team sees it, and build reports that connect campaigns to leads, revenue and customers. The value compounds when the same fields are used consistently across every form on the site.
Field map: what each hidden field should contain
Use this checklist to confirm your Formlets fields are wired correctly. Channel holds the broad traffic type, such as Paid search. Channel Drilldown 1 holds the source, such as Google. Channel Drilldown 2 holds the campaign name. Channel Drilldown 3 holds the ad or ad group identifier. Landing Page holds the full URL path of the first page visited. Landing Page Group holds the section of the site, such as a blog directory. If any of these is blank on a test submission, trace the corresponding UTM parameter first.
Why a dedicated attribution layer helps
Raw UTM capture fails in three distinct ways, and each failure needs a different fix. The first is scope: a raw capture only reports the traffic you tagged, so untagged organic search, social and referral visits never appear beside your paid campaigns. The second is timing: if the form lives on a page the visitor reaches after leaving the ad landing page, the query string is no longer in the address bar and the values are simply absent. The third is consistency: the same source written as Google.com, google or adwords becomes three separate rows that someone has to reconcile by hand. A useful diagnostic is to submit a test form from a second page and check whether the campaign field is blank. A blank field points to the timing problem, while a field that shows an unexpected variant points to the consistency problem. An attribution layer that classifies all channels, stores the original source in a cookie and normalises variants addresses all three at once. It also records the landing page and its group, so you can compare a whole blog section against individual posts.
Pre-launch QA checklist
Before you send traffic, run these checks. Submit a test form from a tagged URL and confirm every hidden field is populated. Submit from an untagged URL and confirm the fields fall back to a direct or organic value rather than breaking. Click from the ad landing page to a second page with the form and confirm the original campaign values still arrive. Check that the campaign, ad group and ad names in your reports match the names in Google Ads. Finally, confirm the CRM or email tool receives the fields in the expected order.
| Metric | Pool Pumps Campaign | Pool Cleaners Campaign |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
Illustrative example from the original article; figures are not a benchmark.
| Metric | 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 example from the original article; figures are not a benchmark.
Frequently asked questions
Do UTM parameters change what visitors see on the page?
No. They are extra text appended to the URL and are read by the attribution script, not displayed to the visitor.
What happens if a visitor lands on one page and submits the form on another?
Without a persistent attribution layer, the UTM parameters are lost when the visitor navigates away from the landing page. A cookie-based layer keeps the original source available for the later submission.
Why do my reports show Google.com, google and adwords as separate sources?
Raw UTM values are case-sensitive and are not normalised. An attribution layer groups these variants into a single channel so you do not have to merge rows manually.
Can I track leads from organic search and social as well as Google Ads?
Yes, provided the attribution layer classifies all traffic channels rather than only paid search. The same hidden fields then carry the source for every lead.
| 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 |