Skip to content

Capture Google Analytics attribution in Fluent Forms

A form submission tells you who contacted you, but not always how they found you. By storing channel, campaign detail and first landing page alongside the submission, you can connect later leads, opportunities, customers and revenue back to the marketing activity that produced them.

Why form submissions need attribution context

Without attribution stored on the lead record, reporting often stops at website visits or clicks. The visitor may browse several pages before submitting, so the form itself needs to carry forward the context of the first visit. That context includes the marketing channel, more specific campaign detail, and the page where the journey began.

How the capture flow works

An attribution script installed on the website examines visitor and campaign information, classifies the visit into channels comparable to those in Google Analytics, and stores that classification in a browser cookie. When a form is completed, the script writes the stored values into hidden fields on the form. On submission, Fluent Forms saves those values together with the name, email, phone number and other details entered by the visitor. The same submission can then be passed through a native Fluent Forms integration or a tool such as Zapier into a CRM or spreadsheet.

Setup checklist

Checklist: 1) Add the six hidden fields listed below to each lead form. 2) Install the attribution script on the site. 3) Submit a test form from a known campaign link and confirm every hidden field is populated. 4) Confirm the values appear in the Fluent Forms submission record. 5) Map the fields to the matching CRM or spreadsheet fields. 6) Test a second submission from a different channel or landing page so grouping and drilldown values can be distinguished.

Worked example: a paid-search visit

Consider a visitor who arrives from a branded Google Ads campaign for a legal firm. The broad channel is Paid Search, the first drilldown identifies Google, the second identifies the brand campaign, and the third carries a further descriptor such as Los Angeles Legal, subject to the UTM values used on the ads. The landing page might be a litigation services URL, with Services as its group. That combination lets a report separate the effect of the campaign from the effect of the page that first received the visitor.

Channel detail versus landing-page detail

Channel data shows the broad origin and can include further detail such as ad group, keyword or campaign for paid search. Landing page data shows the first page seen and its category. Together they support two different questions: which marketing activity produced the lead, and which part of the website first received that visitor. For example, a blog category total can be compared with the performance of individual posts, while a channel total can be compared across paid, organic and social activity.

Four reports to build after capture

Use leads by channel to compare monthly volume and guide budget allocation. Use opportunities by Google Ads campaign to see which campaigns create sales-ready opportunities, not only enquiries. Use customers by Facebook ad network to compare results across Facebook, Instagram, Messenger and WhatsApp placements. Use revenue from Organic Search by search engine to judge whether SEO investment is producing valuable customers relative to other channels. In each case, group by the captured field and then join the resulting leads, opportunities, customers or revenue in the CRM.

Hidden fields to add to Fluent Forms
Hidden fieldWhat it recordsUse it to answer
ChannelBroad marketing channel, such as Paid Search or Organic SearchWhich channel produced this lead?
Channel Drilldown 1First level of channel detail, such as the platformWhich platform sits behind the channel?
Channel Drilldown 2Second level of detail, such as a campaignWhich campaign produced this lead?
Channel Drilldown 3Third level of detail, such as a further campaign or ad descriptorHow does this lead compare within the campaign?
Landing PageFirst page the visitor saw on the siteWhere did the visitor journey begin?
Landing Page GroupCategory of that first page, such as Blog or ServicesWhich site section first received the visitor?

Field set as listed in source; values depend on visitor and campaign data available at visit time.

Reports enabled by captured attribution data
ReportGroup byDecision it supports
Leads by ChannelChannel and monthWhere to allocate marketing budget
Opportunities by Google Ads campaignGoogle Ads campaign and monthWhich campaigns create sales opportunities
Customers by Facebook Ads NetworkFacebook ad networkWhich network produces customers
Revenue from Organic Search by search engineSearch engine, filtered to Organic SearchWhether SEO investment is producing revenue

Reports require captured fields to be passed into a CRM or spreadsheet and joined to downstream lead, opportunity, customer or revenue records.

Frequently asked questions

Which fields should I add to a Fluent Forms form?

Add hidden fields for Channel, the three Channel Drilldown levels, Landing Page and Landing Page Group. An attribution script installed on the site then fills those fields from visitor and campaign information before the form is submitted, so Fluent Forms stores the values with the contact details.

What is the difference between Channel, Drilldown and Landing Page data?

Channel gives the broad source, such as Paid Search or Organic Search. Drilldown fields add progressively finer detail, such as the platform, campaign and a further campaign or ad-level descriptor. Landing Page records the first page seen, while Landing Page Group records its category, such as Blog or Services.

What reports become possible after capture?

Once the fields travel with the submission into a CRM or spreadsheet, you can group leads by channel, opportunities by Google Ads campaign, customers by Facebook ad network, and revenue from Organic Search by search engine. Those views help compare volume and value rather than relying on clicks alone.