Capture Google Ads Data in Formstack in Four Steps
Visitor and lead counts alone can mislead budget decisions. When each submission also carries the campaign, ad group, ad and landing page that produced it, you can follow a lead through to customer and revenue and compare campaigns on cost per customer and return on ad spend, not just form completions.
Why lead counts alone are not enough
Consider two campaigns with identical spend. In the illustrative example, Pool Pumps and Pool Cleaners each spend $2,000. Pool Pumps gets 200 visitors and 20 leads, while Pool Cleaners gets 100 visitors and 10 leads. Judged only at the lead stage, Pool Pumps looks stronger and would attract more budget. But Pool Cleaners produces 5 customers and $25,000 revenue, compared with 2 customers and $8,000 revenue for Pool Pumps. That means a 50% vs 10% lead-to-customer rate, $5,000 vs $4,000 average value per customer, $400 vs $1,000 cost to acquire a customer, and 3x higher return on ad spend for Pool Cleaners. Capturing source data at submission is what makes that fuller comparison possible.
The four-step setup
Step 1: Tag every ad URL. UTM parameters are extra text appended to the destination URL. For example, a destination page such as https://roipaths.com/integrations/salesforce could become https://roipaths.com/integrations/salesforce?utm_medium=paidsearch&utm_source=google&utm_campaign=brand-campaign. A consistent convention helps reporting: medium for paid search, source for Google, campaign for the campaign name, term for the ad group and content for the specific ad. Free UTM builder tools can assemble the URLs.
Step 2: Add hidden fields to the Formstack form. Add six fields: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. In Formstack this is done by dragging in a Hidden field type for each one.
Step 3: Let the attribution script fill the fields. On submission it writes the stored UTM-derived values into the hidden fields, plus the visitor's landing page and its group. For example, a paid-search brand campaign might resolve to Channel = Paid search, Drilldown 1 = Google, Drilldown 2 = Brand campaign and Drilldown 3 = Free account ad, alongside the landing page and group.
Step 4: Use the captured data. The attribution values arrive together with the lead's own details such as name, company, email and phone. They can be included in lead notification emails, sent to a CRM such as Salesforce, Pipedrive or HubSpot for the sales team, or used to build reports showing which campaigns produce leads, customers and revenue.
Decision and verification checklist
Checklist before you rely on the data:
- Every Google Ads destination URL carries the full UTM set, spelled consistently.
- All six hidden fields are present on every lead form, not just one.
- A test submission from a tagged URL populates all six fields correctly.
- A test submission after browsing to a different page still retains the original campaign values.
- The CRM or notification destination maps each hidden field to a visible field.
- Reports group by normalised channel rather than raw UTM text.
What separates a reliable setup from raw UTM capture
Four distinctions matter when choosing a method. First, scope: a method that only handles Google Ads leaves organic search, organic social and paid social unattributed, whereas capturing all traffic lets you see where leads and customers actually come from. Second, persistence: tools that require UTM parameters on the submission page lose attribution when a visitor lands on one page and submits on another; storing values in a browser cookie preserves them across navigation. Third, cleanliness: raw UTM capture fragments reporting when the same source is written as Google.com, google or adwords; normalising variants assigns those leads to one channel. Fourth, landing page context: capturing the landing page and its group shows whether content sections such as a blog generate leads, both as a whole section and per individual post.
| Field | Purpose |
|---|---|
| Channel | Broad source category, e.g. Paid search |
| Channel Drilldown 1 | Source, e.g. Google |
| Channel Drilldown 2 | Campaign, e.g. Brand campaign |
| Channel Drilldown 3 | Ad, e.g. Free account ad |
| Landing Page | First page the visitor arrived on |
| Landing Page Group | Section of that page, e.g. features or blog |
Field names as listed in the setup steps.
Frequently asked questions
What are the four steps in order?
Add UTM parameters to the ad destination URL, add the six hidden fields to the form, let the attribution script populate them from the stored UTM values on submission, then route the completed submission to notifications, a CRM or reporting.
Does the visitor have to submit on the landing page?
No. The attribution values are stored in a browser cookie, so they persist across pages until the form is submitted, even if the submission page differs from the landing page.
Why not capture raw UTM values directly?
Raw values such as Google.com, google and adwords would otherwise appear as separate sources. Normalising capitalization and variant spellings assigns them to the same channel, reducing manual stitching in reports.
| 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 |