Capture Google Ads data in Paperform in 4 steps
Knowing which paid campaigns produce enquiries is only the first layer. To judge value, you also need to follow each lead through to customer and revenue outcomes. This guide explains a four-step setup that stores campaign information with every Paperform submission, so reporting can connect spend to downstream results.
Why lead volume alone can mislead
Imagine two campaigns with identical spend. One brings more visitors and form submissions, yet the other creates more customers and higher revenue. Judging only by traffic or goal completions would point to the wrong winner.
The captured example makes this concrete. Pool Pumps and Pool Cleaners each cost $2,000. Pool Pumps generated 200 visitors, 20 leads, 2 customers and $8,000 revenue. Pool Cleaners generated 100 visitors, 10 leads, 5 customers and $25,000 revenue. Once customer and revenue data are included, Pool Cleaners shows a 50% lead-to-customer rate versus 10%, $5,000 average customer value versus $4,000, $400 acquisition cost versus $1,000, and roughly three times the return on ad spend.
Checklist for useful reporting:
- Record the source of every lead, not only paid-search leads
- Carry that source through to customer and revenue records
- Compare conversion rate, customer value, acquisition cost and return on ad spend
- Review landing pages as well as campaigns, so content sections can be judged on downstream value
Four steps to capture the data in Paperform
Step 1: Tag each ad destination with UTM parameters. These are additional URL elements that identify medium, source, campaign, term and content. A consistent convention for paid search is medium for the channel type, source for the platform, campaign for the campaign name, term for the ad group, and content for the specific ad.
Step 2: Add hidden fields to the Paperform. The fields needed are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. In Paperform, this is done by dragging in a Hidden field type for each one.
Step 3: Let the attribution tool populate those fields. It watches visitor origin and, at submission, writes the stored UTM values into the hidden fields. It also adds the first landing page and its group. For a paid-search brand campaign example, the populated values could be Channel = Paid search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand campaign, and Channel Drilldown 3 = Free account ad, alongside the landing page and group.
Step 4: Use the captured submission data. Each completed form then contains both the contact details entered by the visitor and the campaign and landing-page context. That combined record can be shown in lead notifications, sent to a CRM, or used in reports on which campaigns produce leads, customers and revenue.
What to check before you trust the reports
Four distinctions matter when choosing a method:
- Coverage: A channel-wide approach records organic search, paid social, organic social and other sources, not only Google Ads. That prevents over-investing in paid media when search or content is driving most customers.
- Persistence: Raw UTM capture usually fails when the form sits on a later page. Storing values in a browser cookie preserves them across browsing, so a visitor who lands from an ad, browses elsewhere, and then requests a quote is still attributed correctly.
- Cleanliness: Inconsistent tagging such as capitalised, lowercase and domain variants of the same source creates fragmented reports. Normalisation groups those variants under one channel.
- Landing-page context: Recording the exact first page and its group lets you compare a whole section, such as a blog, and also drill into individual posts or pages.
Before publishing, test one submission from a tagged ad, confirm every hidden field is populated, then check the same values appear in the notification or CRM record.
Wrap up
With campaign, landing-page and contact data stored together, reporting can show which Google Ads campaigns generate customers and revenue, and which other channels deserve more investment. Before committing to a tool, check its current trial length, plan limits and cancellation terms directly with the provider, since these can change.
| Measure | 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 |
Captured example from the source; use as an illustration of why downstream data matters, not as a current benchmark.
Frequently asked questions
Will UTM data be lost if the form is not on the landing page?
No. The attribution tool described stores the UTM values in a browser cookie, so they remain available when the visitor later reaches a form on a different page from the first landing page.
Does it capture only channel data?
Yes. It also records the first landing page and its group, allowing reporting by individual page and by site section such as a blog.
How does it handle inconsistent UTM tagging?
It normalises common inconsistencies such as capitalisation and variant source spellings, so reports do not need manual stitching of raw UTM values.
| 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 |