Capture Google Ads Data in Lead Pages
A Lead Pages form can tell you that someone enquired. It cannot tell you, on its own, which Google Ads campaign sent them, which ad group they came through, or which ad they clicked. Closing that gap means tagging your ad URLs, placing hidden fields on the form, and letting a capture tool fill those fields before the submission is stored. This guide walks through that sequence and then shows why the resulting data changes budget decisions.
Why lead counts alone can point you the wrong way
Picture the budget meeting. Two Google Ads campaigns sit side by side, one selling pool pumps and one selling pool cleaners, and the only numbers on the slide are spend, visitors and form completions. The pumps campaign has twice the visitors and twice the goal completions for the same spend, so the obvious recommendation is to shift budget toward pumps.
Now add two more columns to the slide: customers and revenue. The recommendation reverses. Cleaners produced fewer leads but more paying customers, a higher average customer value, a lower cost per customer and a stronger return on ad spend. The full comparison is set out in the campaign performance tables below, and the arithmetic behind each line is explained in the next section.
The lesson generalises: if your reporting stops at form completions, you are optimising for the cheapest lead rather than the most valuable customer.
Reading the two campaign tables
The first table is the view you get when a tool such as Google Analytics is your only source: spend, visitors and goal completions. The second table keeps those rows and adds leads, customers and revenue. Both are illustrative figures for the pool-equipment example, not benchmarks for your account.
Work through the second table line by line. Pool pumps: $2,000 spend, 200 visitors, 20 leads, 2 customers, $8,000 revenue. Pool cleaners: $2,000 spend, 100 visitors, 10 leads, 5 customers, $25,000 revenue. From those cells you can derive the following:
- Lead-to-customer conversion: pumps converts 2 of 20 leads (10%); cleaners converts 5 of 10 leads (50%). Note: the original source text states this rate as "950% vs. 10%", which is internally inconsistent with its own "five times greater" wording and with the table cells; the 50% figure computed from the table is used here and the 950% typo is not reproduced.
- Average customer value: $8,000 ÷ 2 = $4,000 for pumps; $25,000 ÷ 5 = $5,000 for cleaners.
- Cost per customer: $2,000 ÷ 2 = $1,000 for pumps; $2,000 ÷ 5 = $400 for cleaners.
- Return on ad spend: $8,000 ÷ $2,000 = 4× for pumps; $25,000 ÷ $2,000 = 12.5× for cleaners, three times higher.
Every one of those conclusions depends on knowing which campaign each customer came from, which is exactly what the setup below captures.
Step 1: tag your Google Ads URLs
UTM parameters are extra text appended to the end of a destination URL. If the page you want to send people to is https://roipaths.com/integrations/salesforce, the tagged version adds a query string such as utm_medium=paidsearch&utm_source=google&utm_campaign=brand-campaign.
You can invent your own values, but a consistent convention for Google Ads pays off later. A workable pattern:
- UTM Medium: Paid search
- UTM Source: Google
- UTM Campaign: the name of your Google Ads campaign
- UTM Term: the name of the ad group the ad belongs to
- UTM Content: the specific ad
Building these URLs is straightforward, and free builders exist online if you would rather not assemble them by hand. The important discipline is to apply the same pattern to every ad, because inconsistent values are what make later reporting messy.
Step 2: add hidden fields to the Lead Pages form
Hidden fields are form inputs that visitors never see but that still travel with the submission. Add these six to your lead capture form:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
In Lead Pages, drag a 'Hidden' field type into the form for each one. The field names must match exactly, because the capture tool looks for those names when it writes values in.
Step 3: let the capture tool fill the fields
Once the hidden fields exist, the capture tool tracks where each visitor came from and populates the fields from the UTM values at the moment a form is completed.
Take a visitor who arrives from a brand campaign in paid search. The fields would be filled as follows: Channel = Paid search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Brand campaign; Channel Drilldown 3 = Free account ad. The visitor's landing page (for example, a cloud-storage features page) and its first landing page group (for example, features) are recorded as well.
That mapping is the heart of the setup: three drilldown levels carry campaign, ad group and ad, while the two landing page fields describe the page that received the click.
Step 4: store the data with the lead
When a visitor submits the form, the Google Ads values are saved alongside whatever the visitor typed: name, company, email, phone and so on. From there you have three practical routes for the data:
- Include it in new-lead notification emails so the source is visible the moment an enquiry arrives.
- Pass it into your CRM so sales can see where each lead originated.
- Feed it into reports that show which campaigns produce leads, customers and revenue.
A quick pre-launch check: submit a test form from a tagged URL, confirm all six hidden fields carry values, and confirm the same values appear in the destination system.
What separates a reliable setup from a fragile one
Several properties matter more than the specific tool you choose.
All traffic, not just ads. A capture method that only handles Google Ads leaves you blind to organic search, paid social and organic social. If most of your leads arrive through SEO, a Google-Ads-only report will misdirect your investment.
Persistence across pages. Many UTM methods require the parameters to be present on the page where the form is completed. That breaks when a visitor lands on a campaign page, clicks 'Get A Quote' and completes the form somewhere else. A cookie-based approach keeps the values available regardless of how the visitor navigated before submitting.
Consistent source values. Raw parameters can arrive as Google.com, google and adwords for the same traffic source. Without normalisation you must stitch three rows together by hand. A capture layer that accounts for capitalisation and similar inconsistencies assigns those leads to one channel.
Landing page detail. Recording both the landing page and its group lets you judge a whole section, such as a blog, and then drill into individual posts to see which ones generate leads, customers and revenue.
Field and control map
Use this map to check that each hidden field has a defined source before you publish the form:
- Channel — the broad traffic type, e.g. Paid search.
- Channel Drilldown 1 — the source within that channel, e.g. Google.
- Channel Drilldown 2 — the campaign name.
- Channel Drilldown 3 — the ad group or specific ad.
- Landing Page — the first page the visitor saw.
- Landing Page Group — the section that page belongs to.
If any field is left unmapped, the corresponding column in your reports will be empty and the campaign comparison in the tables above becomes impossible to reproduce.
When this setup is worth the effort
The work pays off when your campaigns differ in lead quality, not just lead volume, and when you can act on the difference by moving budget. If every campaign converts at the same rate and produces customers of similar value, the extra fields add little. If conversion rates and customer values vary widely, as in the pool-equipment example, lead-only reporting will actively mislead you.
A reasonable starting point is to tag one or two campaigns, add the hidden fields to a single high-traffic form, and compare the resulting customer and revenue figures against your current lead-only view before rolling the pattern out across every form.
| Metric | Pool Pumps Campaign | Pool Cleaners Campaign |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
Illustrative example figures for a pool-equipment business, not benchmarks. This is the limited view available when only visitor and goal data are measured.
| 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 figures for a pool-equipment business, not benchmarks. Derived rates (conversion, average customer value, cost per customer, ROAS) are calculated from these cells in the body text.
Frequently asked questions
Do I need to tag every Google Ads URL, or only some?
Tag every ad you want to attribute. A campaign that lacks UTM parameters will not populate the hidden fields, so its leads will appear without a campaign source and cannot be compared against tagged campaigns in your reports.
What happens if a visitor lands on one page and submits the form on another?
With a capture method that stores UTM values in a cookie, the values persist and are written into the hidden fields wherever the form is completed. Methods that rely on the parameters being present on the form page lose the data in this scenario.
Why do my reports show several different Google sources?
Raw UTM values are case- and format-sensitive, so Google.com, google and adwords can each appear as a separate source. A capture layer that normalises these inconsistencies assigns all of them to one channel, which removes the manual stitching.
Can I see which blog posts generate customers, not just leads?
Yes, if you record both the landing page and the landing page group. The group lets you assess a section such as the blog as a whole, and the individual landing page lets you drill into specific posts once customer and revenue data is attached.
How do I know the setup is working before I rely on the reports?
Submit a test form from a tagged URL and check that all six hidden fields carry values and that the same values arrive in your CRM or notification email. If any field is blank, confirm the field name matches exactly and that the URL carries the corresponding UTM parameter.
| 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 |