How to Capture Google Analytics Data in Formsite Forms
Formsite collects the answers people type, but it does not know on its own whether a lead arrived from a paid search ad, an organic result or a social post. This guide shows how to add six hidden fields to a Formsite form and have a tracking script fill them with channel and landing page details at submission time, so the same record that reaches your CRM also explains where the lead came from.
Why put acquisition data inside the form
Growth decisions depend on knowing which channels and campaigns produce leads and customers that pay back their cost. Analytics alone shows sessions; it does not attach a source to the named person who filled in your form. Moving channel information into the form record closes that gap, because the source travels with the lead into whatever system stores it. The practical result is reporting that connects marketing spend to pipeline rather than to pageviews.
What the tracking script does before the form is submitted
A small tracking script supplies the acquisition data in this workflow. You place its code on your website, and it inspects each visit as it happens and sorts the visit into a marketing channel such as Paid Search, Organic Search or Paid Social. Those details are kept in the visitor's browser rather than written into the form immediately. When the visitor opens a Formsite form, the script writes the stored values into the hidden fields, and on submission they are carried along with the rest of the answers to your CRM and any other tool connected to Formsite.
Step 2: Let the tracking script fill the fields
Once the hidden fields exist, the form is ready. Nothing needs to be typed by the visitor and no extra question appears on screen. The tracking script completes the fields in the background based on the campaign parameters in use.
Take a paid search example. A visitor searches, clicks an ad, and lands on a product page before completing the form. The fields would read Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand Campaign and Channel Drilldown 3 = Dropbox. The Landing Page field would hold the full URL of the first page viewed, such as www.dropbox.com/features/productivity_, and Landing Page Group would hold its section, /features.
Step 3: Confirm the values arrive with the submission
When the visitor submits name, mobile, address and the rest, Formsite stores the channel and landing page values alongside those answers. Check a test submission in the Formsite results view before connecting anything downstream: if the hidden fields are present but blank, the visit carried no usable campaign data; if the fields are absent entirely, the form is missing them. Those are different problems with different fixes.
Step 4: Pass the record to your CRM or other tools
Formsite's native integrations or Zapier can forward the completed submission, hidden fields included, to systems such as Salesforce, Hubspot, Pipedrive and Zoho CRM. Map each hidden field to a matching property or custom field in the destination so the values stay reportable rather than sitting in a notes field.
The two kinds of data you end up with
Channel data answers how someone arrived. Beyond the top-level channel, the drilldown fields carry the finer detail for that channel; for paid search that means the ad group, keyword and campaign behind the click. Landing page data answers where the visit began: the first URL viewed and the section it belongs to. Together they let you compare, for example, leads from paid search against leads from organic search, then break each down by the content that introduced them.
Reading landing page data in reports
If the first page a visitor sees is dropbox.com/blog/best-file-storage-tools, the Landing Page field records that URL and Landing Page Group records /blog. In a CRM report you can group by the page group to see which sections of the site generate leads, then drill into individual posts to see which ones perform best. This is the difference between knowing that the blog works and knowing which article does.
Pre-launch checklist
- Six hidden fields exist on every form that should report a source.
- Field labels match the list exactly, including spacing and capitalisation.
- A test submission shows non-empty Channel and Landing Page values.
- Each hidden field is mapped to a real destination field in the CRM or email tool.
- Reports group by Channel and Landing Page Group before drilling into individual campaigns or posts.
| Hidden field label | What it holds | Example value |
|---|---|---|
| Channel | Top-level marketing channel for the visit | Paid Search |
| Channel Drilldown 1 | First level of detail within the channel | |
| Channel Drilldown 2 | Second level of detail within the channel | Brand Campaign |
| Channel Drilldown 3 | Third level of detail within the channel | Dropbox |
| Landing Page | Full URL of the first page viewed | www.dropbox.com/features/productivity_ |
| Landing Page Group | Section that the landing page belongs to | /features |
Example values come from a paid search scenario and depend on the UTM parameters in use; other channels will produce different drilldown values.
Frequently asked questions
Do visitors see or fill in these hidden fields?
No. Hidden Field elements are not shown on the published form, and the tracking script writes values into them in the background, so the visitor's experience is unchanged.
Why is the Channel field empty on some submissions?
An empty Channel usually means the visit carried no campaign parameters the tracking script could classify, or the field label does not match the expected name. Confirm the label first, then check whether the visit had usable campaign data.
Do I need Zapier to get the data into my CRM?
Not necessarily. Formsite's native integrations can forward submissions, and Zapier is an option for destinations without a native connection. Either route works as long as the hidden fields are mapped to real fields in the destination.
Can I report on individual blog posts rather than the whole blog?
Yes. Group by Landing Page Group to see which sections generate leads, then group by Landing Page to compare individual URLs within a section.