Capture Google Ads Data in 123FormBuilder
You can connect a 123FormBuilder submission to the Google Ads campaign that produced it by tagging ad URLs, adding hidden fields to the form, and letting an attribution tool populate those fields when a visitor submits. The result is a lead record that shows not only who contacted you, but which campaign, ad group, and ad brought them in — so reporting can follow through to customers and revenue, not stop at clicks and form completions.
Why lead origin matters beyond visitors and form completions
Visitor and lead counts alone can mislead budget decisions. Consider two campaigns that each spend $2,000. One brings 200 visitors and 20 leads; the other brings 100 visitors and 10 leads. On early metrics, the first looks stronger. Add downstream results and the picture can reverse: the second campaign may produce 5 customers and $25,000 in revenue, versus 2 customers and $8,000 for the first. That means a higher lead-to-customer rate (50% versus 10%), higher value per customer ($5,000 versus $4,000), lower cost per customer ($400 versus $1,000), and roughly three times the return on ad spend. Capturing campaign origin on the lead itself is what makes that comparison possible.
Four steps to capture Google Ads data in 123FormBuilder
Follow these four steps in order. Skipping the tagging step means there is nothing to capture; skipping the hidden fields means there is nowhere to store it.
1. Add UTM parameters to your ads
UTM parameters are short text values appended to a destination URL. For example, a page URL can end with utm_medium=paidsearch, utm_source=google, and utm_campaign=brand-campaign. A consistent convention for Google Ads is: UTM Medium = Paid search; UTM Source = Google; UTM Campaign = the campaign name; UTM Term = the ad group name; UTM Content = the specific ad. Use the same values every time — inconsistent tagging is the most common cause of messy reporting later. Free UTM builder tools can help assemble the URLs.
3. The attribution tool writes the data into the hidden fields
Once the fields exist, the attribution tool reads the UTM values from the visitor's arrival, stores them in a browser cookie, and writes them into the hidden fields at submission time. A paid-search brand campaign visit might be recorded as Channel = Paid search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand campaign, and Channel Drilldown 3 = Free account ad. The tool also records the landing page (for example, dropbox.com/features/cloud-storage) and its group (for example, features). Because the values are held in a cookie, they survive the visitor browsing to other pages before submitting — for instance, landing on an ad page, then clicking through to a separate quote-request form.
4. The data is captured with the submission
On submission, the captured values travel with the visitor's name, company, email, and phone. You can then include them in lead notification emails, pass them to a CRM such as Salesforce, Pipedrive, or Dynamics so sales sees each lead's origin, and build reports showing which campaigns produce leads, customers, and revenue.
Why an attribution tool beats raw UTM capture
Raw UTM capture alone has three weaknesses. First, it only records tagged paid traffic, so organic search, organic social, and paid social leads have no origin. Second, it requires the UTM parameters to still be present on the exact page where the form is submitted, so multi-page journeys lose attribution. Third, it stores values exactly as tagged: UTM_Source=Google.com, utm_source=google, and utm_source=adwords become three separate sources that must be reconciled by hand. An attribution tool that normalizes values, remembers them across pages, and covers all channels avoids all three problems.
Landing-page data and a pre-launch checklist
Beyond channel data, landing-page capture shows which parts of your site generate leads and revenue. Recording both the full landing page and its group lets you compare a whole section, such as a blog, and then drill into individual posts. Use this as a checklist when reviewing reports: confirm every campaign URL is tagged, confirm all six hidden fields are on every lead form, test a submission from a tagged URL, and verify the values appear in the notification email or CRM record before relying on the reports.
| Field | What it stores | Example |
|---|---|---|
| Channel | Traffic channel | Paid search |
| Channel Drilldown 1 | Source within the channel | |
| Channel Drilldown 2 | Campaign | Brand campaign |
| Channel Drilldown 3 | Ad group or ad | Free account ad |
| Landing Page | First page the visitor arrived on | dropbox.com/features/cloud-storage |
| Landing Page Group | Section of that page | features |
Field names as listed in the setup steps; example values from the worked paid-search example.
| 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 |