Skip to content

Capture Marketing Attribution Data in Fluent Forms

Fluent Forms collects the submission; it does not, on its own, know whether the person arrived from a paid search ad, an organic result or a newsletter.

This guide shows how to close that gap: create hidden fields in your form, let an attribution tool fill them as visitors browse, and let Fluent Forms carry those values to whatever receives the submission. You will also find a field map, a test checklist and a way to tell a missing-data problem from a wrong-data problem.

What this setup actually does

Three things happen in sequence. First, your form gains hidden fields — inputs the visitor never sees but which travel with the submission. Second, an attribution tool watches which marketing channel a visitor arrived from and writes that information into those hidden fields. Third, when the form is submitted, Fluent Forms captures the attribution values along with the normal contact details and passes them to the CRM and other tools connected to the form.

The result is that a lead record can carry its own origin story: the channel, the campaign, the ad, and the first page the person saw. That is what makes downstream reporting possible without asking the visitor anything.

Step 1 — Add the hidden fields

Open your form in Fluent Forms and add hidden fields for the attribution values you want to keep. These fields are the handover point: the attribution tool needs somewhere to write, and Fluent Forms needs somewhere to read from at submission time.

Keep the field names consistent between the form and the receiving tool. A hidden field that exists but is never mapped downstream will collect data that goes nowhere, which is the most common reason a setup looks complete but reports stay empty.

Step 2 — Let the attribution values be filled in

As visitors move through your site, the attribution tool monitors the marketing channel they came from and writes the matching values into the hidden fields you created. This happens before the form is submitted, so by the time someone fills in their name and email, the origin data is already sitting in the form.

Step 3 — Capture on submission and forward it

On submission, Fluent Forms captures the attribution information — channel, campaign name, ad name and similar values — and sends it to the CRM and any other tools you have integrated with the form. Nothing extra is asked of the visitor, and no manual tagging step is needed at the point of conversion.

Field and control map

Use this map to plan which hidden fields to create and what each one is for. The left column is the value category; the right column describes what a record should contain once the setup is working.

What the captured data looks like

Think of the two data categories as answering two separate reporting questions.

The first question is how the visitor found you. The answer is a channel label — Paid Search, Paid Social, Organic Search and so on — and, where the channel supports it, the finer detail beneath that label. A paid search visit, for example, can be traced to the campaign, ad group and keyword that produced the click; other channels carry their own equivalents.

The second question is what content met the visitor first. The answer is the URL of the first page they saw, plus the category that page belongs to. Someone who arrived on a blog article about licensing music would be recorded with that article's URL and the page category "Blog".

Keeping the two questions separate matters when you read reports later: a channel breakdown tells you which routes bring people in, while a landing-page breakdown tells you which content earns their attention once they arrive.

Where the data can go

The practical question is which tool receives the submission, because that is where the attribution values will land. The values are ordinary form fields, so they follow the submission to whatever Fluent Forms is already connected to. Grouped by the decision you are making:

  • If you need each lead record to show its origin, route the values to your CRM. The original tool documents connections to Salesforce, Zoho, Pipedrive, Insightly and others; confirm which of these your own setup supports before relying on the list.
  • If you need to segment subscribers by where they came from, route the values to your email platform. The original tool documents Mailchimp, Campaign Monitor, AWeber and others; verify against your own integration list.
  • If you need revenue traced back to the channel and content that produced the customer, route the values to your billing system. The original tool documents Stripe, Square, PayPal and others; verify against your own integration list.
  • If you need dashboards that break key business metrics down by channel and campaign, route the values to your analytics or BI layer. The original tool documents Tableau, Power BI, Google Data Studio and others; verify against your own integration list.

In every case the same hidden fields supply the values; only the destination changes. Treat the named platforms as the original tool's documented integrations, not as a confirmed list for your own account.

Pre-launch checklist

Run through these before you rely on the numbers:

  1. Every hidden field you plan to report on exists in the live form, not just a draft.
  2. Each hidden field is mapped to a matching field in the receiving tool.
  3. A test submission from a tagged link produces values in all expected fields.
  4. A test submission from a direct visit produces the expected default or empty values rather than a blank record.
  5. The first landing page recorded matches the page the test visitor actually arrived on.
  6. The record appears in the CRM, email list, billing tool or report you intended — not only in the Fluent Forms entry list.

Missing values vs. wrong values

Two failures look similar in a report but have different causes.

If attribution fields are empty, the chain is broken somewhere: the hidden field may not exist on the live form, may be named differently from the field the attribution tool writes to, or may not be mapped to the downstream tool. Start at the form, then check the mapping.

If attribution fields are populated but point to the wrong channel or campaign, the chain is working and the input is at fault. Check the tracking parameters on the links that brought the visitor in, and check how your channel rules classify that traffic. Fixing the form will not help here; fixing the tagging will.

Getting started

Before you commit to a plan, confirm the commercial terms directly with the provider. Pricing, any free starting tier and trial length can change, so treat figures you have seen elsewhere as unverified until you check the current offer yourself. A sensible evaluation sequence is to confirm what the free tier includes, note the starting price of the first paid plan, and check the trial's length and conditions — then decide whether the setup fits your form volume and reporting needs.

Hidden field map for Fluent Forms attribution
Value categoryWhat the field should containWhere it is used
ChannelBroad source such as Paid Search, Paid Social or Organic SearchCRM records, channel-level reports
Channel detailCampaign, ad group and keyword (for Paid Search) or the channel's equivalentCampaign and keyword reporting
Campaign nameThe named campaign the visitor arrived throughCRM fields, BI breakdowns
Ad nameThe specific ad that produced the clickAd-level reporting
Landing page URLThe first page the lead saw on your siteContent attribution, page-level reports
Landing page categoryThe type of page, such as BlogGrouped content reporting

Field categories reflect what the attribution tool captures; the exact field names you create in Fluent Forms are yours to choose, but they must match the downstream mapping.

Frequently asked questions

Do visitors see or fill in the attribution fields?

No. They are hidden fields, so the visitor never interacts with them. The attribution tool writes values into them in the background, and Fluent Forms submits them along with the rest of the form.

When exactly is the attribution data captured?

At form submission. By that point the channel and landing-page values have already been written into the hidden fields, so the submission carries them out to your connected tools.

Can I send the same data to more than one destination?

Yes. The values are ordinary form fields, so they travel to whichever tools Fluent Forms is connected to — a CRM, an email platform, a billing system or a BI tool — without needing separate collection for each.

What is the difference between channel data and landing page data?

Channel data describes how the visitor arrived, such as Paid Search or Organic Search, with campaign and keyword detail where available. Landing page data describes the first page they saw and that page's category. One is about the route in; the other is about the content that met them.

Why are my attribution fields empty in the CRM?

The most likely causes are a missing hidden field on the live form, a name mismatch between the field and what the attribution tool writes to, or a missing mapping to the downstream tool. Check the form first, then the mapping.