Capture Google Analytics Data in 123FormBuilder Forms
A form submission on its own usually tells you who contacted you, not how they found you. Adding structured visit data to the submission closes that gap, so each lead in your CRM can be traced back to the channel, campaign detail and landing page behind it.
Why form submissions need visit context
Google Analytics is useful for understanding how visitors arrive at a website. The missing piece is what happens after that visit: a visitor may become a lead, an opportunity, a customer or revenue, and those outcomes live in the CRM rather than in visit reports. When the visit context travels with the form submission, reporting can compare channels and campaigns on leads and revenue instead of clicks and sessions alone.
The workflow has two parts. A small script on the website records how each visitor arrived and groups the visit into a standard channel such as Organic Search, Paid Social or Paid Search. It keeps that information in the browser. When the visitor submits a form, the script fills hidden fields on the form with the channel, landing page and related detail. The form tool then stores those values alongside the visible answers, such as name and email address, and can forward the whole record onward.
Four-step setup checklist
Work through these steps in order:
- Add six hidden fields to the form and label them exactly as listed below.
- Confirm the attribution script is installed on the website so it can fill those fields automatically at submission.
- Submit a test form and check that all six hidden fields arrive populated, not blank.
- Connect the form tool to your CRM or other destination using its native integrations or a connector such as Zapier.
- Map each hidden field to the matching field in the destination so channel reporting uses the captured values.
- Run a report in the destination grouped by channel and landing page to confirm leads are attributed before relying on the data.
Step 1: Add six hidden fields
In the form editor, open the field you want to hide and choose the hide-field option in the edit panel. Repeat this for six fields, labelled:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
The first field gives the broad channel. The three drilldowns add progressively finer detail about that channel. The final pair records the exact landing page and the page group or category it belongs to. Keeping the labels consistent matters, because the script fills fields by their labels and the downstream mapping depends on them.
Step 2: Hidden fields are filled automatically, with an example
Once the hidden fields exist, the script completes them automatically when a visitor submits the form. Consider a visitor who clicks a paid search ad and lands on a product features page before completing the form. In that scenario the fields would be filled as follows, with the exact drilldown values depending on the UTM parameters used by the advertiser:
- Channel: Paid Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Brand Campaign
- Channel Drilldown 3: Dropbox
- Landing Page: the features page the visitor landed on
- Landing Page Group: the category containing that page
The same pattern applies to other channels. An organic visitor would instead produce a channel such as Organic Search, with drilldowns reflecting the organic source and any keyword detail available, and the landing-page pair would still identify the page and its category.
Steps 3 and 4: Capture on submission, then forward to your CRM
At submission, the form tool captures both the visible answers and the hidden attribution values in a single record. That combined record is what makes later reporting possible: the lead's contact details sit next to the channel and landing page that produced them.
From there, native integrations or a connector such as Zapier can send the record to a CRM such as Salesforce, Pipedrive, HubSpot or Zoho CRM, as well as to email marketing or billing tools that integrate with the form tool. Once the data is in the destination, reports can show which channels drive the most leads, sales opportunities, customers and revenue, and which landing pages and subcategories perform best. That makes it easier to shift time and budget toward the pages and channels that actually return results, and to judge campaign return on investment from outcomes rather than traffic alone.
| Hidden field | What it records | Use it to answer |
|---|---|---|
| Channel | Broad channel for the visit, such as Paid Search or Organic Search | Which channel brought in this lead? |
| Channel Drilldown 1 | First level of channel detail, such as the search engine or platform | Which platform within the channel? |
| Channel Drilldown 2 | Second level of detail, such as the campaign | Which campaign within the platform? |
| Channel Drilldown 3 | Third level of detail, such as the advertiser or account | Which advertiser or account? |
| Landing Page | Exact page the visitor landed on | Which page converted this lead? |
| Landing Page Group | Category or group containing the landing page | Which page category performs best? |
Field labels are the labels the script expects on the form; drilldown values vary by channel and by the UTM parameters in use.
Frequently asked questions
Why capture analytics data on a form if Google Analytics already tracks visits?
Google Analytics shows how visitors reached a site, but that visit-level view does not by itself show which campaigns produced leads, customers or revenue. Capturing the channel and landing-page values on the form submission connects the lead record to the visit that produced it.
Which hidden fields should be added to a 123FormBuilder form?
Six hidden fields are needed: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. The three drilldowns hold progressively more specific channel detail, while the landing-page pair records both the exact page and its category.
Where can the captured data be sent after submission?
After submission, the form tool's native integrations or a connector such as Zapier can forward the captured values to systems including Salesforce, Pipedrive, HubSpot and Zoho CRM, alongside email marketing and billing tools that integrate with the form tool.
What do channel and landing-page data each tell you?
Channel data records how the visitor arrived, for example Organic Search, Organic Social, Paid Search or Direct, with extra detail such as keyword or ad group for paid search. Landing-page data records the exact page and its category, so reports can show which pages and subcategories perform best.