Capture Google Ads Data in Leadformly
Knowing which paid campaign produced a lead is only the start. The useful question is which campaign produced a customer and revenue. This guide explains how UTM tagging, hidden form fields and browser-stored attribution work together in Leadformly so each submission carries its campaign origin into notifications, a CRM or reporting.
Why downstream tracking changes the decision
Visitor and form counts can mislead budget decisions. Consider two campaigns that each cost $2,000. One brings 200 visitors and 20 leads; the other brings 100 visitors and 10 leads. On early metrics alone, the first looks stronger.
The downstream picture can reverse that conclusion. If the first produces 2 customers and $8,000 in revenue while the second produces 5 customers and $25,000, the smaller campaign is actually performing better. Its lead-to-customer rate is 50% compared with 10%, its customer value is $5,000 compared with $4,000, its cost per customer is $400 compared with $1,000, and its return on ad spend is three times higher.
Decision checklist: attach campaign origin to every lead, carry that origin through to customer and revenue records, compare campaigns on downstream value rather than clicks alone, and shift budget only after the full journey is visible.
Four-step setup and field map
Start with consistent tagging on the destination URL. A practical Google Ads convention is: medium for the paid channel, source for the platform, campaign for the campaign name, term for the ad group, and content for the specific ad. Free URL builders can help assemble these values.
Next, add hidden fields to each Leadformly form. In Leadformly, this is done by dragging in a Hidden field type. The fields needed are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group.
When a visitor arrives with UTM parameters, attribution logic reads them, stores them in the browser, and populates the hidden fields at submission. For example, a paid-search brand campaign might produce Channel = Paid search, Drilldown 1 = Google, Drilldown 2 = Brand campaign and Drilldown 3 = Free account ad, together with the first landing page and its group.
Field map: Channel summarises the traffic type; the three drilldowns add progressively finer campaign detail; Landing Page records the exact first page; Landing Page Group records its section, such as a blog or features area. On submission, those values travel with the contact details the visitor entered.
Using the data and avoiding common gaps
Captured values can be added to lead notification emails for immediate context, passed to a CRM so the wider team can see lead origin, or used in reports that connect campaigns to leads, customers and revenue.
Three distinctions matter. First, attribution should cover all traffic, not only paid search, so organic search and social sources are visible in the same reporting view. Second, storing attribution in a cookie preserves it when the form sits on a later page than the ad landing page. Third, normalised channel values avoid splitting one source into multiple records because of capitalisation or naming variants such as Google.com, google and adwords.
Landing-page capture adds another layer: reporting can show performance for a whole section and for individual pages within it, helping teams judge whether content areas contribute to pipeline and revenue.
| Field | Purpose |
|---|---|
| Channel | Broad traffic type, such as paid search |
| Channel Drilldown 1 | Platform or source detail |
| Channel Drilldown 2 | Campaign detail |
| Channel Drilldown 3 | Ad or ad-group detail |
| Landing Page | First page visited |
| Landing Page Group | Section of the first page |
Field names are as listed in the captured setup steps.
Frequently asked questions
What if the form is on a different page from the ad landing page?
No. Attribution is stored in the browser, so a visitor can move from the ad landing page to another page, complete the form there, and still be linked back to the original campaign.
Why not capture raw UTM values directly?
Raw values can split one source into several records when capitalisation or naming differs. Normalised channel fields group those variants under the intended channel, making reporting cleaner.
Can landing-page performance be measured too?
Yes. The first page visited and its section can be recorded alongside channel data, so a blog post or other content area can be assessed for leads, customers and revenue.
| 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 |