Skip to content

Capture Google Ads Data in FormAssembly: A Four-Step Setup

Visitors and form completions alone do not show which advertising work produced customers or revenue. This guide explains how to tag paid-search visits, store their campaign details while people browse, and submit those details with a FormAssembly lead so reporting can continue beyond the first click.

Why campaign identity must survive to the lead record

A pool-equipment advertiser spends $2,000 on each of two campaigns. Pool Pumps produces 200 visitors and 20 leads; Pool Cleaners produces 100 visitors and 10 leads. Judged only on traffic and leads, Pool Pumps looks stronger. The downstream result reverses that impression: Pool Cleaners creates 5 customers and $25,000 in revenue, compared with 2 customers and $8,000 for Pool Pumps. Its lead-to-customer rate is 50% rather than 10%, its average customer value is $5,000 rather than $4,000, its acquisition cost is $400 rather than $1,000, and its return on ad spend is three times higher. The practical lesson is to preserve campaign identity at form submission, then join that identity to later customer and revenue records.

Step 1: Tag each ad destination with UTM parameters

Add UTM parameters to the destination URL behind each Google Ad. These parameters are extra text appended to the URL so the receiving page can identify the campaign context. A consistent paid-search convention is: UTM Medium for Paid search, UTM Source for Google, UTM Campaign for the campaign name, UTM Term for the ad group, and UTM Content for the specific ad. For example, a destination ending in /integrations/formassembly could carry utm_medium=paidsearch, utm_source=google, and utm_campaign=brand-campaign. Use a UTM builder to keep naming consistent across campaigns.

Step 2: Add six hidden fields to FormAssembly

Create these hidden fields in the lead form: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; and Landing Page Group. In FormAssembly, add a field of type Hidden Field for each one and configure its default value. The first four fields carry the normalized channel hierarchy. The final two identify the exact first page and its broader page group.

Step 3: Let the tool populate the fields at submission

When a visitor arrives, the attribution tool reads the UTM values and stores them in a browser cookie. That persistence matters when the form is on a later page: the parameters do not have to remain in the address bar. At submission, the tool fills the hidden fields. In a brand-campaign example, Channel becomes Paid search, Channel Drilldown 1 becomes Google, Channel Drilldown 2 becomes Brand campaign, and Channel Drilldown 3 becomes Free account ad. The tool also records the landing URL, such as /features/cloud-storage, and its group, such as features.

Step 4: Use the captured data in notifications, CRM records, and reports

The submitted record now combines the person's form answers—such as name, company, email, or phone—with the campaign and landing-page fields. Use those fields in lead notifications so each recipient can see the origin immediately. Send them to a CRM so sales and marketing share the same source context. Build reports by campaign, ad group, ad, landing page, or landing-page group, then join the results to customer and revenue data. A useful pre-launch checklist is: every ad URL is tagged; naming follows one convention; all six hidden fields exist; a test submission fills every field; a multi-page browsing test still retains the original campaign; and the CRM or notification receives the values.

Failure distinctions to check before launch

Raw UTM capture and normalized attribution solve different problems. Raw capture preserves exactly what was typed, which can split one source into several labels when capitalization or naming varies. Normalized attribution recognizes common variations and assigns them to a consistent channel. Cookie-based persistence also differs from reading parameters only on the form page: it retains the first-touch context across internal navigation. Finally, landing-page fields add a content dimension that UTM values alone do not provide, allowing a blog section and individual posts to be evaluated separately.

Capture every source, not only paid search

The same setup can cover Organic Social, Paid Social, Organic Search, and other sources, not only Google Ads. That broader view prevents a paid campaign from receiving credit for demand actually created elsewhere. It also supports budget decisions: if search optimization produces most customers while paid search produces fewer, resources can be shifted based on complete lead-source evidence rather than an incomplete advertising-only view.

Frequently asked questions

What happens if someone does not submit on the page they first landed on?

No. If the visitor lands on the homepage and later submits on another page, parameters stored in a browser cookie can still be passed to the form, so the originating campaign is not lost because of internal navigation.

Why not capture raw UTM values directly?

Raw values can fragment reporting. For example, Google.com, google, and adwords may appear as separate sources. Normalization groups recognizable variations under one channel, such as Paid search, reducing manual cleanup.

Which hidden fields are needed in FormAssembly?

Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Add each as a Hidden Field type in FormAssembly and configure a default value for it.

Pool Pumps CampaignPool Cleaners Campaign
Spend$2,000$2,000
Visitors200100
Goal Completions2010
Pool Pumps CampaignPool Cleaners Campaign
Spend$2,000$2,000
Visitors200100
Leads2010
Customers25
Revenue$8,000$25,000